• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Permission Denied??? - BUG

Weird, here's the error I get when I try to access it.

ERROR: Sorry, you do not have permissions to access the requested object.

Error Code: 103
 
Ahhhhhhh, figured it out.

Some mod seems to have moved the thread to a forum that I did not have added to my view. So apparently if the thread gets moved and you don't have that forum enabled in your profile, you're going to get this error when you try to access it.

Jason, here's another forum bug for you to fix.

techfuzz
 
No, the URL and ID are correct, Fusetalk doesn't know how to properly handle it.
Here are the steps to reproduce the problem:
1. Create and subscribe to a thread in a forum
2. Remove the forum as an active forum from under your profile
3. Go to My Forums and click on the thread

You should get the permission denied error.

techfuzz
 
Originally posted by: techfuzz
Originally posted by: Jason Clark
you mean category blocking?

That is correct.

techfuzz

Yep, this has been bugging me, also.

I don't have HD or FS/FT in my list of categories that show up, but I will often look at FS/FT threads linked by TeAm members, but I now am unable to do that. I do not wish to actively block the other forums, just not have them visible unless I specifically click a link to them.



Garry
 
Originally posted by: Confused
Yep, this has been bugging me, also.

I don't have HD or FS/FT in my list of categories that show up, but I will often look at FS/FT threads linked by TeAm members, but I now am unable to do that. I do not wish to actively block the other forums, just not have them visible unless I specifically click a link to them.
Thanks, I couldn't quite put that into words, but you did for me. This is the issue that is at hand in a nutshell. I would like to add though that I block categories because they serve little interest to me and it's a waste of space to list them (also a bandwidth issue).

Here are what I think the 3 possible solutions are:
1. Allow access to other categories even if they are personally blocked
2. Change the error message to be more informative
3. Don't permit moderators to move threads from one category to another

techfuzz
 
Originally posted by: simms
Why not just enable them? Tempted to buy things?

Partly, yes. Mainly, because I never will. It also saves a bit of bandwidth by not listing those categories which I will more than likely never view, unless linked for specific reasons (as I said before, a TeAm mate selling something, as we are now not allowed to put FS/FT threads in DC only).


It's something which worked one way before, but has again changed completely with the new version of FuseTalk.


Garry
 
Originally posted by: Confused
Originally posted by: simms
Why not just enable them? Tempted to buy things?

Partly, yes. Mainly, because I never will. It also saves a bit of bandwidth by not listing those categories which I will more than likely never view, unless linked for specific reasons (as I said before, a TeAm mate selling something, as we are now not allowed to put FS/FT threads in DC only).


It's something which worked one way before, but has again changed completely with the new version of FuseTalk.


Garry

"It also saves a bit of bandwidth"

That's what I like to see, a dedicated Anandtech Community member 😀

:cookie;

*crys tears of joy*
 
I ran this by the developers and this is working as it is supposed to. You block the category, so we don't show anything to do with that category.

We won't be altering the way this works at this time.,
 
Originally posted by: Jason Clark
I ran this by the developers and this is working as it is supposed to. You block the category, so we don't show anything to do with that category.

We won't be altering the way this works at this time.,
If it's working as it is supposed to, the error message should be changed to be more informative. For the average user this error message -
ERROR: Sorry, you do not have permissions to access the requested object.
Error Code: 103

is ambiguous and misleeding. It isn't that the user doesn't have permission to access the requested object, it's being blocked at-will because of the user's personal preferences. User preferences and user security (i.e. permissions) are two different entities. At the very least provide for the user some kind of instruction in the error message indicating how to fix this or what the real issue is, not some ambiguous useless error message that only developers will understand.

techfuzz
 
Back
Top