👨‍💻 #Proposal-89: Community Admin/Mod Fix on SteemitdevsteemCreated with Sketch.

in Steem Dev8 days ago (edited)

🪲 The Problem

Following the release of the URL Updates in #proposal-86's final deliverable, a bug was introduced that prevented admin and moderator privileges from appearing within a post - unless the post was accessed via a specific route.

You'll notice in the screenshot below that there's no ability to change the user's label, despite having Admin privileges.

{05866716-F3EA-4A58-B008-1AC39DFE23F5}.png

This was raised as #bug-3937 on GitHub.

Separator-code.png

⚙️ The Cause

This was caused by the change in URL structure when improving Steemit's SEO.

The replacement of hive-xxxxxx with the community name meant that when the page state of a post is set and the code looks up the community via the URL, Hivemind cannot return the community information without the hive-xxxxxx community identifier.

So when the page tries to access the 'community' information in the state, it returns 'undefined' - an empty object.

It's this 'community' property which then drives the post permissions.

Separator-code.png

🛠️ The Fix

The fix is straightforward enough (as always, the few lines of code mask the effort involved in solving the problem!) and involves linking the getCommunty() function to the page;

Then, as the page mounts, if the community property is empty, call this function.

I'll document the code fully (all 9 lines of it) once it's been thoroughly tested.

Separator-code.png

🧪 Testing

As the post title indicates, this is now available on https://steemitdev.com for testing.

It would be great if all community administrators and moderators who read this check that the functionality is now available to them and I'd appreciate a brief comment below to say whether it is / isn't working for you.

Separator-code.png

🚀 #proposal-89

We're extremely close to getting #proposal-89 over the line so that I can continue development for the next 111/2 months. I wasn't going to leave an annoying bug that I introduced, hence the fix before the proposal is hopefully approved.

Your support is still needed to get this over the line





 

 

Sort:  
 8 days ago 

I support your proposal.

Thank you - We're so close...

Tested, tested, one, two, one, two… Works!

Great that you are here, great that you stay here. I’m looking forward to an even better Interface (is that possible after you fixed all the problems?) because concerning the proposal I have no doubts!

Thank you - things are looking good to get this fix live 🙂

As for the proposal - it climbed the mountain whilst I slept so here we go... 🚀

it climbed the mountain

You have my votes (yup more than one)

♥️🍀

Is this problem solved?

Screenshot_20250311-123746_Samsung Internet.jpg

A comment that slides.👆👇

The sliding coild make it possible to set the % but if I try it keeps sliding side wards. Ieven tried to hold the screen with one hand while I tried to move the slider which is impossible.

As you can see the slider is out of vision if I only see the comment (all the white surrounding it is what I can see if the comment van be swiped.

Screenshot_20250311-124014_Samsung Internet.jpg

It would also be great if the % of vote voild be set by typing it. It takes me very long to slide the % I eant to vote for.

Oh, that voting bar's a pain in the butt on a mobile. That really should be logged as a bug and fixed!

I've raised it here so that I don't forget - https://github.com/steemit/condenser/issues/3940

I hadn't noticed that it wasn't working temporarily. For the moment I can only say: no problems to be seen.

Thanks for checking. Things are looking good my end too so it should be good for approval 👍

It appears to me that the HIVE-XXXX is going to be replaced by the community name in URL of the post. If a domain already exist with the same community name by another registrant then what will be ICANN's Uniform Domain-Name Dispute-Resolution Policy (UDRP) implication.

The domain name will always be steemit.com so we could have 10 communities, all with the same name and there will be no negative implications to this. If all of the communities are active, then it could even benefit the platform for that community keyword.

How about setting as a beneficiary if the hive + number is unknown and names look idemtical?

The hive-xxxxxx account and community identifier still exists so setting that as a beneficiary is still good. The only thing that’s changed is when you click on a post - instead of hive-xxxxxx appearing in the url, the community name will instead. So if you post with @hive-xxxxxx and ask people to delegate / set as a beneficiary, that will all work as before.

Thanks for answering.

Thank you for the explanation with clarification.