-
- 718 Posts
In svn trunk all fixed.
In change log i see [#MODX-289] Fixed MODx Parse Error in module dependencies tab. (4069)
But i can’t understand, how 0962 was born? There so much bugs...
[#MODX-289] NOT fixed in 0962 from download page.
>:(
also.. image path in manager. I made a few patches. but it was missed..
[#MODX-185] SET NAMES vs SET CHARACTER SET issue IS NOT resolved. Somebody read jira?
I dont have problem with this, i made modx for my self without this bugs.
But what "mortal" people need to do with this ?
There is a separate discussion about MODX-185, and it will be resolved. Also see MODx-289 for discussion on that subject. 0963 will be out to address any outstanding issues such as this.
What bug are you referring to with the image path in the manager?
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
-
- 194 Posts
When trying to ’Manage Dependencies’ on the modules page I’m getting a
« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - Table ’modisk.smd’ doesn’t exist »
SQL: SELECT smd.id,COALESCE(ss.name,st.templatename,sv.name,sc.name,sp.name,sd.pagetitle) as ’name’,CASE smd.type WHEN 10 THEN ’Chunk’ WHEN 20 THEN ’Document’ WHEN 30 THEN ’Plugin’ WHEN 40 THEN ’Snippet’ WHEN 50 THEN ’Template’ WHEN 60 THEN ’TV’ END as ’type’ FROM smd LEFT JOIN `modisk`.`modx_site_htmlsnippets` sc ON sc.id = smd.resource AND smd.type = ’10’ LEFT JOIN `modisk`.`modx_site_content` sd ON sd.id = smd.resource AND smd.type = ’20’ LEFT JOIN `modisk`.`modx_site_plugins` sp ON sp.id = smd.resource AND smd.type = ’30’ LEFT JOIN `modisk`.`modx_site_snippets` ss ON ss.id = smd.resource AND smd.type = ’40’ LEFT JOIN `modisk`.`modx_site_templates` st ON st.id = smd.resource AND smd.type = ’50’ LEFT JOIN `modisk`.`modx_site_tmplvars` sv ON sv.id = smd.resource AND smd.type = ’60’ WHERE smd.module=3 ORDER BY smd.type,name
is this what the issues discussed here are about ?!?
anyhow I don’t see differences between the code in the patch and the original one in0.9.6.2’s mutate_module_resources.dynamic.php file
The patch was to correct spelling mistakes (debobj --> depobj), but it did not get merged properly from the branch to trunk. This has now been done and we will release a follow-up shortly to solve this and a few other recent problems related to patches.
-
- 194 Posts
’b’ - ’p’ now I finally saw it!
...will wait for the .3 release!
-
- 23 Posts
So the topic is resolved, but how can I fix this? I’m using the latest version of Modx and still get the following error:
« MODx Parse Error »
MODx encountered the following error while attempting to parse the requested resource:
« Execution of a query to the database failed - Table 'qlt_wellness.smd' doesn't exist »
SQL: SELECT smd.id,COALESCE(ss.name,st.templatename,sv.name,sc.name,sp.name,sd.pagetitle) as 'name',CASE smd.type WHEN 10 THEN 'Chunk' WHEN 20 THEN 'Document' WHEN 30 THEN 'Plugin' WHEN 40 THEN 'Snippet' WHEN 50 THEN 'Template' WHEN 60 THEN 'TV' END as 'type' FROM smd LEFT JOIN `qlt_wellness`.`modx_site_htmlsnippets` sc ON sc.id = smd.resource AND smd.type = '10' LEFT JOIN `qlt_wellness`.`modx_site_content` sd ON sd.id = smd.resource AND smd.type = '20' LEFT JOIN `qlt_wellness`.`modx_site_plugins` sp ON sp.id = smd.resource AND smd.type = '30' LEFT JOIN `qlt_wellness`.`modx_site_snippets` ss ON ss.id = smd.resource AND smd.type = '40' LEFT JOIN `qlt_wellness`.`modx_site_templates` st ON st.id = smd.resource AND smd.type = '50' LEFT JOIN `qlt_wellness`.`modx_site_tmplvars` sv ON sv.id = smd.resource AND smd.type = '60' WHERE smd.module=2 ORDER BY smd.type,name
For those about to rock... I salute you
-
- 1,336 Posts
Use MODx, or the cat gets it!
MODX Staff
MODX Staff