Invision Community 4: SEO, prepare for v5 and dormant account notifications By Matt Monday at 02:04 PM
DReffects2 Posted December 4, 2020 Posted December 4, 2020 (edited) So i am having all kinds of strage template related issues lately. For example: <img src='{file="$record->_record_image_thumb" extension="cms_Records"}' alt="{$record->container()->name}"> did NOT output the URL in the src="" property but instead gave a base64 encoded data stream src='data:image/webp;base64,UklGRmgIAABXRUJQVlA4IFwIAADQIACdASpaAEoAPm0uk0akIiGhK9RsMIAN I've disabled all sorts of caching within IPS, checked the templates, rebuilt stuff, etc. Also i found that if I output the URL in HTML before the <img> tag like this <p>{file="$record->_record_image_thumb" extension="cms_Records"}</p> <img src='{file="$record->_record_image_thumb" extension="cms_Records"}' alt="{$record->container()->name}"> the value in src="" would be in fact the correct URL to the /uploads directory, not some base64 encoded data. (This makes no sense at all to me...) Turns out that the Google PageSpeed apache module started to modify the html code during output somehow. I do not know if this behaviour is normal. I've disabled the PageSpeeds module for now and all my problems are gone... Can anyone verify this or suggest a different PageSpeed configuration? I am running the affected site on a Centos8 machine with Plesk 18 and Google PageSpeed is in its default configuration as provided by the Plesk extension library. I am using PHP 7.4.13 Thanks... Edited December 4, 2020 by DReffects2
CoffeeCake Posted December 4, 2020 Posted December 4, 2020 Yes, that's part of the optimizations it can make. https://www.modpagespeed.com/doc/filter-image-optimize
Recommended Posts