[Bug] Can't edit random post.

[Afrodude]

Finally I have just figured out why I am seeing this message. 

It's really sad there were no error logs to show, and we have tried before to find what causing this in this topic.

 

The bug is related to the new anonymous content new feature. 

How this message shows. 

• Forum that has allow anonymous content feature enabled. 
• Admin group or staff groups have permission to post anonymously (can post anonymously enabled for the group)

This message shows whenever the staff members who can edit any member's post/reply trying to edit a member's reply to the topic where forum has allow anonymous content feature enabled and this member group has no permission to post anonymously. 

The message will not show any more if you give that member group permission to post anonymously or disable this feature from forum settings, and only shows whenever staff members trying to edit the reply of a member who has no permission to post anonymously where this feature enabled on the selected forum. 

After this message shows, and the topic still saying saving.... 

Yet it never ends, but if you refresh the page you will noticed it's already saved. 

 

Hopefully you guys fix this bug because it wasn't easy to find after all this time especially it doesn't has any error logs.  

[Marc]

Could you please check you are using the latest release of the platform on this? I cannot see any issues with this when testing on my end.

Here is what I  did, just to ensure we are on the same page

1. Edited one of my test forums and set it so that people could post anonymously
2. Created a test group which allowed anonymous posting
3. Created a test user, who was a member of that group
4. Posted a new reply to a topic as that member, and posted it anonymously
5. Edited my own group (now logged in as a member with full admin and moderator permission) to ensure I do not have permission in there to post anonymously in the group setting
6. Edited the post I created above

[Afrodude]

1 hour ago, Marc Stridgen said:

Created a test group which allowed anonymous posting

No. As I mentioned above the message shows to a member in a group that can't post anonymously. ( Admin is editing this member's reply) 

Look what you should do in order to see this message. 

1. A test forum that has allow anonymous content feature enabled. 

2. You can use the member group. Create a new member in this group for testing, and this group has no permission to post anonymously.

3. Admin group has permission to post anonymously.

4. Create a new topic on the test forum. 

5. Login as the new member and reply to the topic that was created by the Admin. 

6. Reply to the topic ( Remember this group has no permission to post anonymously, so this member won't be able to see the option), Just add any random comment. 

7. Logout from the member's account. 

8. Finally, login in as an Admin and edit the test member reply, and now you will see this message. 

 

Now after you have seen this message. Give permission to member group to post anonymously, and then go back to the same reply and edit it. You won't see the message again, yet if you remove the permission and edit the test member reply you will see the message each time you are trying to edit it.  

BTW I am using latest version of IPS. 

Edited September 20, 2021 by Afrodude

[Marc]

Sorry, Im a little confused here. Is it the member whos post was create who cannot post anonymously, rather than the person who is editing?

[Afrodude]

34 minutes ago, Marc Stridgen said:

Sorry, Im a little confused here. Is it the member whos post was create who cannot post anonymously, rather than the person who is editing?

I guess yes. The person whois editing is in Admin group that has access to post anonymously, and the admin is just editing any post was posting by any member's group who doesn't have access to post anonymously on any forum that has anonymous content feature enabled.

This message shows to me as admin while trying to edit other members replies. 

If you do the 8 steps I mentioned above, trust me you will understand it. 

Edited September 20, 2021 by Afrodude

[Marc]

I'm still unable to replicate the issue here in any way. Are you using the latest release of the platform there?

[Afrodude]

2 hours ago, Marc Stridgen said:

I'm still unable to replicate the issue here in any way. Are you using the latest release of the platform there?

If you are really paying attention to my replies, you would notice I answered your question dear.

 

Moreover, this issue is since 4.6 version. 

[Marc]

6 minutes ago, Afrodude said:

If you are really paying attention to my replies, you would notice I answered your question dear.

 

Moreover, this issue is since 4.6 version. 

My apologies. I had indeed missed that. I cannot however replicate this in any way on my test instance. Without being able to replicate this, I am unable to report this as a bug. I can certainly take a look at it on  your own site if you would like for me to do this. I would need an example user, forum, and item you are trying to edit.

[Nathan Explosion]

@Afrodude - what browser are you using? If Firefox, see here for a little more information on that error you are seeing.

 

[Marc]

That is indeed certainly worth a shot. (pun intended)

[Afrodude]

27 minutes ago, Nathan Explosion said:

what browser are you using?

All browsers. 

Again @Marc Stridgen if you did follow the steps above you would see the error message. I spent some time to create some videos to show you paraphs you will understand it better.

The second video where the Test member in the member group reply to the topic I created.

 

 

[Jim M]

Thanks for the steps/videos. I was able to reproduce this and got together some steps/further info for our developers. I reported this internally so our developers review and a fix will be available in a future maintenance release. Thanks for reporting this!

[Chris Anderson]

@Jim MThis isn't "really" a SOLUTION until you roll out a bugfix in an upcoming maintenance release.  If someone is scanning the forums and sees that it has been solved, they might assume the problem has already been fixed in a prior release.

There should be some other way of acknowledging that an issue has been properly identified and a request to the developers has been made to create a bugfix. 

Maybe you could mark this kind of post with a bugfix pending tag: "bugfix-4.6.7" or "bugfix-4.6.x" if it might end up being fixed a little farther down the line. 

This would help manage customer expectations for those reporting the issue and others that may be impacted by the bug and search the forums to determine if it has been reported and what the resolution might be.

[Jordan Miller]

2 hours ago, Chris Anderson said:

@Jim MThis isn't "really" a SOLUTION until you roll out a bugfix in an upcoming maintenance release.  If someone is scanning the forums and sees that it has been solved, they might assume the problem has already been fixed in a prior release.

There should be some other way of acknowledging that an issue has been properly identified and a request to the developers has been made to create a bugfix. 

Maybe you could mark this kind of post with a bugfix pending tag: "bugfix-4.6.7" or "bugfix-4.6.x" if it might end up being fixed a little farther down the line. 

This would help manage customer expectations for those reporting the issue and others that may be impacted by the bug and search the forums to determine if it has been reported and what the resolution might be.

Nice suggestion! We were thinking of possibly implementing tags somehow. This would be a great thing to discuss in its own dedicated topic 🥲 Appreciate the feedback! 

[nodle]

25 minutes ago, Jordan Miller said:

We were thinking of possibly implementing tags somehow.

Can't you just do a prefix tag like:

Fixed in 4.6.6

Fixed in 4.6.7

etc.?

[Chris Anderson]

Requested my comments in the post be deleted.  A new post has been created:

 

[Afrodude]

9 hours ago, Jim M said:

Thanks for the steps/videos. I was able to reproduce this and got together some steps/further info for our developers. I reported this internally so our developers review and a fix will be available in a future maintenance release. Thanks for reporting this!

Finally someone gets it. 

[Afrodude]

7 hours ago, Jordan Miller said:

Nice suggestion! We were thinking of possibly implementing tags somehow. This would be a great thing to discuss in its own dedicated topic 🥲 Appreciate the feedback! 

Perhaps since IPS will use this forum to submit tickets you guys IPS dev team might come with a new setting mark as processing with yellow highlight, and whenever the issue is fixed you can mark the new reply from IPS support team as solution. Moreover, whenever it's marked as solution it will remove the mark as processing automatically because the solution is finally here.  

Edited September 21, 2021 by Afrodude

[Marc]

13 hours ago, Chris Anderson said:

@Jim MThis isn't "really" a SOLUTION until you roll out a bugfix in an upcoming maintenance release.  If someone is scanning the forums and sees that it has been solved, they might assume the problem has already been fixed in a prior release.

There should be some other way of acknowledging that an issue has been properly identified and a request to the developers has been made to create a bugfix. 

Maybe you could mark this kind of post with a bugfix pending tag: "bugfix-4.6.7" or "bugfix-4.6.x" if it might end up being fixed a little farther down the line. 

This would help manage customer expectations for those reporting the issue and others that may be impacted by the bug and search the forums to determine if it has been reported and what the resolution might be.

Incidentally, and just to add to my colleagues comments above, we do actually follow up these tickets also. They are internally marked so that we can come back to them and let people know once it is resolved. The feedback though is very much appreciated 🙂

 

[Marc]

Just quick update to let you know that this has actually now had a fix applied and is awaiting developer review, so will be in a future release. Likely the next release