Support Forum

Clicking "Mark All Topics As Read" Takes Me to Main Page, Does Nothing

SK Se Kim
Se Kim
Member

Since upgrading to 5.3, users are no longer able to properly use the “Mark All Topics As Read” button in the top right corner of the forum pages.  Clicking “Mark All Topics As Read” simply sends users to the main blog page, and out of the forum.  Furthermore, upon returning to the forum, none of the topics are marked “read”.  The “Mark All Topics As Read” button worked perfectly until right after the update.  

15 Answers

New Answer

MP Mr Papa
Mr Papa
Member

what is the url of the mark all read button?  We have had one other user with perhaps something similar, but in general no issues with it since the upgrade for users…

SK Se Kim
Se Kim
Member

Hi, the button points to:

 

http://www.mywebsite.com/?mark-read

YS Yellow Swordfish
Yellow Swordfish
Member

which is clearly incorrect and missing the forum slug.

Steve: Do we need to change this in some way. I know 2 users out of hundreds is not manysmilebut… Has it got something to do with the server type? Maybe ISS instead of *Nix or something.

CA Carlos
Carlos
Member

Hi, as Steve and Swordfish know i have the same issue… if it helps my page is on a 1and1 L2 dedicated server but gestionated by them… so is more easy.. i have not much options and is very easy to work in…

The “mark all as read” has always worked ok..but it stopped working with the same issue that Se Kim has…

 

I didn´t change any config… either the WP or the server…. but if i install again SP on another WP the problem stills remains… so it comes from the server…. 

hope this helps…. and sorry for my poor english!! :(

MP Mr Papa
Mr Papa
Member

@andy, wouldnt think so… its an option loaded from the db…  highly doubt the slug is missing in teh db…

and frankly, this has changed in upcoming 5.3.1 to use ajax instead… would wait until release tomorrow and see what happens with these two users…

CA Carlos
Carlos
Member

good idea… let´s wait until 5.3.1

 

Thanks for all guys!! great job…. 

MP Mr Papa
Mr Papa
Member

it was a totally unrelated change…  just use ajax with no page reload…

CA Carlos
Carlos
Member

Mr Papa said
it was a totally unrelated change…  just use ajax with no page reload…

I´m not an expert… but maybe this can solve our problem :)  

MP Mr Papa
Mr Papa
Member

maybe.. it wont use the page slug anymore… though no clue why on two installs it would not be available…

SK Se Kim
Se Kim
Member

Ok.  If a new version is being released tomorrow, I will see if that solves it.

 

Though only two of us here are having the issue, it is annoying hundreds of forum users :)

YS Yellow Swordfish
Yellow Swordfish
Member

Steve is right that this should be resolved by changing the current page-reload to using Ajax which will be in the imminent update.

But I think he was wrong to dismiss the current issue as being a server issue. The current logic uses the server http request return variables to ascertain and build the reload page url and clearly on these two reports the variable in question is not being returned by the server. Academic at this juncture but a curious issue al the same.

SK Se Kim
Se Kim
Member

FYI:  Performing the most recent upgrade today solved this issue.

MP Mr Papa
Mr Papa
Member

good deal… of course, the change was unrelated to your problem as it uses ajax instead of page load but glad it got it working for you…