Login to backend of Joomla as Super User.
Create a new Article.
Save the newly created Article.
Upon saving, you will get a server error page.
I did find this error:
Save failed with the following error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') GROUP BY c2.id) AS c2 SET state = c2.newpublished WHERE id = c2.newI' at line 6
A new Article will be saved.
A php error results upon saving a new Article.
See this Post for my FPA results: https://forum.joomla.org/viewtopic.php?f=834&t=1019750
See this Post for the fix: https://forum.joomla.org/viewtopic.php?f=834&t=1019750
| Labels |
Removed:
?
|
||
| Labels |
Added:
No Code Attached Yet
|
||
This is not Joomla, it is a 3rd party extension. Please contact the developer.
According to @toivo https://forum.joomla.org/viewtopic.php?f=834&t=1019750#p3750671 editing Joomla's file libraries/src/Table/Nested.php solves the issue
However, this issue is caused by a genuine bug. Change the string 'newpublished' in line 1474 to 'newPublished' and the query should now work:
->set("$published = " . $this->_db->quoteName("c2.newPublished"))
Or are you saying a badly written 3rd party extension is causing that line to be interpreted incorrectly?
Thank you - I cannot reproduce the error on my applications, but woll re-check.
Thank you - I cannot reproduce the error on my applications, but will re-check.
| Labels |
Added:
bug
|
||
Something in the environment which is sensible for capitalisation
It might depend on the collation of the information_schema database. On standard installations it is _ci (case insensitive), and normally one should not change that, but maybe we have a different collation here?
Anyway, the suggested fix is right.
I'm just preparing a PR with a fix ... I've slightly modified the suggestion.
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-08-05 18:57:31 |
| Closed_By | ⇒ | richard67 |
I've meanwhile found some information in MySQL documentation which could be helpful to identify an environment where the issue could be reproduced, or at least explain why it cannot be reproduced for most people:
@catwired Could you report back which OS your database server is running on, and could you check and report back the value of the "lower_case_table_names" system variable? The latter can be obtained e.g. in phpMyAdmin with the SQL statement SELECT @@GLOBAL.lower_case_table_names;;
This is not Joomla, it is a 3rd party extension. Please contact the developer.