Hi,
there is a bug on Page Builder 5.0.8. My version of Joomla is 4.3.3.
On the heading widget it's impossible to manage the responsive preferences: the choice of the device in which display the widget content doesn't work. An example of a page in which the problem occurs is the following: https://appartamentilemuse.it/offerte-sconti-promozioni-per-le-tue-vacanze-in-umbria.
Moreover on the heading widget cited above it's impossible to choose the Goole Font: it is possible to choose only a very little number of fonts.
I send you the access to the site so that you can verify by yourself.
Can you please help me fix this bug?
Thanks in advance for the support.
Best regards.
Problems with Heading widget of Page Builder 5
4 replies
Hi there,
I appreciate you reaching out. I sincerely apologize for this oversight. I just exported your module JSON file and checked on my localhost. It works fine on end my end. No clue found why happen this problem. Initially solved your issue by adding custom css class.
-Thanks
Sorry but the problem still exists.
As you can see in the screenshot below inside the Page Builder Module "Offerte" there are four headings alternatively hidden and shown on mobile. The ones called "MOBILE" and "Mobile" are shown on mobile and the others are shown on desktop.

On the frontend, however, the ones that I see are the first two heading, no matter what the advanced/responsive elements settings are on the backend. In the image below the text "PACCHETTI & OFFERTE" for desktop devices should be shown, but it is hidden despite its settings on the backend.

Please check and let me know. Thanks
Sorry but the problem still exists.
please look at the screenshot below:

The text highlighted on the image is the one displayed by the heading widget highlighted below:

As you can see it should be hidden on desktop devices, and instead it results visible. This happens for every heading widget no matter how I modify the responsive visibility preferences.
Check again. Thanks
Hi,
no: the responsive settings of the module simply don't work.
Many thanks.
We will improve it. I just shared your issue to our developer team. I will get back to you soon. Thanks