Support Offline : Mon - Fri / 10am - 6pm (GMT +6)

Your Time: Our Time:

Page builder background image path issue in Compress CSS for production

Featured Lock Resolved Bug
Production-ready template - SP Eventum template by JoomShaper on SP Page Builder and Helix3 Framework. Starting point was Quickstart dated June 2019 with all updates applied to bring it current.
Template modifications complete, including using SPPB Row Options to load row background images in css.

Switch SP Page Builder - switch to Production - no issue.
Switch SP Eventum Template built with Helix Frameowrk to Compress JS - Works as advertised.
Switch SP Eventum Template built with Helix Frameowrk to Compress CSS - All css linked images are now 404

An image that was linked via the path:
/images/venue/venue-bg.jpg
Now is trying to be loaded via the path:
/media/com_sppagebuilder/css//images/venue/venue-bg.jpg
I would work around the issue by moving the dozen background images to where the software wants to find them, but the resulting path with a "//" in the middle is not a proper file location.
I don't understand why a concatination of various css files into one file and removal of whitespace would introduce a completely new path that has no relationship to either the joomla default images folder, nor the template's images folder.

Besides "Don't turn on Compress CSS", is there a solution to this issue? The Eventum template and SPPB are not new, and I am using only SPPB products in the template stack as setup in the Quickstart - I shouldn't be the first to be coming across this issue.

9 Answers

Toufiq - Staff

More than a month ago #Permalink
Hi there,

Greetings from JoomShaper for being with us & Thanks for your query. Your query is very important to us. Please follow my instructions to solve your issue. I hope it will help you solve your issue.

1. Don't use both(Page Builder production mode and Helix compression mode) feature at a time
2. Use the Page Builder production mode or Use the Helix compression mode

Note: Helix compression mode will be a problem while Template has been Overitted addon. I would suggest to you to use the Page Builder Compression mode

-Thanks

Duke S.

More than a month ago #Permalink
I would suggest to you to use the Page Builder Compression mode


This confuses me. If I use only Helix, how do I disable compiling the less/scss code in Page Builder when that is no longer necessary. If it keeps compiling, that creates overhead and keeps busting the cache as each new css file is compiled and creates a new source file to consolidate.

How do I follow the suggestion to use only Page Builder Compression mode - Simply switching to Production does not result in any consolidation of files. I have not seen a "Page Builder Compression mode" option, where do I find it?

FInally, as a practical matter, how to I make the compression apply to non Page-builder pages. Page Builder is designed to render only the component area of the page - what about css & js for modules that are outside of the component area? How do we make page builder take effect for parts of the page or other pages that are outside Page Builder's scope?

Keep in mind, it was not my weird idea to use these together - this is a template stack in a quickstart purchased from JoomShaper and it should be capable of rendering a website with combined and minified css and js for all pages. So, how do we do this? And/or troubleshoot the weirdness so Helix can do what it is designed to do correctly without being corrupted by Joomshaper's own Page Builder product that is packaged with it? We need to reach "done" which includes not requiring 12 http requests when one will do.

Tell me where to start looking for the issue / where and why a new image path gets injected into the css.
I have to agree with Duke S. , there is a strange issue with production mode and image paths. Although I am a long time user of Joomshaper framework and pagebuilder, I used the build-in compression and minify options for the first time. Why does it change the paths?!? IMHO, both options should work together. I consider this as a bug.

Al Mamun - Staff

3 weeks ago #Permalink
Hi,

It was fixed. Can you please tell me which Helix and Page Builder version are you using?

Thanks,
Mamun
Can you please tell me which Helix and Page Builder version are you using?


PageBuilder Pro 3.6.2
Helix3 2.5.6

Al Mamun - Staff

3 weeks ago #Permalink

PageBuilder Pro 3.6.2
Helix3 2.5.6


It was fixed in Helix Ultimate not Helix3. It will fixed in Helix3 next update.

Thanks,
Mamun

Duke S.

3 weeks ago #Permalink
@Pepperstreet - Thank you for joining into this thread and helping me get attention on this issue. I don't know why my detailed report was not worthy of attention, but glad you could help convince the staff that fixing the product was worthy of their attention. /D
@Pepperstreet - Thank you for joining into this thread and helping me get attention on this issue.

You're most welcome! I simply had the same issue, but forgot to post a topic. Fortunately I did a search and found your topic. Joining forces feels great! ;)
It was fixed in Helix Ultimate not Helix3. It will fixed in Helix3 next update...
Mamun


Great. Glad you still support and care about v3 !


There are no replies made for this post yet.
Be one of the first to reply to this post!

Leaderboard (30 days)

Paul Frankowski

Paul Frankowski

Total Accepted Answers: 109
Toufiq

Toufiq

Total Accepted Answers: 64
Sifat

Sifat

Total Accepted Answers: 44
Mehtaz Afsana Borsha

Mehtaz Afsana Borsha

Total Accepted Answers: 17
Rashida Rahman

Rashida Rahman

Total Accepted Answers: 17

118

Templates

305858

Community Users

Newsletter

Don’t miss any updates of our new templates and extensions and all the astonishing offers we bring for you.
We never spam

Joomla! ® name is used under a limited license from Open Source Matters in the United States and other countries. JoomShaper.com is not affiliated with or endorsed by Open Source Matters or the Joomla! Project.

Connect Us