AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
Notifications
Clear all

[Closed] Users that are not logged in (Guests?) unable to see the "next page" buttons

3 Posts
2 Users
0 Reactions
3,687 Views
Posts: 75
 TGW
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@tgw)
Estimable Member
Joined: 9 years ago
[#6294]

Please see here

the-great-work.org/community/main-forum

There are 20+ pages to this forum, but a logged out user has no access to the "next page" button. Attached are screenshots

So

I have turned off most account verification for a brief period so you can register with any fake email address, if you want to try it from your dev workstations

 

 

 

 

 

sd

2 Replies
Posts: 75
 TGW
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@tgw)
Estimable Member
Joined: 9 years ago

attachment 2

sd

Robert
Posts: 10753
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@robert)
Support Team
Joined: 3 months ago

Please navigate to Dashboard > Forums > Dashboard admin page, and click on the [Delete all caches] button. if this doesn't help please wait for next version release. We've already fixed this issue in next 1.5.0. It cones very soon.


Share: