Migx with Gallery not rendering thumbs correctly with image tv in Revo 2.2.7

28 Posts

littleseal Reply #1, 13 years, 4 months ago

I've recently upgraded a few sites from Revo 2.2.6 to 2.2.7 . PHP 5.3.23. Migx 2.4.3, Gallery 1.5.2

I set the Migx image tv media source to 'Gallery' and when I use the image browser in the migx tv for viewing the Gallery the thumbs are not created so the full image size shows.
This is only with media source set to 'Gallery', it's fine with media source set to 'File system' and it's only with Revo 2.2.7.

One other issue after upgrading to Revo 2.2.7 on a Zen internet server is that when I upload an image using TinyMce within the Migx tv and save it I can't then reopen that field item, the loading gif stays and a Error notice appears saying 'Forbidden is not defined: Forbidden'. This only occurs when uploading an image!
The suhosin value was increased to 4096 and permissions to the migx connector.php are recusively 755.

Any ideas? [ed. note: littleseal last edited this post 13 years, 4 months ago.]

5,888 Posts

Bruno17 Reply #2, 13 years, 4 months ago

I set the Migx image tv media source to 'Gallery' and when I use the image browser in the migx tv for viewing the Gallery the thumbs are not created so the full image size shows.

what's the image-src then?

One other issue after upgrading to Revo 2.2.7 on a Zen internet server is that when I upload an image using TinyMce within the Migx tv and save it I can't then reopen that field item, the loading gif stays and a Error notice appears saying 'Forbidden is not defined: Forbidden'. This only occurs when uploading an image!
The suhosin value was increased to 4096 and permissions to the migx connector.php are recusively 755.

didn't try to upload images with tinyMCE inside MIGX. So I can't say what happens there at the moment.

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

28 Posts

littleseal Reply #3, 13 years, 4 months ago

Thanks for looking into this Bruno.

The image src:

Modx 2.2.7 doesn't include image width and height and images are full size:

<div class="modx-pb-thumb">
<img title="Budget 2013" src="/assets/components/gallery/connector.php?action=web/phpthumb&src=%2Fassets%2Fgallery%2F3%2F63.jpg">
</div>

Modx 2.2.6 works fine and includes image width and height:

<div class="modx-pb-thumb">
<img width="90" height="90" title="Hugos Restaurant" src="/modx/assets/components/gallery/connector.php?action=web/phpthumb&src=%2Fmodx%2Fassets%2Fgallery%2F3%2F2.jpg">
</div>

28 Posts

littleseal Reply #4, 13 years, 4 months ago

The forbidden notice only happens when I upload an image into the TinyMCE RTE then save it, with no image saved in the RTE it's absolutely fine and I've realised this occurs with both Modx 2.2.6 and 2.2.7 with one particular host but it's fine with other hosts, both running PHP 5.3. This really suggests it's down to server settings NOT Migx

Firebug Console Post statement:
http://mysite.co.uk/modx/assets/components/migx/connector.php 403 Forbidden

So I think this isn't a MIGX issue but any suggestions to what might be restricting access in the PHP settings?

5,888 Posts

Bruno17 Reply #5, 13 years, 4 months ago

Quote from: littleseal at Jun 03, 2013, 03:01 PM

Thanks for looking into this Bruno.

The image src:

Modx 2.2.7 doesn't include image width and height and images are full size:
<div class="modx-pb-thumb">
<img title="Budget 2013" src="/assets/components/gallery/connector.php?action=web/phpthumb&src=%2Fassets%2Fgallery%2F3%2F63.jpg">
</div>
Modx 2.2.6 works fine and includes image width and height:
<div class="modx-pb-thumb">
<img title="Hugos Restaurant" src="/modx/assets/components/gallery/connector.php?action=web/phpthumb&src=%2Fmodx%2Fassets%2Fgallery%2F3%2F2.jpg" height="90" width="90">
</div>

what are the tpl-chunks for both, what are the output-options for this TV-field in both?

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

28 Posts

littleseal Reply #6, 13 years, 4 months ago

Field in Migx tv input options form tabs for both:

{"field":"image","caption":"Image","inputTV":"imageTV"}

imageTV output-options for both set to 'default' and media-source set to 'Gallery'

Not sure what tpl-chunks you're referring to as they aren't introduced at this stage as it's a TV linked to a template in a resource.

28 Posts

littleseal Reply #7, 13 years, 4 months ago

Just to clarify what the Modx browser looks like:

Modx 2.2.7 with full size images, no thumbs

Modx working fine 2.2.6

For a quick fix I've just altered the CSS in manager default index.css file, adding height and width.

.modx-pb-thumb img {
    vertical-align: middle;
    height: 80px;
    width: 100px;
}

[ed. note: littleseal last edited this post 13 years, 4 months ago.]

28 Posts

littleseal Reply #8, 12 years, 7 months ago

An update on the forbidden notice...
I've SOLVED the issue when editing a migx tv item and receiving error: Unexpected token <:Forbidden, Firebug console shows a 403 forbidden when attempting to access /assets/components/migx/connector.php.

It's a mod_security setting on the server that restricts the inclusion of coding, in my case html elements other than the 'p' element, in the JSON string with an ajax request. My hosting company, Zen internet, whitelisted the ModSec rule ID and applied it to my account only, as the site is on a shared server.

I hope this helps anyone with a similar issue.

5,888 Posts

Bruno17 Reply #9, 12 years, 7 months ago

Thanks Charlie, for reporting about the source and solution for your issue.

-------------------------------

you can buy me a beer, if you like MIGX

http://webcmsolutions.de/migx.html

Thanks!

☆ A M B ☆
165 Posts

lithiumlab Reply #10, 12 years, 6 months ago

This problem is still present.
I've tried modxcloud instance with 2.2.14 with latest Gallery 1.6.2.
Using a regular image tv with Gallery Media Source.
thumbnails are not being generated correctly

The result is the same as the screenshots above

This seems nothing to do with MIGx

Any work arounds?