@SELECT binding - {PREFIX} doesn't work

My first post to this great community!

I made a list type TV and write follwing query in insert options referring this page.



This was expected to get ids and longtitles from children of document 2, but it actually shows error not finding table ’{PREFIX}site_content’.
{PREFIX} doesn’t get replaced.

I had looked through templvars.commands.inc.php, guessed and use [+PREFIX+] instead. ...And now it’s working fine.

It could be only in my situation, but posting this just in case the documentation isn’t correct.

Good catch Shiro; I actually changed that a while back and had forgotten about this. This was so that you could set placeholders in a snippet elsewhere on the page and then use the values in the SELECT statements. I hope it is useful, and sorry for not keeping the documentation in sync. We’re trying to develop a better strategy in that area and if you have any ideas or contributions, please don’t hesitate...

Cheers!

Thanks OpenGeek,

I’m still struglling to get used to the MODx way, but am definetely liking it!
I’ll see what I can do to like it more!

Glad this post was here, from over 2 years ago.
Documentation on this page
http://modxcms.com/select-binding.html
still incorrectly tells users to use {PREFIX}

I was bitten by this issue about 6 weeks ago - I reported it as a bug on the 3rd June, and only just had a response today.

I wish it wouldn’t take so long to get a reply (in this case over a month) just for an answer as simple as "replace { } with [ ]" !

Quote from: Pandy06269 at Jul 09, 2008, 04:27 PM

.. I reported it as a bug on the 3rd June, and only just had a response today.

Pandy06269: That was me who responded to your ticket in Jira today. I was only able to do so because I came across this problem 2 days ago.

Ah, thanks for that.

Do the developers actually monitor Jira then? Cause I’ve had a couple of tickets raised with no response, and a couple of others you’ve responded to but no feedback from the developers?

netProphET is one of the developers. JIRA is definitely monitored.

I can’t speak for other devs, but for me, the biggest factor is that this is volunteered time and we all need to pay our bills and feed our kids (or fish or whatever). I tend to go for long periods of time without having much time to pay attention to what’s going on in the forums or in Jira.

Ultimately, (and obviously) the project would benefit from more developer-hours. Lots of talented people are already contributing what they can, so that means more developers are needed, and that’s what the Guiding Forces are working on. A lot of core-dev energy has been going into 0.9.7. This "technology shift" is not only aimed at building a better MODx for users, but at attracting developer talent. I think the strategy is very sound.

I am positive you’ll see an acceleration of activity and responsiveness to Jira issues as these seeds take root.

Documentation corrected.