saved TV data disappear when reopen to edit

hi guys

it looks like i have a missfunction, bug or something with one of my TVs I created
so, here it is in a nutshell what I did and what is not functioning or causing anomalies:

I have many product pages which have certain properties. In order to make it as flexible as possible to maintain,
I created a TV in which I have given all types of properties available. I used the following settings:

• Input Type: Check box
• Input option values: 1 rétegben fed||1 vagy maximum 2 rétegben fed||beltéri||csepegésmentes||csiszolandó||ecsetelhető vagy hengerelhető||fogazott glettlappal||géppel-felhordható||gomba- és rovar ellen||görgőszék-álló||gyorsan kész||keverőszárral||kézzel felhordható||kültéri||lég- és páraáteresztő||mosható||padlófűtéshez||rugalmas||simítóvassal||színezhető||targoncázható||több komponensű||vegyszerálló||vízlepergető||vízzáró és viszszigetelő||vízzel higítandó (and so on, in my case there are words and phrases which contain hungarian characters as well since it is a hungarian website)
• Default value: empty


• Output type: delimiter
• Delimiter: ,

When editing the product page and selecting (check box) few properties then Save, everything looks to be ok on both backend and frontend sides.

And the problem:
When want to reedit the page, under Template Variables tab, some of the previously selected and saved properties look to be deselected. Prior doing anything, I checked the db in which all previously saved data are still stored correctly.
In my opinion it is either a bug or some kind of missfunction or caching issues might be involved, I couldn’t figure out.

I would appreciate if someone would test it himself on his MODX platform. If you create the same TV, just play with it a bit and let me know if you also encounter similar missfunction. I also checked the hungarian characters, which are OK everywhere, right collation in db, all charcaters appear correctly in the db and so on..

I use MODX vers 2.08 -pl
MySQL client vers: 5.0.51a

Caching settings:
Everything set to Yes except
Enable Database Cache, Disable Global Cache Options, Cache JSON Data, Refresh Trees on Site Cache all these set to No

I am very curious what the problem might be. A bug?

thanx in advance

MySQL 5.0.51a is not supported by MODX (or other modern CMF/CMS) due to some major flaws related to GROUP / ORDER BY statements if I recall correctly.

With limited knowledge of how MySQL actually works I can imagine saving would be fine (just an UPDATE) but retrieving the data could very well use those statements to gather data to populate the TV.


I’d suggest starting by asking your host to update MySQL..

hi Mark

You might be very right
I just checked myself again all the requirements for MODX to function smoothly and it is clearly specified that there are major issues with MYSQL vers 5.0.51 http://rtfm.modx.com/display/revolution20/MySQL+5.0.51+Issues

thanx again for your support
we will update our MySQL version asap

Quote from: Mark at Apr 27, 2011, 04:52 PM

MySQL 5.0.51a is not supported by MODX (or other modern CMF/CMS) due to some major flaws related to GROUP / ORDER BY statements if I recall correctly.

With limited knowledge of how MySQL actually works I can imagine saving would be fine (just an UPDATE) but retrieving the data could very well use those statements to gather data to populate the TV.


I’d suggest starting by asking your host to update MySQL..

hi Mark

it looks like the problem persist even after the MySQL update. We updated to client version 5.1.41 -3ubuntu12.9-log
could you eventually test this issue on your platform?

we are very curious if it is a bug or something else we couldn’t figure out till now

thanx in adv

That’s the client version. The problem is in the server version, which is what’s actually running the database. The client version only provides the interface to access the database. Two different things; ideally they should be the same version.

hmmm

despite all our effort, this problem looks to be a never ending situation

I am listing exactly what versions we use:

• MODX vers 2.08 -pl
• PHP Version 5.3.2-1ubuntu4.7
• Apache 2.0 Handler
• Server version: 5.1.41-3ubuntu12.9-log
• MySQL client version: 5.1.41

it looks like all requirements are met but still whenever we select the items in the TV involved, after reedit it looks like forgetting the previously selected values as I described in the first post

could anyone make a test on his platform? I would highly appreciate

if it would work on someone else’s platform, I would agree that there is something wrong at our side, otherwise it could be a major issue

waiting for your support and thanx in advance

I’m unable of reproducing this on my own 2.0.8 site..

MySQL 5.0.91
PHP 5.2.14

Quote from: Mark at Apr 29, 2011, 11:29 AM

I’m unable of reproducing this on my own 2.0.8 site..
MySQL 5.0.91
PHP 5.2.14

Hi Mark

Thanx for the effort. Today we have tried this TV by changing hungarian characters to latin, for ex instead of ’ö’ we used ’o’ or ’a’ instead of ’á’ and so on. In this case everything worked just ok.
As I mentioned in one of my previous posts, our db collation, including collations in table fields are set to utf8-hungarian, so theoretically all settings are just ok still it looks like the CMS forgets previously set data selected in our TV.
We are curious if after all, is this a bug or there might still be something we didn’t notice.
So, I think it would worth paying more attention to this issue and see if there is a major problem which should be corrected not for us but for the whole community using this CMS.

I copied the exact values you posted, so it shouldn’t really affect it much. I think my DB has a collation of utf8-general-ci.

Maybe try recreating the TV with those values and see if it has any difference.

Quote from: Mark at May 01, 2011, 06:22 AM

I copied the exact values you posted, so it shouldn’t really affect it much. I think my DB has a collation of utf8-general-ci.
Maybe try recreating the TV with those values and see if it has any difference.

well
we just went through this as well by converting all collations to utf8-general-ci, still same problem
I think, now we have tried all options, simply can’t think of any other alternatives but in case you have some other idea, I would highly appreciate. There is definitely something which doesn’t handle correctly non-latin characters, in hungarian, especially the ’ő’ and ’ű’ characters.
Probably a debugger would reveal this problem.