[frentix]

The problem was in /usr/share/wordpress/wp-content/themes/flexform/includes/plugins/aq_resizer-1x.php

On line 23

if( !file_exists($img_path) OR !getimagesize($img_path) ) return false;

the code exists silently without any error logging. The calling method outputs then empty <figure> elements to the DOM. If an error would have shown up in the apache error log we would have found the wrong configuration / missing link much quicker.

Would be great if you could improve the code there for other users as well.

Thanks.

[frentix]

Hello,

finally we were able to resolve the issue, it was a dead symlink somewhere in our filesystem.

We were only able to do so by changing the code to reflect where it was searching for the images. Maybe some kind of failsafe would be good, that one gets more than only an empty tag but maybe an error message in a logfile.

Thank you for your assistance,
Oliver

[frentix]

Good morning.

The hostingprovider, that would be us. We own a little server farm and everything works like a charm. WordPress does work on the server. Flexform too. It is just that it is not creating the links inside the <figure></figure> tags in the portfolio.

Are there any special requirements for this to work? We have
ubuntu 14.04
apache 2.4 – 2.4.7
php5 – 5.5.9
php5-gd – 5.5.9
libgd3:amd64 – 2.1.0-3

Any help would be highly appreciated!
Oliver

[frentix]

Hi Kyle,
sorry, we replied on the email instead of writing the answer in the support ticket itself.
best regards
Christian
————-
Hi Kyle,

Thanks for looking into this. It’s probably not be the GD img library:
# dpkg -l|grep libgd
ii libgd3:amd64
ii libgdbm3:amd64
ii libgdk-pixbuf2.0-0:amd64
ii libgdk-pixbuf2.0-common

We have noticed something else and are wondering if you can tell us what might have caused this:
<li data-id=”id-1″ class=”clearfix portfolio-item span4 standard services-openolat firmen “>
<figure>
<!– There used to be code in here, right? –>
</figure>
<div class=”portfolio-item-details”>
<h4 class=”portfolio-item-title”>Algordanza</h4>
</div>

We switched from Apache 2.2 to 2.4 last weekend.. unfortunately we cannot fix this without some help and hints, we do not really understand the inner workings of wordpress.

Thanks,
Oliver