Forums

Error when saving page or block

Permalink
Hi all you fab folk....

We have come across a very strange error, not sure what has caused it. We upgraded to 5.7.5.13 but it didn't seem to happen straight away.

When we save a page or block after editing a new tab is opened that is just white with the following text: 
{"message":null,"title":null,"time":"2017-03-24 15:40:48","redirectURL":"","aID":"18166","arHandle":"Main Dark","bID":"16749","cID":"1588","pages":[{"name":"Page Name","cID":"1588"}]}


Then if I return to the previous page and click save again, it throws the following error:
Exception Occurred: /home/titania/public_html/updates/concrete5.7.5.13_remote_updater/concrete/controllers/dialog/block/edit.php:48 Call to a member function getInstance() on a non-object (1)


Which refers to : $bi = $b->getInstance(); in the above file.

I am totally confounded, any ideas very welcome :)

Thanks in advance!

Ben
BHWW
 
mnakalay replied on at Permalink Reply
mnakalay
Hello,
The problem with the blank screen and the lines of data you are getting was reported but hasn't been fixed yet. It seems it is intermittent and hard to pinpoint.

But when you come back to the previous page, you don't need to save again. My understanding is the saving was already done as what you see is not an error, it's just the wrong data being shown on screen

So technically if you just come back to the previous page and reload the page then ppublish the page you should see your edit
contactoicograf replied on at Permalink Reply
contactoicograf
I have the same error in one of my sites, as @mnakalay says everything its made when you returning to the site, although this causes confusion.
Hopefully they will fix this bug soon.
zanedev replied on at Permalink Reply
zanedev
Did anybody ever find a fix for this? I'm seeing the same thing on a site after transferring to a new server. It is not happening locally but happens with every save or add block on the server.
zanedev replied on at Permalink Reply
zanedev
Okay I figured it out for anybody else that comes across this here is the solution. The reason it was not working on the new server was because we were forcing `x-frame-options` to `deny` in our apache ssl.conf for additional security (common practice nowadays).

The edit/add block dialogs all use an iframe so the browser could not read the json response even though the json appears valid in the console. The empty error dialog is because the code for the dialog is not outputting the native js error, it only outputs error messages set from the application.