? Success

User tests: Successful: Unsuccessful:

avatar podlom
podlom
31 Jul 2015

To fix SQL errors such as:
Save failed with the following error:
You have error in your SQL syntax; check the manual corresponds to your MySQL version for the right syntax use near 'AND sha1_hash = '...' LIMIT 0, 1' at line 3 SQL=SELECT * FROM dbprefix_ucm_history WHERE ucm_item_id = 1 AND ucm_type_id = AND sha1_hash = '...' LIMIT 0, 1
You are not permitted to use that link to directory access that page (#1).

avatar podlom podlom - open - 31 Jul 2015
avatar podlom podlom - change - 31 Jul 2015
Status New Pending
avatar joomla-cms-bot joomla-cms-bot - change - 31 Jul 2015
Labels Added: ?
avatar zero-24 zero-24 - change - 2 Aug 2015
Title
Update base.php
Prevert SQL errors where the UCM type id is not set
avatar zero-24 zero-24 - change - 2 Aug 2015
Category SQL
avatar zero-24 zero-24 - change - 2 Aug 2015
Title
Update base.php
Prevert SQL errors where the UCM type id is not set
avatar zero-24
zero-24 - comment - 2 Aug 2015

@podlom can you give us testinstructions how we can reproduce the issue? So we can test that this patch fix it?


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7596.

avatar podlom
podlom - comment - 3 Aug 2015

Yes, sure. We had Joomla version 3.1.5. We have updated it using admin (/administrator/index.php?option=com_installer&view=update) to 3.4.3 and then updated Database using (/administrator/index.php?option=com_installer&view=database). Then we have tried to edit any article in Content ---> Article Manager we got such SQL errors.

avatar zero-24 zero-24 - change - 3 Aug 2015
Title
Prevert SQL errors where the UCM type id is not set
Prevent SQL errors where the UCM type id is not set
avatar brianteeman brianteeman - change - 13 Apr 2016
Status Pending Closed
Closed_Date 0000-00-00 00:00:00 2016-04-13 17:35:54
Closed_By brianteeman
avatar brianteeman
brianteeman - comment - 13 Apr 2016

As it has been almost a year since this was created and we are now on Joomla 3.5.1 with no other reports I can only assume that this was an isolated bug related to your own installation. So I am closing this at this time. It can always be reopened if further information can be provided how to replicate this with a clean install of Joomla 3.5.1


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/7596.

avatar brianteeman brianteeman - close - 13 Apr 2016

Add a Comment

Login with GitHub to post a comment