Page Builder Image Sources

I have an open discussion with them now regarding the missing 'Images and Links' tab on front end editing, to which there has thus far been no response. When you enable this option in the Articles > Options > Editing and Layout (this is off by default) the Helix UI breaks - it looks like compuserve c. 1986.

https://i.postimg.cc/kg5rkD6M/frontend.png

They absolutely need to fix this. No update to Helix since 1.1.2 January 2020, before the plague.

That is really frustrating. I was thinking I am going to convert my customers to Page Builder just to find out it doesn't even pull the Joomla article images. It is really mind-boggling.

You can use PageBuilder in any major Joomla template system so you can still bring them into SPPB - it is the best at what it does, in my opinion. I use SPPB in every website I administer, using a variety of template producers - but I have two in development that will require front end editing so unless this is addressed soon, the production sites will be built over one of the alternates (I am prototyping in triplicate).

Hi Alex. My thoughts - personally, I never use Helix Blog Image. I use only standard images for Joomla articles. This is all that should be done to avoid the problem. I do not find any sense in the Helix Blog Image functionality.

@Pavel The problem is from the front end, Helix Ultimate "Images and Links" tab is not properly implemented. After you enable "Frontend Images and Links" in Articles > Options to bring up the "Images and Links" tab we see on the back end, the front end Helix Ultimate UI is completely broken (image). So the problem is that Helix Ultimate front end core Joomla editing is missing this key functionality.

I have two sites in development that will absolutely rely on this functionality, so unless Joomshaper updates its current (and future?) Helix framework to include this, these sites will enter production using a different framework. As it stands, I have tested T4 successfully (note the images and links tab) with untrained editors having no problem, so despite my absolute preference for Helix Ultimate, it's not hard to see where this could be headed if Joomshaper doesn't finally address this longstanding issue.

EDIT: this is not an SPPB issue, as the T4 example is using SPPB - the best pagebuilder in the business.

Hi blue_Shift. Thanks I got it. Never use the front interface, so I did not know about it.

Hi guys,

I found a workaround for the articles addon. I'm going to try it on the articles vertical slider addon now.

I basically had to manually change the site.php file located in the addon folder in the right spot. I set the $image variable to pull from joomla's core intro image field.

(It seems like there is actually an issue displaying ANY images using the articles and articles slider addon. (It doesn't seem to be affecting the articles category display page menu's; just the module addons used by PB.) I'm using the latest version of PB on joomla 3.9 and php 7.4. I wonder if there is an issue with the image helper classes up the tree that the addons use to set the $image variables...)

Honestly, i think setting these to pull from the core joomla intro article images would be better; seeing as most people do not use the Blog tab in the article editor to choose images. It would be nice if the Joomshaper Helix Blog images parameters would pull the images to crop from the Joomla core intro or full image fields. A lot of sites that are currently using this method would work out of the box.

Anyways... here is the workaround i posted on the question i had in the forums. Hope it might help until they can fix what seems to be a bug.

https://www.joomshaper.com/forum/question/1696

Thanks :)

Hi blue_Shift,
I never us the PB frontend so I went ahead and gave it a try and i can concur that it is a big issue that should be fixed immediatelly. When you say longstanding, how much time are we talking about? Because if they are not giving any attention at all to this issue, I will be forced to move on as well.

Hi Danny,

Thanks for posting a workaround, I will surely look into it today. You might have saved me a lot of headaches for a project I am currently working on.