Install Joomla 3.7.5
Install Yootheme Pro 1.9.6
Create with the Pagebuilder a Element, that contains images
Set the width and height for the images in the element
With Joomla 3.7.5 the images are shown
After an Upgrade to Joomla 3.8.0 RC1 the images not shown
PHP 7.1
MySql 5.7
Before Upgrade: Joomla 3.7.5 Stable
Joomla 3.8 RC1
Posted this also here: http://yootheme.com/support/question/114582
I tested Joomla 3.8 RC1 + Yootheme Pro 1.9.5 and if you set the width or height for images (not for Background images), the images are not shown anymore. If you use Joomla 3.7.5, there is no Problem.
This is ok: src="/xxx/templates/yootheme/cache/auto-crash-18d5e554.png"
But the srcset are broken: srcset="//xxx/xxx/templates/yootheme/cache/auto-crash-18d5e554.png
The //xxx doesn't belong there.
Labels |
Added:
?
|
Category | ⇒ | Plugins |
Status | New | ⇒ | Information Required |
@ufuk-avcu cause Comment above can you please close Issue?
Hey. I just thought that this could be relevant from BC's point of view if the behavior changes in other extensions as well.
Status | Information Required | ⇒ | Discussion |
If it can be isolated what specifically changed, we can look into the issue. The report lacks any detail to be able to do anything.
Core doesn't do anything to generate srcset
attributes by default. #15300 added support for processing srcset
in the system SEF plugin in full, so maybe that change affected the Yootheme handling. But that is IMO hardly a B/C break.
I can confirm that this is a bug in the core joomla SEF plugin implementation. The same behaviour can be noticed in DJ-MediaTools gallery which also uses srcset attribute. The relative site path is added to image url no matter if image url contains it already what creates doubled relative path at the beginning of the image url.
Status | Discussion | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-09-19 05:09:58 |
Closed_By | ⇒ | franz-wohlkoenig |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17919
closed as having Pull Request #17978
They've replied: