[PAID] Need help to solve this issue

AI-generated summary

A user seeks help to fix a UI issue where clicking the ā€˜X’ to close the welcome banner in Discourse doesn’t work until a page refresh. Arkshine identifies the issue as a missing tracking property in the user’s dismissed_banner_key, requiring a core fix via a pull request. The user, haydenjames, expresses concern over the need for a code-level fix despite being unfamiliar with coding, and offers a $100 reward. Arkshine reassures that it’s a minor issue and not unique to the user, likely caused by a recent code change. Mittens questions the need to pay for such fixes, prompting haydenjames to share a humorous image emphasizing the value of expertise. The discussion highlights the gap between technical knowledge and non-technical users, with merefield supporting the idea that developers need to be compensated for their skills.

What would you like done?
Solve this issue: Clicking "x" to close welcome banner does not work until page refresh

When do you need it done?
ASAP

What is your budget, in $ USD that you can offer for this task?
$100

2 Likes

That’s something you would need to fix in the core.

A quick test showed me it misses a tracking property on the user’s dismissed_banner_key to make the change reactive on the UI.

msrdc_w0WeMRWjM3

I can PR later.

3 Likes

You have to pay for this stuff?

2 Likes

Thanks for your reply. Beyond fixing, how does this even happen. I’m a total noob, so

I had to research that to figure out what you meant was ā€œI can open a pull request later.ā€ As mentioned, when it comes to code or core or anything along thoes lines I’m a total noob.

I don’t mess with Discourse outside of the Admin UI allowed settings. So that’s a bit alarming that the ā€œcodeā€ needs fixing. :anxious_face_with_sweat:

In any case if you can solve, I’ll stop responding to other DMs now. If you accept Paypal that would be great. If not let me know method.

Also, I would like if you can provide info on cause, so that I can avoid creating this issue (assuming its something I’ve done).

1 Like

If you don’t know, you just don’t know. I did try the free route in a forum posts.

My niche isn’t anything along the lines of JavaScript, code or Discourse core. I can either spend more hours trying to solve myself or… pay someone who has experience and training in this niche and can as-it-were use a hammer knowing exactly where to hit.

2 Likes

Sorry, I tend to be too technical sometimes :sweat_smile:.

No worry, it’s a minor interface issue. You’re correct, I’ll propose a change in the Discourse repository later with a pull request.

1 Like

How is this only affecting my install. I am a bit OCD, but I’m sure if other admins had this issue it would be known a month or 2 ago.

Anything I need to avoid doing in future?

You’re not the only one, I can reproduce it in my local instance.

Discourse code is always evolving, it’s possible a recent change for this feature created this side-effect. It happens. What you can do in this situation is to report and wait for a fix!

1 Like

Ahh ok. I understand. It started a while back. I should have marked the first date. But it would be either February or March.

1 Like

This is a very disappointing Post.

Do you have to pay rent? Well, spoiler alert, so do most Developers, unless they are living with mum! :smiley:

5 Likes

Sometimes tech/dev communities forget that what may seem simple to those with experience and knowledge still holds real value. The real worth comes down to how badly the person hiring needs the task done quickly and correctly.

I’ll share something my late father forwarded to me a few years back, which he’s always taught me:

Hopefully, it adds a smile to those who read it that are wielding the hammers.

6 Likes

Dude, I don’t code, I don’t do any of that stuff, so I don’t know what it costs or what it takes to do it.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.