Topic title says all. Whenever I try loggin' in by the feature on the top menu bar, I get that error. However, when I head over to the login page and login, its fine. :p
What browser do you use?
Does that happens on any page you try to login or maybe on some page/s happens more frequently?
I've seen some similar errors in the log, but I can't find a way to reproduce it... :(
I use Chrome. I haven't tested it out on other pages yet, just the main homepage (not the community page). :p
I had this few times on Chrome too.
emanuele try to open forum in incognito tab and log in.
I usually do not write that I'm not able to reproduce something without trying it first. ;)
I tried and I'm not able to reproduce it, that's what I wanted to say.
Anyway, now I was able to reproduce it: you are accessing elkarte.net instead of www.elkarte.net.
Maybe
@Spuds or
@TE it's possible to setup a redirect to the www one?
The fastest way to "fix" it for you is to change the bookmark (if you use one), or navigate to any other page before logging in. ;)
Alright, thats good.
Off topic: So, who owns Elkarte btw?
Edit: I think I also found another bug, I gotta try it again to see if it really is a good or not. So gimme some time. :p
Its something
@TE needs to tweak in the site config file, in the server section, along the lines of
server_name elkarte.net;
return 301 $scheme://www.elkarte.net$request_uri;
Right now TE is doing the awesome hosting, at one point I was but the server I had it on was a bit weak in the knees! (i.e. the not so aweseome one :P) I did the actual domain registration ... not sure who "owns" anything, its an embodiment of FLOSS really, we simply try to keep things easy going and constructive. Lots of folks have made contributions and I think of them all as owners. Sure some have done more than others, that's a choice or a passion, not a point of drama ;)
Oh, nice nice.
Alright, bug found.
So...the arrow thats on the right side, beside "posted by: username"...will take you to the LAST recent post, correct?
Whenever I click that on this forum, it takes me to the first main post. :P
I believe the arrow will take you to the first new post (for you) in that thread vs the absolute last post. The old behavior was to take you to the last post.
Yeah but the last post is the newest, isn't it? Either way, it takes me to the first post, whether it was updated or not. :p
Seems to be taking me to the last post, not sure why its not working for you, I think its just a named anchor so the browser should just jump to that page point when the dom is loaded. :-\
Either my browser is on drugs, or yours is. :p
Dunno, works as expected here... :-\
Anyone else did see something like this happen?
Yep, yesterday when I wanted to register a new user via the registration in the admin center. Today I tried it again and it worked.
Second situation of this kind: today when I tried to save my changes to membergroups in two separate browser windows (in both I was logged in). Didn't worked, I couldn't save the changes. I closed the second window.
I meant the fact that the arrow brings you to the first message of the topic and not to the last one. ;)
BTW, about these errors you faced: are they "unable to verify URL", or maybe "token verification failed"? Because the "unable to verify URL" is quite an odd error to see in normal usage... :-\ Even when multiple windows are open...
Oops! :-X
It's "token verification failed" in my case.
Token failed is "kind" of normal in certain conditions.
The tokens are a security feature that (simplifying) allows to submit a form only once, that way, if you are tricked to submit data of a form by an hacker or so, it's very difficult to get the token right, and most likely you'll face the token verification failed.
Unfortunately, you'll get the same error if for example you submit a form, receive an error and you use the "back" button of the browser to go back, because what happens is:
Elk generates a token and adds it to the form
you submit the form
first thing that Elk does is check if the token is correct, if it is, the token is invalidated and the program proceeds
Elk generates an error maybe because you set something wrong and gives you the "fatal error page" with the "back" button
if you use the browser's back button, you will come back to the original form, but this form contains the token that has been invalidated
you re-submit the form
* Elk verifies the token, but it finds it was invalidated and gives you the "token verification failed" error.