No Code Attached Yet bug
avatar catwired
catwired
4 Aug 2025

Steps to reproduce the issue

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

Expected result

A new Article will be saved.

Actual result

A php error results upon saving a new Article.

System information (as much as possible)

See this Post for my FPA results: https://forum.joomla.org/viewtopic.php?f=834&t=1019750

Additional comments

See this Post for the fix: https://forum.joomla.org/viewtopic.php?f=834&t=1019750

Votes

# of Users Experiencing Issue
1/1
Average Importance Score
1.00

avatar catwired catwired - open - 4 Aug 2025
avatar catwired catwired - change - 4 Aug 2025
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 4 Aug 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 4 Aug 2025
avatar catwired catwired - change - 4 Aug 2025
The description was changed
avatar catwired catwired - edited - 4 Aug 2025
avatar chmst
chmst - comment - 5 Aug 2025

This is not Joomla, it is a 3rd party extension. Please contact the developer.

avatar Webdongle
Webdongle - comment - 5 Aug 2025

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?

avatar chmst
chmst - comment - 5 Aug 2025

Thank you - I cannot reproduce the error on my applications, but woll re-check.

avatar chmst
chmst - comment - 5 Aug 2025

Thank you - I cannot reproduce the error on my applications, but will re-check.

avatar chmst
chmst - comment - 5 Aug 2025

Thanks again to you and @toivo. Interesting .. this newPublished and newpublished exists since 6 years :) and nobody noticed.

avatar chmst chmst - change - 5 Aug 2025
Labels Added: bug
avatar chmst chmst - labeled - 5 Aug 2025
avatar brianteeman
brianteeman - comment - 5 Aug 2025

Thanks again to you and @toivo. Interesting .. this newPublished and newpublished exists since 6 years :) and nobody noticed.

and nobody else had such an easily reproducible error or can replicate this error

avatar chmst
chmst - comment - 5 Aug 2025

Something in the environment which is sensible for capitalisation

avatar richard67
richard67 - comment - 5 Aug 2025

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?

avatar richard67
richard67 - comment - 5 Aug 2025

Anyway, the suggested fix is right.

avatar richard67
richard67 - comment - 5 Aug 2025

I'm just preparing a PR with a fix ... I've slightly modified the suggestion.

avatar richard67 richard67 - close - 5 Aug 2025
avatar richard67
richard67 - comment - 5 Aug 2025

Closing as having a pull request. Please test #45848 .

@catwired If you know someone who also can reproduce the issue, e.g. from replies to your forum post, please ask them to test the pull request, too.

Thanks in advance.

avatar richard67 richard67 - change - 5 Aug 2025
Status New Closed
Closed_Date 0000-00-00 00:00:00 2025-08-05 18:57:31
Closed_By richard67

Add a Comment

Login with GitHub to post a comment