Last post 7 hours 58 min ago

Posts last week 94

Average response time last week 34 min

All time posts 67914

All time tickets 10497

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#2685 – Issues logging in on the front end

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Thursday, 08 September 2016 20:01 UTC

holdsworthdesign

Hi,
We use sh404SEF on http://www.xxxx.ca/, and recently our client noticed that when logging in on the front end, they get this error message:

The most recent request was denied because it contained an invalid security token. Please refresh the page and try again.

I've tried it myself, and I can log in once, and then after that, I cannot log in until I clear the session table in the database.

If I turn off URL optimization, then logging in happens without any issues.

Do you have any suggestions?

Thanks!

Friday, 09 September 2016 07:58 UTC

wb_weeblr

Hi

I have no information on this, and never had any report of such thing. I don't see how sh404SEF could be actually involved in it, however it happens that 3rd-party extensions do not work properly has they assume Joomla SEF is in place.

1 - What are your exact and full Joomla and sh404SEF versions?
2 - Could you please provide us with superadmin credentials to your website. You can create a temporary account, and delete it afterwards, but it must have superuser level.

Thanks and regards

Monday, 12 September 2016 19:28 UTC

holdsworthdesign

Hi,
I thought it was odd as well!

Here's login info:

http://www.xxxx.ca/
Username: xxxx
Password: xxxx

There's a link in the footer which takes one to the front-end login form.

Thanks for your help!

Tuesday, 13 September 2016 08:41 UTC

wb_weeblr

Hi

Actually that seems to be a bug in Joomla 3.6.x.

Rgds

Thursday, 15 September 2016 19:59 UTC

holdsworthdesign

Hi,

This isn't an issue with updating Joomla. It's already running 3.6.2.

The issue is specifically when logging in on the front end with sh404SEF running.

Thanks.

Friday, 16 September 2016 06:44 UTC

wb_weeblr

Hi

I didn't experience that, had no problem logging in on the frontend with the credentials you provided.

[xxxx]

Anything else I should know?

Rgds

Friday, 16 September 2016 20:25 UTC

holdsworthdesign

Hi,

I should have clarified, it gives the error when logging in a second time right after I log out.

Thanks.

Monday, 19 September 2016 08:04 UTC

wb_weeblr

Hi

OK. The thing is, I get the same behavior without sh404SEF enabled. It's a caching issue I'm sure (disabling the Page cache system plugin and joomla conservative caching makes the error disappear).

What's seems to be happening is that once this error happens (and it's normal that it happens sometimes), the error seems to be cached and redisplayed upon subsequent logins.

I don't think sh404SEF is actually involved in that, but I am afraid this is once again one of those things where we will have our hands dirty trying to find what's happening and what's the real cause.

If you provide me with an akeeba backup of the site, I can then download it and install a local copy, on which I can debug the PHP code and actually understand the problem. This is a lengthy process, so I would please ask before we engage in it that you fully update the site: currently there are 8 extensions that need to be updated. Please test afterward (and clear your browser cache: you have enabled Browser caching in the page cache plugin, so browser cache needs to be cleared each time)

Another important thing is that you use K2 2.7+, but you do not have the K2 sh404SEF plugin, which builds URLs for sh404SEF. I believe that's a requirement for proper operation of K2 and sh404SEF. I'm not sure if that relates to the problem at hand, but considering your site is the only one experiencing this, it's would good to fix all moving parts.

Rgds

Monday, 19 September 2016 19:47 UTC

holdsworthdesign

Hi,
Thanks for your help! With what you said, we were able to work around the caching issue and get things working. Thanks!

Tuesday, 20 September 2016 06:56 UTC

wb_weeblr

Hi

OK, glad to hear that. Please also take my remark RE: the K2 plugin into considerattion. There is no problem for existing URLs, but if you add K2 content to that site, the URLs created without the K2 plugin will not be nice, with /item/ in them.

Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.

Be sure to also check out wbAMP, our new Accelerated Mobiles pages plugin for Joomla - the next big thing is SEO, direct from Google themselves!

Rgds

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.