Strange error message when including images in edit mode

Permalink
Hi folks

I have a strange error, if I try to include images (in edit mode) in a website.

After submitting the image in the overlay, we got a white page with the following error:
{"message":null,"title":null,"time":"2017-01-10 07:45:00","redirectURL":"","btID":"27","bID":"1367","arHandle":"Content : 44","aID":"140","cID":"1","pages":[{"name":"Home","cID":"1"}]}


The url in the address bar looks like this:
http://www.domain.com/index.php/ccm/system/dialogs/page/add_block/s...

Unfortunately, this error only appers when adding some images, other content elements are working perfectly. No errors in the Chrome debugging console found.

Informations from our concrete5:
# concrete5 Version
Core Version - 5.7.5.9
Version Installed - 5.7.5.8
Database Version - 20160615000000

# concrete5 Packages
None

We are using a PHP SCSS compiler, to compile SCSS to CSS. But the error still appears, if we deactivate this compiler.

Maybe anyone can help me out?

Thanks in advance.

Cheers, Marcel

 
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi marcelmarty,

You mention that this happens when adding images. How and where are you adding these images?
marcelmarty replied on at Permalink Reply
Hi

This error occurs, if I'd like to add a image to a defined Area (not a GlobalArea, but I think with global Areas this error occurs too).

The Area is defined like that:

<?php
defined('C5_EXECUTE') or die("Access Denied.");
$this->inc('elements/header.php'); ?>
<section>
    <?php
    $a = new Area('Corusel');
    $a->display($c);
    ?>
</section>
<section>
    <?php
    $a = new Area('Content');
    $a->enableGridContainer();
    $a->display($c);
    ?>


So it is a really basic template. I do not think that the template itself is the problem. Maybe there are some problem with includes in the header_top.php or something else?

Cheers, Marcel
Vuish replied on at Permalink Reply
Just as a hint for you.

I think I remember seeing this message in one of my projects. It had to do with our activated Google Pagespeed server module.

It turned out that Pagespeed combined/minified assets in a way Concrete5 didn't work smooth anymore. Not sure how we solved it. I think we excluded some assets from Pagespeed.

To solve your problem:
I would try to remove all custom JavaScript assets from your site and load only those assets required by Concrete5 by default. Maybe you load jQuery twice or the order of some custom loaded assets throw an error that prevent Concrete5 assets from doing their job.
Also disable combining/minification for your assets.