Fórum Discourse Meta

Thanks for your feedback, it is helpful. Note that random username generation isn’t mandatory at all and You can opt-out using these instructions in the first post: rishabh: Opting out of random username generation If you want to use email codes for signup but without pre-filled username generation, click Show related settings for this upcoming change and disable the enable_random_usernames site setting. Once done, here’s what the screen looks like:

Will we be able to permanently disable these cards? As a user, if I click on that link I just want to go to the category page, not some intermediary step. Also as UX feedback: how would you go from the card to the category topic list? It’s not clear from the screenshots.

kris.kotlarek: My theory is that 6th of July you had a new dashboard enabled for a moment (with the new tracking method enabled), and you disabled it. That’s right

Today on meta.discourse.org … Key Stats In the last 24 hours, Meta saw 77 new posts across 33 new topics , with 99 likes given to those posts. Top users by activity: Moin — 11 posts, 13 likes Mbauman — 5 posts, 7 likes Awesomerobot — 3 posts, 7 likes Martin — 3 posts, 7 likes Zogstrip — 2 posts, 6 likes Satonotdead — 4 posts, 5 likes Ethsim2 — 6 posts, 4 likes Lief — 3 posts, 4 likes Chapoi — 1 post, 4 likes Olivia — 1 post, 4 likes Interesting Topics #Feature Mbauman asked for the ability to post in non-enabled languages , arguing that the long tail of languages should be supported for authorship even when a site hasn’t vetted translations. Moin pointed out that Discourse AI already translates posts regardless of the written language, and Awesomerobot suggested hiding the composer menu or letting admins configure additional languages as reasonable next steps. Olivia confirmed there is still no built-in order:op_edit for topic filters in the OP Edit Time feature request , recommending Data Explorer as a workaround. Moin then highlighted the per-category Allow unlimited owner edits on first post setting, which Lief said was a perfect fit for their employee-authored article workflows. Support Satonotdead asked about the 50 max nodes limit in Workflows while building a badge-to-cheer-points automation. Awesomerobot explained it’s mostly a practical UI and performance ceiling, and suggested splitting workflows with the “workflow call” and “call workflow” nodes. Mcwumbly agreed, a

Thank you for reporting this. We are in transition on how browser pageviews are measured. My theory is that 6th of July you had a new dashboard enabled for a moment (with the new tracking method enabled), and you disabled it. It is totally fine, but the graph should move back to use numbers from the old tracking. I have a PR with the fix: github.com/discourse/discourse FIX: Select the browser pageview counters for each day (#43766) main ← blank-site-traffic merged 04:53AM - 17 Sep 26 UTC KrisKotlarek +154 -97 Two transports count browser pageviews. A beacon request sends one count. A head … er on a usual request sends the other count. Both transports can record the same visit. Thus a report must read only one of them for each day. Before this change, a report found the first day with beacon data. It then read the beacon counters for that day and for all later days. One day with beacon data was sufficient to make this decision. Some sites recorded beacon data on one early day only. Beacons were behind a feature flag. On these sites, a report read a beacon count of zero for all later days. The site traffic report subtracts the browser pageviews from the total pageviews. The remainder is "other traffic". Thus all traffic became "other traffic". A report now makes this decision for each day. It reads the beacon counters on each day that recorded beacon traffic. It reads the header counters on the other days. A day with no beacon data does not change the other days. The admin dash

This plugin would be immensely more valuable if it worked with custom urls (more than just amazon) Most forums are niche and most niches have a handful of small businesses with affiliate programs. I’d be happy to provide affiliate knowledge as assistance, but I don’t code anymore

jenmck: Oh?!? When I had 4 columns, there wasn’t a plus button to the right of the 4th column and I couldn’t figure out how to add another - is there a different way to do it that I missed? That’s very exciting news! Nope, no special thing needed If you hover on the empty space in the board you will see the plus button:

I merged an upcoming change for this today, and enabled it on Meta Category hashtag floating cards and subcategory hashtag display improvements Announcements We are making some changes and improvements to how subcategory hashtags display per Can we make inline links to subcategories more concise? , and at the same time are adding the same floating card functionality that you already see for user mentions e.g. if you click on @martin . This card will show the category title, icon/emoji, description, as well as links to any parent categories. Users with permission can see the “Edit description” button, as well as the “New Topic” button, which is also c… See here Community Building Community Building > Praise Contribute > Bug (Edit: Hmm hashtag separator is still showing but shouldn’t, will investigate)

Finally had the time to test it myself; everything seems to be resolved

Looks like all my views are considered “other traffic” now.

I hit the 50 node limit for the first time recently as well. In my case, it was reasonably straightforward to split things up. But I was a bit surprised when I hit it. I knew the limit existed, but I it didn’t feel like I had 50 nodes yet. I counted. I did. I could imagine making the hard coded limit a bit higher, but I think it’s helpful to have a limit and the number isn’t far off from what it should be. One thing though… I noticed that sticky notes count towards the limit. That felt odd, and I think we should probably change that.

I think it’s just a rough point at where things could start slowing down and get difficult to manage in the UI… if you had to debug 100 nodes in one workflow it would probably be somewhat painful. We have “workflow call” and “call workflow” nodes that can be used to split things up. You can set a workflow that starts with “workflow call” as the trigger, and use “call workflow” from another workflow to invoke that first workflow.