Jonathan Lahijani Posted September 16 Posted September 16 10 hours ago, taotoo said: Yes - at first removing the slash worked, then it only worked sometimes, and now it never works! Weird. For me it's perfect.
Ivan Gretsky Posted September 17 Posted September 17 This might be ip-based protection or something like that. I guess LA is in the whitelist)
Peter Knight Posted September 19 Posted September 19 403 errors had disappeared for me today. They’re back again (boo) but today was the first time in weeks I could visit https://processwire.com/talk/discover/unread/ 1
Tiberium Posted September 20 Posted September 20 I can only use https://processwire.com/talk/discover without slash. So the menu point in the header is non-functional for me, since months now. It makes it hard to follow old topics, when something happen their 🙁. 1
Tiberium Posted September 24 Posted September 24 As status update: Now it is functional without problems. Even witht he ending slash. 1
dynweb Posted September 24 Posted September 24 Works for me again, too, first time in weeks (months?). 1
Tiberium Posted Sunday at 08:32 AM Posted Sunday at 08:32 AM And we are back with the problem. And again, removing manual the slash will fix it. 1
gmclelland Posted Sunday at 02:27 PM Posted Sunday at 02:27 PM 5 hours ago, Tiberium said: And we are back with the problem. And again, removing manual the slash will fix it. Ugh…same for me now. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now