Hi, I told you Piotr, update rush is not always recommeded.

Temporray I installed you SPPB 3.8.2 - please keep it by now.

Front-end editor should work now. Please wait for SPPB 3.8.4 update.

If we talk about missing icons, because new SPPB uses Font Awesome 5 (not old FA 4.7) - you have to choose them again in those addons.

its working! fanks

Hi yesterday I was working with SP Page Builder on the content of my website, while editing, I refreshed the web browser, and an error appeared: https://agencja.jaro24.eu/edit/1.html

Warning: htmlspecialchars() expects parameter 1 to be string, object given in /components/com_sppagebuilder/parser/addon-parser.php on line 617

I tried to fix it with a new update to 3.8.3 from 3.8.2, but now Font Awesome 5 are missing again and there is a 404 error

please help, what should I do? Piotr

Piotr - tip #35 >> https://www.joomshaper.com/documentation/sp-page-builder/sp-page-builder-3/faq-problems-solutions#warning-htmlspecialchars-parser-addon-parser-php

I told you to keep 3.8.2, right?

I panicked ;)

0.o

when will the software version 3.8.4 be available?

in thist tip #35:

4. You have delete all php files from folder: templates/your_template/html/sp_pagebuilder

i dont have this folder "sp_pagebuilder" in "html"

that's no help.., here's a bug....

where is tip, help for Font Awesome 5 ? i searching on: www.joomshaper.com/documentation/sp-page-builder/sp-page-builder-3 I was looking on the site and also no help... ehh

no help for error "addon-parser.php on line 617" and no help for "Font Awesome 5" why?

when will the software version 3.8.4 be available?

This week

ABout Errors and missing Icons - it's problem with your template that overriden many our addons, also icon addon.

EVIDENCE / DOWÓD

FOnt Awesome 5 icons are working fine, Icon addon

Problem as I said before was caused by addons override by template.

Warning: htmlspecialchars() expects parameter 1 to be string, object given in /components/com_sppagebuilder/parser/addon-parser.php on line 617

Fixed, it was caused by Pie Progress addon override (!) And this was described in SPPB documenation.

In general it was help beyond support, because all issues were caused by template developer (ThemeCanyon org).

ALL FIXED

Po polsku: W dużym uproszczeniu napisanie addonów w szablonie, to jest jak używanie zamienników dla części w samochodzie. Działają, ale z czasem coś się psuje i sypie się całe auto. Także de facto to ja usunąłem te zamienniki dając możliwość Joomla używać orginalne cześci. Tym samym wyręczyłem twojego developera od szablonu. W normalnym warszacie to powinna być płatna usługa, ale cóż... Mam nadzieje, że wszystko jasne. Ale faktycznie przepraszam, gdzieś mi twój ostatni post umknął, stąd opóźnienie. Błędy się już nie wyświetlają.

thank you very much

You're welcome.

Please mark topic (one of the answers) as solved.