Problem in the new public release of 0.95

when using the $modx->getFullTableName() function its giving the wrong output with my current install...

modx is using the DB mme_ with a prefix mme_ but when i use that function and or for example jot using it to get the jot table it giving this value `mme_`.modx_content where is should be `mme_content`...

HOW? can i fix this ASAP.??

What is the value of $table_prefix in your config.inc.php?

$table_prefix = ’modx_’;

Quote from: Aikdo at Dec 12, 2006, 11:36 AM

$table_prefix = ’modx_’;

That sounds like the problem, why is it set to modx_ if it is actually mme_ ?

[ Queues creepy, suspicious sounding music... ]

sorry my mistake...

its in a database mme_ and username is mme_ but the table prefix is modx_

however in that case i cant work out why my jot installation that came with the store wont work im get a SQL error

« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - 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 ’’ at line 1 »
SQL: UPDATE `mme_`.modx_jot_content SET title=’test’,content=’test test test’,createdon=’1165945726’,createdby=’-1’,secip=’81.110.100.71’,sechash=’02df286c6882ce88d52691e7a303eede’,uparent=’50’,tagid=’’,published=’1’ WHERE id=;
[Copy SQL to ClipBoard]

Parser timing
MySQL: 0.0095 s (16 Requests)
PHP: 0.0698 s
Total: 0.0793 s

I’m not familiar enough with Jot to give you a definite answer, but this appears to be a glitch in that snippet (not 0.9.5). So I would try posting your question in the Jot forum for a quicker reply. It seems to me that the SQL query should be:

UPDATE mme_modx_jot_content SET...

and it’s being created as

UPDATE `mme_`.modx_jot_content SET...

which just looks like a minor typing error in the script.

Someone more familiar with Jot can surely point you to where to correct this if that is indeed the problem.

EDIT: See OpenGeek’s post below...

The problem is with this part of the query...

WHERE id=;

Not sure why no id value is being set here, but this is definitely a Jot specific issue...

Quote from: pixelchutes at Dec 12, 2006, 11:42 AM

[ Queues creepy, suspicious sounding music... ]

[ Stops the music. ]

I have the same problem, downloaded the new 1.0.1 from the repository and all is ok.