Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

Install under Joomla 3 failed #35

Open
creactiv opened this issue Mar 12, 2014 · 4 comments
Open

Install under Joomla 3 failed #35

creactiv opened this issue Mar 12, 2014 · 4 comments

Comments

@creactiv
Copy link

It says: 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 'SET =1 WHERE ='otrsgateway' AND ='plugin'' at line 1 SQL=UPDATE SET =1 WHERE ='otrsgateway' AND ='plugin'

Any idea how to fix that? I am looking into the combination of OTRS and Joomla; and i am really excited about this combination, since other tools also can be connected to Joomla. So this really would make sense for me. Nevertheless, will you be able to update the connectors to more recent otrs and joomla versions?

Thanks for your work :-)

PS: MySQL Version is 5.1.73, PHP is 5.3.2

@lbourne43
Copy link

Hi creactiv

Thanks for your interest. Sorry, we don't have support for Joomla 3 yet but this is something that we plan to add in the future.

Regards
Lewis

@creactiv
Copy link
Author

Well, do you have a time Frame? And could you perhaps assist how to fix that MySQL Problem?
Thank you for your quick reply.
Best

@lbourne43
Copy link

We don't have a time frame yet but we are happy to assist you with any problems that you come across. The issue that you are seeing is the result of a change in Joomla 3 to the object returned by JFactory::getDBO(). It's method: 'nameQuote()' has been removed and replaced with another called 'quoteName()'. The usage is the same so you can just open up joomla_1.6/com_otrsgateway/install.otrsgateway.php and change the '$db' method from 'nameQuote()' to quote name where it is used on lines 37-40. eg:

$tableExtensions = $db->nameQuote("#__extensions"); 

becomes:

$tableExtensions = $db->quoteName("#__extensions");

After this change the installer should run without error but Joomla versions are radically different from one another so you are likely to come across more problems.

@ChuckNorrison
Copy link

Solution in #39

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants