Awaiting an answer SP Page Builder

htaccess-Issue after update to Sp Pagebuilder 4.0.6

Asked by Dresden Hepcats e.V. (c/o Michael Fiedler) 3 years ago Last activity 3 years ago

Hello,

after the most recent update to SP Pagebuilder 4.0.6 (also true for the latest version of 3.x.x) we are getting an http 404 error on the while attempting to edit a website on the frontend.

Error message: GET https://www.dresden-hepcats.de/dev/index.php?option=com_sppagebuilder&view=form&id=40&layout=edit-iframe&Itemid=492&lang=* 404

This appears to be due to htaccess - disabling it gets it working again. Currently, we have the following lines in htaccess, which worked so far:

########## Begin - SP Page Builder
RewriteRule ^administrator/components/com_sppagebuilder/(.*)$ - [L]
RewriteRule ^components/com_sppagebuilder/(.*)$ - [L]
########## End  - SP Page Builder

Are you aware of any change, which requires an update of the htaccess rules. What do we need to adjust in htaccess to get it working again?

Thanks in advance,

Sascha

7 replies

Paul Frankowski Senior Staff

3 years ago · edited

Hi Sascha,

To be honest those lines which use used were suggested by offcial Akeeba Support, that's why we added them into SPPB documenation as well few months ago.

About security aspects of those lines - probably you have to talk with Web Security Experts or Akeeba Support.

Dresden Hepcats e.V. (c/o Michael Fiedler) Asked this

3 years ago

Hello Frank,

acutally I did the research myself a few months ago. If you look up my previous tickets you'll find out, that I suggested the lines to be included in your docs.

Frankly, speaking I am quite dissatisfied with the developer support provided here. The last time I had to find the solution for myself, as well. Other extension providers (e.g. Akeeba) are capable of providing support on security aspects of their extensions. They give instructions what their extensions require, also in terms of htaccess.

In the case of SP Pagebuilder support, I have the feeling that there is not even an intention of trying to fix the issue together with the customer, rather the customer is asked to find the solution with someone else (this is not our responsibility).

Sorry, but my expectation is that the extension developer provides support for such security issues and what needs to be configured in htaccess. Especially in light of error messsages which provided.

Dresden Hepcats e.V. (c/o Michael Fiedler) Asked this

3 years ago

Hello,

I would like to add a question, which will hopefully help to move forward: what directories and files on the webserver need to be accessible by the edit request above (GET https://www.dresden-hepcats.de/dev/index.php?option=com_sppagebuilder&view=form&id=40&layout=edit-iframe&Itemid=492&lang) which causes the http 404 error.

Having the knowledge on the required files and directories could help to adjust the htaccess file and allow for editing the frontend having the htaccess file activated.

Kind regards,

Sascha

Dresden Hepcats e.V. (c/o Michael Fiedler) Asked this

3 years ago

Hello Frank,

is there any news any news on my request :-).

Kind regards,

Sascha

Paul Frankowski Senior Staff

3 years ago · edited

There are over 1000 extensions for Joomla conflicts are natural thing, that's why in Support Policy we have information that we cannot solve all of them. Especially if we talk about security extenions that "block" everything they can. Private I use RSfirewall and all works fine. Akeeba Tool Pro is specific tool, that sometimes it locks even Super User... weird.. but happends :( so must be used only by Advanced Webmasters, with nerves of steel!

Paul Frankowski Senior Staff

3 years ago

Please check if you get error 404 also with default Joomla .htaccess (not changed by Akeeba Tools)

if no, you have to talk with Akeeba support, sorry but problem (maybe) is caused by their software , not ours!

Dresden Hepcats e.V. (c/o Michael Fiedler) Asked this

3 years ago

Hello Frank,

I think there is a misunderstanding - I manually edited the htaccess-file to allow for proper access to sp pagebuilder. Though Akeeba admin provides the functionality edit this, it comes with the paid version only which we do not have installed. Therefore, it is not a conflict with a third party extension.

We use a custom htaccess file, which is restrictive, yes. But I don't think that this is the problem here. I can adjust it, but therefore I need to know what paths sp pagebuilder needs to have access to.

Apart from that - do you see another psossibility to get some logging apart from HTTP 404 when editing the file in frontend? This could possible help to troubleshoot the required access.

Regards,

Sascha