Joomla 3 ошибка при сохранении

• 8 Ответов
• 2106 Просмотров
• 

On a pretty new site, something has happened that has caused articles to give following error message upon saving (on frontend only)

Save failed with the following error: Invalid Parent ID

In search for a solution, I found that one reason for the error is that the category tree structure has gotten messed up for some reason and there seems to be many solutions. I first tried the following:

• Rebuild all menu item
• Rebuild all categories
• Refresh all categories by edit and save/close
• Refresh all articles by edit and save/close

As otherwised explained in this article:
https://www.joomla-tips.org/joomla-troubleshooter/save-failed-with-the-following-error-invalid-parent-id.html

Iv’e also tried to create a temporary category and move all categories under it and back to root as explained in this article:
https://www.itsupportguides.com/knowledge-base/joomla-tips/joomla-save-failed-with-the-following-error-invalid-parent-id/

However none of this seems to work. It is only when editing or creating articles on frontend I get this error message. Never been a issue when doing the same on backend, where it saves without any error.

Last thing I tried was to install the ACL Manager extension which also has a diagnostic tool to fix issues with assets tables. One was detected with com_category. However fixing it didn’t solve it either.

Any help appreciated.

asked Aug 25, 2017 at 10:54

Maybe you are using Falang component? In my case only soultions was update PHP to 7.0 or 7.1
This problem exists since of Joomla 3.7.3 — it’s all I know…

This is indeed a issue caused by the Falang Componenet (2.9.1) with Joomla 3.7.3+.

The issue seems to be a problem with php 5 and the query used by Joomla in assets tables.

One way of fixing this is to update to php 7.0+ as @Tomasz Malinowski mentioned.

However updating to php 7.0+ can cause other errors if your site is not ready for it, as was my case.

So if you need to keep php 5 (in my case 5.6) then this fix works until a new version of Falang is released with a official fix.

In …/libraries/joomla/table/asset.php line 110 replace

->select('1')

with

->select($this->_db->quoteName('id'))

For Joomla 3.8+ the above line to replace is located in …libraries/src/Table/Asset.php line 99

answered Aug 30, 2017 at 21:38

On a pretty new site, something has happened that has caused articles to give following error message upon saving (on frontend only)

Save failed with the following error: Invalid Parent ID

In search for a solution, I found that one reason for the error is that the category tree structure has gotten messed up for some reason and there seems to be many solutions. I first tried the following:

• Rebuild all menu item
• Rebuild all categories
• Refresh all categories by edit and save/close
• Refresh all articles by edit and save/close

As otherwised explained in this article:
https://www.joomla-tips.org/joomla-troubleshooter/save-failed-with-the-following-error-invalid-parent-id.html

Iv’e also tried to create a temporary category and move all categories under it and back to root as explained in this article:
https://www.itsupportguides.com/knowledge-base/joomla-tips/joomla-save-failed-with-the-following-error-invalid-parent-id/

However none of this seems to work. It is only when editing or creating articles on frontend I get this error message. Never been a issue when doing the same on backend, where it saves without any error.

Last thing I tried was to install the ACL Manager extension which also has a diagnostic tool to fix issues with assets tables. One was detected with com_category. However fixing it didn’t solve it either.

Any help appreciated.

asked Aug 25, 2017 at 10:54

Maybe you are using Falang component? In my case only soultions was update PHP to 7.0 or 7.1
This problem exists since of Joomla 3.7.3 — it’s all I know…

This is indeed a issue caused by the Falang Componenet (2.9.1) with Joomla 3.7.3+.

The issue seems to be a problem with php 5 and the query used by Joomla in assets tables.

One way of fixing this is to update to php 7.0+ as @Tomasz Malinowski mentioned.

However updating to php 7.0+ can cause other errors if your site is not ready for it, as was my case.

So if you need to keep php 5 (in my case 5.6) then this fix works until a new version of Falang is released with a official fix.

In …/libraries/joomla/table/asset.php line 110 replace

->select('1')

with

->select($this->_db->quoteName('id'))

For Joomla 3.8+ the above line to replace is located in …libraries/src/Table/Asset.php line 99

answered Aug 30, 2017 at 21:38

I’ve had this working in the past (earlier version of Joomla), but must have changed something and I can’t get it work (even in a brand new site). I’m using Joomla 3.4.8, the newest version of JCE, and DirectPhp.
I have Global Configuration > Text Filter Settings > Super Users set to No Filtering, and have adjusted JCE Administration > Editor Profiles > Default > Editor Parameters > Advanced > Allow PHP to yes.

Yet, when I save a any article with Php code I get a 403 error. Without the php code it saves correctly.

Does anybody have any hints?

asked Mar 2, 2016 at 23:06

Many of our clients are facing the same problem. It turned out it is related to their host forcing browser caching on non-static content. Please follow the guide here ( http://www.itoctopus.com/how-to-disable-browser-caching-in-joomla-backend ) and add the appropriate code to the .htaccess file to prevent browser caching. Please post back here if it fixes your problem or not.

One way around this that I worked out was to edit the php code in PHPmyAdmin directly.

It seems that mod_security on your apache server is causing the error to be forced when either your code is bad or is restricted. (this is not a bad thing as it stops hacking attempts on your site really.)

Going through phpMyAdmin requires a bit more skill but works all the same.

Anyway that is what I do now when I encounter this issue. (the hard part is finding what is causing the error in the first place)

Probably mod_security is set to block PHP injection attacks, and it sees that as one. The way to tell is check the apache error log and the mod security audit log. Then, if you have access to the config files, you can configure an exception based around either that url or that variable to whitelist it from PHP injection checks.

WARNING: If you do that, be sure the code handling that form will be able to defend itself from injections, because you just stopped apache from defending it.

But the best solution for this is to write a plugin you can invoke from the content item, rather than inject all that code into your content. Makes it easier to maintain — changes are localized instead of scattered across lots of database records. Change the plugin once and every page that needs it gets the change, instead of having to touch each and every item in the db to make that same change.

PS: There’s a Joomla Stack Exchange. Check the list (top right, at time of writing).

answered Jul 12, 2019 at 15:47