MODx Evolution 1.0 RC Discussions

Great addition Max. Probably a drop-down list would be better. Patch it up and I’ll commit as usual. Russian translit files added already.

Quote from: rthrash at Jul 09, 2009, 02:25 PM

Great addition Max. Probably a drop-down list would be better. Patch it up and I’ll commit as usual. Russian translit files added already.

If you have some free time, look at my tickets in jira.

Hi, I really look forward to modx evolution (and of course revolution) There are 2 little issues that I came a cross lately.

I had a tiny problem with eform (modx-1.0.0-rc1 eform-1.4.4.5). The bug seems to be fixed in the newest version 1.4.4.6. That made me wonder, will the newest version of eform be included in modx-1? See http://modxcms.com/forums/index.php/topic,32896.new.html

The other thing is a problem with mcpuk browser. If somebody uploads an image with special character in the filename, the file will uploaded and saved with the specialchar. The problem is the mcpuk browser then only shows an empy directory. I once investigated a bit into that and found the corresponding code (2 lines), that should strip the special chars, but these 2 lines are currently commented out (in rc1). At this point I am unsure if this is a bug or by purpose, at least I didn’t find something in Jira. Do you think this is worth a bug?
http://modxcms.com/forums/index.php/topic,32666.msg201878.html#msg201878

eni

Quote from: eerne at Jul 09, 2009, 04:32 PM

Hi, I really look forward to modx evolution (and of course revolution) There are 2 little issues that I came a cross lately.

I had a tiny problem with eform (modx-1.0.0-rc1 eform-1.4.4.5). The bug seems to be fixed in the newest version 1.4.4.6. That made me wonder, will the newest version of eform be included in modx-1? See http://modxcms.com/forums/index.php/topic,32896.new.html

Committed at rev 5315

The other thing is a problem with mcpuk browser. If somebody uploads an image with special character in the filename, the file will uploaded and saved with the specialchar. The problem is the mcpuk browser then only shows an empy directory. I once investigated a bit into that and found the corresponding code (2 lines), that should strip the special chars, but these 2 lines are currently commented out (in rc1). At this point I am unsure if this is a bug or by purpose, at least I didn’t find something in Jira. Do you think this is worth a bug?
http://modxcms.com/forums/index.php/topic,32666.msg201878.html#msg201878

Yes it definitely is worth commenting on in JIRA.

@rthrash:
submitted an issue http://svn.modxcms.com/jira/browse/TINYMCE-10

Is it with this release easier to make multilangual sites? Or do you still have to use the tutorial from susan?

Quote from: DNA at Jul 10, 2009, 04:58 PM

Is it with this release easier to make multilangual sites? Or do you still have to use the tutorial from susan?

You might want to have a look at this new multi-lingual module (YAMS) ...it’s still in alpha version though

http://modxcms.com/forums/index.php?topic=36513.0
http://modxcms.com/extras/package/543


cheers/k

I just installed rev. 5254 and the resource tree does not work under IE8 (fine in FF3). It was OK in a previous post rc1 build.
There is a javascript error:


On a different note. I like the way the Quick Manager is coming along as a replacement for QuickEdit. I just wonder if QuickEdit should be made available in the ’Extras’ as some people may not be ready to transition to QM but still wish to install the latest release?

I installed Rev 5355 for a site in Russian and all the Russian text was mangled. The problem was with the files, not the database, because as soon as I replaced the files with RC1 (before going through the ’upgrade’ script), the text was fine. So something is broke.

@uxello, and rfoster:

The IE problems should now be fixed in SVN (as of rev #5412), it was caused by some earlier changes to the codebase to better handle the MODx manager character set encodings (unfortunately, IE isn’t very forgiving in this regard). I would appreciate it if you could please test the latest SVN head revision to see if the problems are fixed for you.

And, thanks for raising the issues