SPPB 4.0.6 Joomla 4.2 working on a subfolder of damain - Forum | JoomShaper
Solved SP Page Builder

SPPB 4.0.6 Joomla 4.2 working on a subfolder of damain

Asked by Luis Cepeda 3 years ago Last activity 3 years ago

I have a main domain site and running SPPB fine, I have a subfolder 2022 which is a redesign of the site I am working on, both sites are using their own database and configuration except 2022 is a folder inside the body of the main domain. I have set my email and license in both as required.

Issue:
1- When I try to add a predesigned block the entire library is block and it ask me to buy the pro version.
2 - When I click on save &close by the menu, it sends me to the front end of the main domain

3- If I click back to admin i takes me back to the correct admin page, which is good.

WHy is this happening? I have added both domains to my domain list in my account as well.

Thanks

Luis

Accepted answer

Marked as the solution
Anne Staff
3 years ago

Hello there,

Thanks for contacting us. I have cleared the joomla cache. It seems fine now. I have attached the screenshot in hidden content. Please clear this cache: https://prnt.sc/10tlQqAGcaeN

-Regards

5 more replies

Oldest first Newest first Most helpful
Luis Cepeda Asked this
3 years ago

Thanks!, that seem to have fixed it.

Fabian W.
3 years ago

Hi there,

I discovered the bug on working with a subfolder like example.com/new-site
Everytime I hit "save & close" / "close" it takes me back to example.com/ what caused in a 404 failure cause "index.php" did not exist in the domain root.

"Back to admin" is working fine.

Any ideas how to fix it?

Luis Cepeda Asked this
3 years ago

That is exactly what happens on my site as well, Fabian and I have the same issues, even this may not be as important at least for me as I am just developing on the subfolder.

Anne Staff
3 years ago

Hello Fabian,

Please take our sincere apology. Would you mind to create a new forum post about your issue? It will help the other user to find solution for same problem.

-Regards

Paul Frankowski Senior Staff
3 years ago

If I may...

It should be fixed in upcoming 4.0.7 version. It on our list of bugs already.

Log in to reply.