Logging out redirect/permissions issue ongoing on 5.6
Permalink
Hi
The love affair with Concrete 5 is coming to an end sadly as 5.6 doesn't seem to have a upgrade to 5.7 and I am having a huge array of bugs on the many sites I've done over the past few years in 5.6. Mainly to do with logging out and access denied errors that seems to be resolved on taking out the .htaccess redirect code and turning off pretty URL's but this isn't sustainable and we can't expect clients to do this. Is there any workaround for this? It manifests itself by access denied issues if you try and do anything on the site sometimes if you publish and then go back in it works but it is happening on a number of sites. Any ideas anyone?
The love affair with Concrete 5 is coming to an end sadly as 5.6 doesn't seem to have a upgrade to 5.7 and I am having a huge array of bugs on the many sites I've done over the past few years in 5.6. Mainly to do with logging out and access denied errors that seems to be resolved on taking out the .htaccess redirect code and turning off pretty URL's but this isn't sustainable and we can't expect clients to do this. Is there any workaround for this? It manifests itself by access denied issues if you try and do anything on the site sometimes if you publish and then go back in it works but it is happening on a number of sites. Any ideas anyone?
I have notice that user permissions sometimes get scrambled on sites that have been through many generations of core upgrades. But on fresh 5.6.x install/upgrades to 5.6.3.3 I have not encountered any such issues.
Hi John
Thanks for your comment - how do you do a 'fresh install' I usually have been doing them through the site itself. So its saying the site is up to date but I somehow suspect its something to do with this.
Thanks for your comment - how do you do a 'fresh install' I usually have been doing them through the site itself. So its saying the site is up to date but I somehow suspect its something to do with this.
Install - for a new site install I usually just put the zip in the filespace and unzip it.
Update - depends on the site. I usually use the dashboard update, then use the force option if necessary to make sure it has fully completed.
However, on any non-trivial site I usually use the overall process described in the howtohttps://www.concrete5.org/documentation/how-tos/developers/organise-... . Core version update is then just part of an overall process of cleaning and streamlining a site.
Update - depends on the site. I usually use the dashboard update, then use the force option if necessary to make sure it has fully completed.
However, on any non-trivial site I usually use the overall process described in the howtohttps://www.concrete5.org/documentation/how-tos/developers/organise-... . Core version update is then just part of an overall process of cleaning and streamlining a site.
This may not be relevant but...
I've seen a similar thing happen with a couple of sites we had running on Heart Internet shared hosting.
The problems we had were related to caching issues - particularly on the login page.
With the sites in question I altered the caching so it wouldn't cache the login page and added a little code to the login controller to empty the site cache on login.
I've seen a similar thing happen with a couple of sites we had running on Heart Internet shared hosting.
The problems we had were related to caching issues - particularly on the login page.
With the sites in question I altered the caching so it wouldn't cache the login page and added a little code to the login controller to empty the site cache on login.
Hi Andy this sounds highly possible as I'm on shared hosting what was the code that you added would you be willing to share?
sure - let me dig it out...
Hi Andy
Got these coming in thick and fast - I'd be really grateful for that snippet of code if you can dig it out. Many thanks in advance...
Got these coming in thick and fast - I'd be really grateful for that snippet of code if you can dig it out. Many thanks in advance...
