Detective work please.....The weirdest problem I have had with C5.6???

Permalink
Your help please.

I started with an old version (5.4) which I have upgraded now as part of my bug fix attempts. After everything I reverted all files to yesterdays backup.

The CAUSE

As far as I am aware nothing changed.

The only event may have been months ago when the host changed php settings however they changed that back within a day and it was running on php 5.2 as it had been before. The client makes fairly basic amends to what its a pretty basic website. Maybe the PHP log (attached) shows something to those that understand it, from Dec 10th 2016?
The reason for the delay is no-one had logged in suvvesffuly to try and update the site.


THE SYMPTOMS

- client could login under their username but saw no edit bar
- super admin, I could login, see the admin bar but not edit. The edit bar showed and I could click and put into edit mode, but I could not exit edit mode. I could access the dashboard etc via the URLS I know
- the client then tried resetting their password a few times
- When visiting the Users page no pop up when trying to click edit came up. I could not remember exactly how 5.4 dealt with users but it felt some functionality which should show wasn’t

> I backed up and then
> I tried changing themes
> I tried changing the Php mode to 5.3 & 5.4 it stopped working on 5.4 totally so I reverted to 5.2 where all was fine on the front end.
> I looked at / updated the plugins, only one (accordion menu) was calling files in the homepage (although it wasn’t on that page) but I hid it and those file references were removed and no change. I then removed every addon one by one. Nothing.
> I setup a new user profile and tried logging in but that was the same as the client, nothing showed
> I tried Pretty URLs and not.

I upgraded to 5.6.3 (I did it via the upgrade path and nothing improved in the intermediate versions)

On 5.6.3

> Its the same, I can login but if try to edit any page you are redirected to the homepage. That page looks like it is in Edit mode, with the layout being surrounded by the edit red dashes, however the Edit button is not free. You can click the Edit button but it has a think. You can scroll over areas n the page and but no pops show. You cannot log out / publish changes however the rollout menu top left offers, properties/ permissions / version etc
> If I click on Properties / design etc etc they all pop up but say Access Denied.
> If I go to Users and add a new profile I can add the profile to the administrator group. If I then select the new username and use the dropdown for edit properties, it works. However if I select Add to Group it shows the popup, I select the Admin group and save and it goes back to the user list (but the background is translucent (see attached image) and it feels something odd has happened.
> If I tried using my totally new profile, I log in, it searches for updates and news (that overlay works file). The homepage then has the edit bar, but no Edit buttons are available (see attached).
> If I try and edit the layout (not the blocks) on the homepage, the popup for the Tables does show, however if I try and make a change it says {"msg":"Access Denied."}


All in its very confusing, I think it must be some odd permissions error I don’t understand. I appreciate it also looks like a Jquery issue but as it happens with the default theme on a Jqeuryless page, I just can’t work it out.

I think maybe the php log might show (to someone who understands) what may have gone wrong in Dec as they updated the

I ended up resting the site to its initial state as I had removed add ons and messed things up when trying to fix it.

This is the site:http://www.williechristie.com, back in its original form, which worked for years until December.

2 Attachments

 
hutman replied on at Permalink Reply
hutman
This sounds like it could be a variety of things, but the first thing I notice when I access your site is a javasript error "Uncaught SyntaxError: Unexpected token <" which appears to be a missing javascript file -http://www.williechristie.com/home/js/am_menu.js...

Also, have you tried to clear the cache? Sometimes that does amazing things.
JohntheFish replied on at Permalink Reply
JohntheFish
In addition tom the script error, I noticed <meta name="generator" content="concrete5 - 5.4.2">

Perhaps there was an incomplete upgrade at some point.
ConcreteOwl replied on at Permalink Reply
ConcreteOwl
You are calling the am_menu.js and the am_style.css twice!

Correctly in your head like this
<link rel="stylesheet" type="text/css" href="/packages/accordion_menu/blocks/autonav/templates/accordion_menu_burble/css/am_style.css?v=06121050f133b9001a1f643b1f674fa5" />
<script type="text/javascript" src="/packages/accordion_menu/blocks/autonav/templates/accordion_menu_burble/js/am_menu.js?v=06121050f133b9001a1f643b1f674fa5"></script>

And incorrectly in your sidebar like this
<div id="l_sidebar">
         <script src="js/am_menu.js" type="text/javascript"></script>
<link rel="stylesheet" type="text/css" href="css/am_style.css" />

To fix this remove the am_menu.js and the am_style.css calls from your sidebar
ConcreteOwl replied on at Permalink Reply
ConcreteOwl
I also notice a call for jquery.min.js in your head that could be clashing with concrete/jquery.js
Try commenting out this line in your head
<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js" type="text/javascript" charset="utf-8"></script>
tobyme replied on at Permalink Reply
Thanks all for taking a look.

Whilst the JS is far from perfect I am pretty convinced this is a permissions / token issue somehow or in the database as the backend behaves oddly. Not just on themed pages.

Iad done these things before but reverted to the original version, so now:

I have disabled and cleared the cache
I removed the AM menu altogether
I have run the update to 5.4.2
I have implemented the Plain Yogurt Theme now

On permissions I realise in the sitemap when I and delete a page it also says:

<b>Invalid form token. Please reload this form and submit again.</b>

I don't know how the token / login works but I think something really odd has a token permanently logged in and locked out the site for editing possibly? I have looked at resetting sessions in the archive and removed TMP session files but nothing has changed.

Here is the HTML of the home page when logged in:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
        "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<!-- Site Header Content //-->
<link rel="stylesheet" media="screen" type="text/css" href="/tools/css/themes/default/main.css" />
<link rel="stylesheet" media="screen" type="text/css" href="/tools/css/themes/default/typography.css" />
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<title>Willie Christie :: Willie Christie</title>
<meta name="description" content="" />
<meta name="generator" content="concrete5 - 5.4.2.2" />
<script type="text/javascript">
var CCM_DISPATCHER_FILENAME = '/index.php';
var CCM_CID = 1;
var CCM_EDIT_MODE = true;
tobyme replied on at Permalink Reply
Also I wonder if this section of the PHP errorlog means anything relevant to someone who knows it? John?

016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Area::getOrCreate() should not be called statically in /home/williech/public_html/concrete/models/block.php on line 63
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Area::get() should not be called statically in /home/williech/public_html/concrete/models/area.php on line 153
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::get() should not be called statically in /home/williech/public_html/concrete/models/area.php on line 121
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::key() should not be called statically in /home/williech/public_html/concrete/libraries/cache.php on line 116
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::getLibrary() should not be called statically in /home/williech/public_html/concrete/libraries/cache.php on line 120
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::key() should not be called statically in /home/williech/public_html/concrete/libraries/cache.php on line 136
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::get() should not be called statically in /home/williech/public_html/concrete/models/block.php on line 67
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::key() should not be called statically in /home/williech/public_html/concrete/libraries/cache.php on line 116
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::getLibrary() should not be called statically in /home/williech/public_html/concrete/libraries/cache.php on line 120
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method Cache::key() should not be called statically in /home/williech/public_html/concrete/libraries/cache.php on line 136
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method PermissionsCache::exists() should not be called statically in /home/williech/public_html/concrete/models/permissions.php on line 69
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method PermissionsCache::getIdentifier() should not be called statically in /home/williech/public_html/concrete/models/permissions.php on line 15
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method PermissionsCache::getObject() should not be called statically in /home/williech/public_html/concrete/models/permissions.php on line 70
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method PermissionsCache::getIdentifier() should not be called statically in /home/williech/public_html/concrete/models/permissions.php on line 45
[10-Dec-2016 10:39:01 CST6CDT] PHP Strict Standards:  Non-static method PermissionsCache::exists() should not be called statically in /home/williech/public_html/concrete/models/permissions.php on line 69
JohntheFish replied on at Permalink Reply
JohntheFish
It could be the host is running on a php version too advanced for c5.6. Perhaps it is running php7 ?