SOLVED: bug in @select template variable section?

=> See my last post on page two for solution.

Hello All,

I’m making my first live MODx website, with Evolution v1.0.2, and enjoying the process.

With the 9x version I had managed to created an @Select binding to create a dropdown list for an editor to select a writer_id from a non-MODx table (in the MODx database). It had worked like a charm in 9x.

However, in 1.0.2, whenever I add the following values to the template variable section, and hit save, the right hand section of the Manager interface goes away, and I see the site home page. It happens with no warning of a data error. Then, when I go back to the TV page, the TV that I had just tried to save is not there.

I do believe that it’s a bug - because even if I was adding incorrect data, it should complain instead of the Manager section going away, without saving the data.

Note that I successfully created a regular text-input TV without a problem.

The @Select values I’m entering are:

- template var name: writer
- caption: writer
- input type: DropDown List Menu
- input option values: @select writer_id, byline from pub_writers
(I assume that the first field will populate the TV, with the second field for additional display?)

- default value: left blank
- widget: nothing selected
- correct template checked

I’ve spent hours on this, scouring the web and all the doc sites, thinking I was entering data incorrectly - but even if I was, I would think that the response on Save would be different.

Thanks for anyone’s help!

Peter Brown

Just tried it in 1.0.0 and it works just as you have it except that I used the site content table.
The first field is for display, the second as the value.

Dear David,

I just tried:

@select id,longtitle from modx_site_content

in the input option values field, and got the same result.

Maybe this is a bug in 1.0.2.

I hope it can get fixed - it’s a very critically needed function.

Peter

Peter, if you pasted that, you’re problem is that it needs to be @SELECT, not @select or @Select.

In 1.0.0 on MAMP it works as lower-case.
I thought that would be the issue, but maybe not.

Quote from: bunk58 at Nov 25, 2009, 04:36 PM

In 1.0.0 on MAMP it works as lower-case.
I thought that would be the issue, but maybe not.

I’m pretty sure that it’s case-sensitive in the version I have (under XAMPP), though I haven’t checked for a while.

Dear Bob,

I tried:

@SELECT writer_id,byline from pub_writers

with the same result. Bombed out.

Even if it was the wrong case, the save page should show an error, not just go away and show me the home page of the site.

Is this the forum to submit this as a bug, or is there a better way to get this bug
to the MODx developers?

Thanks,

Peter

To report bugs, and review other reports and status of them, sign up for a Jira account (third item at the top of this page).
KP

Dear KP,

Thanks; I reported it as a bug.

Peter

Hello All,

I don’t believe this issue is a specific bug in 1.0.2 now, because I did a clean install and didn’t see the bug.

However, it seems to exist when one upgrades from 1.0.0 to 1.0.2, which is what I did for a client.

The bug is in his upgrade, but not in my clean install.
I couldn’t start from scratch with him, because he had data - and now it’s in production.

Does anyone know if there are files that perhaps didn’t get overwritten on the upgrade? I followed the upgrade notes on the MODx website. As a note, I also noticed that on the list of snippets, between the two installs, the upgrade was organized differently, and not as clean.

So, I think I have to tweak some files or db settings, or something.
Any help would be much appreciated.

Thanks,

Peter Brown