Hi,
I have migrated a test website to Joomla 4 and now, If I use Joomla module addon to display a joomla module, like a contact form, does not work.
I get this.
See here : https://prnt.sc/JRojt1qifYgL
What's wrong?
Thanks
L.
Solved
SP Page Builder
unable to display joomla module after joomla 4 migration
Asked by Laurent
4 years ago
Last activity 4 years ago
Accepted answer
Marked as the solution
Toufiq Senior Staff
Our product developed for the Joomla and it's not compatible with the PHP 8. We are working on PHP 8.0 compatible. Until release PHP 8.0 compatible, Please stay with the PHP 7.4. Thanks
21 more replies
Laurent Asked this
It seems that the problem is not linked to joomla module addon because when I edit a page, the error appears directly : https://prnt.sc/wNh2C2YpzE36
Laurent Asked this
also addon bloc cannot be displayed : https://prnt.sc/Gw2jPR9ELKun
Toufiq Senior Staff
Hi there,
Thanks for contacting us. Sorry for the inconvenience. Will you please provide me the Joomla administrator access to check the issue? I will check & get back to you soon.
-Thanks
Laurent Asked this
see hidden content area
Toufiq Senior Staff
- Try to check the default module of Joomla inside the module addon (Instead of third party module)
- Disable the rocket_loader from the cloudflare SSL or mod_security from your hosting server to solve the block issue.
Laurent Asked this
-
see this video : https://screencast-o-matic.com/watch/c31Yi9V37RB
-
this test website is not behind cloudflare service.
Toufiq Senior Staff
I have checked your site on my localhost and everything is working fine. I think your server blocked to load resource of page builder. Thanks
Laurent Asked this
OK I see.
I have tried the same on localhost on my computer and I have the same issue.
does not work.
where can I have a look?
Laurent Asked this
other info : this demo website is installed on the same server where other websites are running and I do not have this issue. but those websites are running on J3 and not J4.
Laurent Asked this
I have changed php version on the server.
I did a rollback on php 7.4.x and works fine.
when I go back to php 8.0.x the problem is coming back.
here are my php settings : https://prnt.sc/w6lpMysh5dMW
Toufiq Senior Staff
PHP 8.0 is not ready. Please stay with PHP 7.4. Thanks
Laurent Asked this
for SP page builder for joomla 4?
Laurent Asked this
ok no problem.
for your info, If I use php 7.4, works but error is displayed on console :
see here : https://prnt.sc/P3eNUiEBc_-R
Jens W.
Hello Laurent,
this is a known problem i had reported some time ago.
There is CSS put into a script-tag and leads to this error.
administrator/components/com_sppagebuilder/helpers/sppagebuilder.php:137
$doc->addScriptDeclaration('.tox-tinymce-aux {z-index: 130012 !important;}');should be
$doc->addStyleDeclaration('.tox-tinymce-aux {z-index: 130012 !important;}');If you change this line, the error will no longer occur.
Laurent Asked this
ok thanks for the feedback.
I assume joomshaper team will fix it for a next release to avoid a css hack ;-)
Jens W.
The problem is already fixed in 4.x and i don't think there will be any other release of 3.x anymore before 4.x stable release.
I reported this problem in january for version 3.8.3.
Since then no fix from joomshaper.
Toufiq Senior Staff
@jens We are working on Page Builder 4 & that's why takes time so long. Please stay with us. Thanks
Laurent Asked this
thanks ;-)
Toufiq Senior Staff
You are most welcome :)
Jens W.
One last addition to this and sorry @Laurent for my complains.
@jens We are working on Page Builder 4 & that's why takes time so long. Please stay with us. Thanks
Since january "reported for 3.8.3", when i reported the issue, they where not able to replace a functionname and fix it.
@Toufiq I really understand, that this big rewrite of a product takes a lot of time and capacity.
But a simple replace of a functionname, which takes only 1 minute for a developer, should be possible in 3 updates. :)
And thank you for providing 50% discount to all new customers.
@both have a nice week :)
Toufiq Senior Staff
@jens I understand the sitituation. We will try to improve it. Thanks
Log in to reply.