Thread

Hi EE community,

I’ve run into a problem with my EE 2.1.3 installation whereby I cannot get any publish layouts to save.

I change a publish layout (logged in a super admin), choose the super admin user group, hit save, the layout briefly flashes white but no confirmation dialogue appears at the top of the control panel. When I reload the publish page for that channel, the layout is still in its initial state. If I try removing the layout for that channel/user group, a confirmation is displayed at the top of the control panel and the layout resets. But I’m back to square one and still cannot get any layouts to save.

I have not always had this problem, although I have found the publish layouts to be a bit flakey (i.e. layouts are saved, but appear slightly differently upon being reloaded).

I have tried Safari and FF5, emptying all browser caches, emptying all EE caches, deleting publish layouts as mentioned. But I cannot get a single layout to save (on any of my channels).

Any help would be fantastic.

Best,
Will Rice

I have now updated to 2.2.2, but the problem persists. I’m now assuming it must be due to a database problem :( or a plugin or extension. But I’m not running many at all.

PLUGINS:
Loop Plugin 1.2
Magpie RSS Parser 1.3.5
Session Variables 1.1
TweetLine 2.3
XML Encode 1.3

EXTENSIONS:
reCAPTCHA 1.0.0
SafeCracker 2.1

Any help greatly appreciated….

Could anyone tell me… on a normal working installation, does the control panel display a confirmation message at the top of the control panel for a successful publish layout save operation, or does it just save without a confirmation?

It is also possible that my web hosting provider (eukhost) have blocked some .php activity as they have rather stringent security measures and I am occasionally blocked by the firewall. But I don’t know which .php scripts are involved in the publish layout saving operation so it’s hard for me to ask them specific questions about whether their firewall may be responsible.

Can anyone tell me which scripts are responsible for the save operation and also if there are any log files that might offer me some clues as to what’s going wrong…

Thanks!

The problem did in fact turn out to be down to my web host’s firewall:

[Sun Oct 09 17:13:47 2011] [error] [client XX.X.XXX.XXX] ModSecurity: Access denied with code 406 (phase 2). Pattern match “\\\\%(?![0-9a-fA-F]{2}|u[0-9a-fA-F]{4})” at ARGS:json_tab_layout. [file “/usr/local/apache/conf/modsec2.user.conf”] [line “20”] [id “950107”] [msg “URL Encoding Abuse Attack Attempt”] [severity “WARNING”] [hostname “www.—————.co.uk “] [uri “/admin.php”] [unique_id “TpHIO9XlU5AAAAQ1a0UAAAAf”]

They added an exception rule that will hopefully stop it re-occuring.

Glad you are up and running again. Feel free to start a new thread if you have any more questions.