Since Scotty seems to be MIA lately, maybe we should make a v1.3.1 release?

Since people are talking in this thread, I wanted to bring up a VERY bad bug, for security reasons.

You know how Scotty implemented the "private" stuff for fields, if the user wishes? I dunno why, but using the Sorting Options code, it outputs the field, even if the user had said it was supposed to be private.

Thing is, I don’t have the faintest clue of how to fix that...

Alrighty guys. Scotty’s given us the "green light", so to speak, for doing this.

Maybe a good plan of attack would be to gather up all of the bug fixes already made, as well as the issues currently active (like that Sorting Options issue). Get a file updated with all of the bugfixes, do some testing on it to make sure everything’s alright, then do a v1.3.1 release.

And then work on the non-fixed issues, get those resolved, then do a v1.3.2 release. I know two releases might seem bad for the end user, but I bet some of the existing bugs might take a while, and having fixed bugs not being fixed in the current release is the more important issue right now (plus, the current issues aren’t groundbreaking --- just issues with accepting special characters and whatnot).

What do you guys think about that plan?

Did Scotty ever mention working on the project at some point to do a 1.4 release?

Sounds good to me... better than going through a 420+ long thread...
this will enable opening new support threads for each version too...

Quote from: Sulman at Mar 27, 2008, 08:11 AM

Did Scotty ever mention working on the project at some point to do a 1.4 release?

Yes, part of that was adding proper form checking support (like checking for bogus text in e-mail addresses), as well as allowing HTML in the inputHandlers.

it would be great if you include something like
this: http://modxcms.com/forums/index.php/topic,18272.msg140731.html#msg140731
and this: http://modxcms.com/forums/index.php/topic,18272.msg140731.html#msg140731
in the release 1.3.1

Thank you!

Quote from: Bruno17 at Mar 31, 2008, 08:34 AM

it would be great if you include something like
this: http://modxcms.com/forums/index.php/topic,18272.msg140731.html#msg140731
and this: http://modxcms.com/forums/index.php/topic,18272.msg140731.html#msg140731
in the release 1.3.1

Thank you!

That would likely be more of a v1.3.2/1.4.0 addition, since v1.3.1 is meant mainly for bug fixes.

You did mention that the sorting issue is the MOST IMPORTANT one -- AFTER applying the existing bugfixes.
I agree.
But PLEASE make sure that, when touching the sorting code, the using of usernames as associative ID keys will get out of it!!!
PHP is not unicode-capable so, when usernames are used as arguments for the array of users, this can stop the processing with error.

I don’t think that a parsing errors caused by unicode are "just issues with accepting special characters" -- as you wrote.
The bigger half of the world (and the future of www also) is upon unicode!
I’m not fighting but trying to give a new view to yours.

Unfortunately I’m not able to program PHP, it was my best to find the cause of this issue.
So I wish the best to Soshite and the others contributing this ’PE Update project’! Good luck, guys!

I’m not familiar with the WLpe code but if the sorting is done by MySQL rather than the snippet, it should handle Unicode characters fine as long as all the setting are correct (a big if) and MySQL is at least 4.1.

Here’s some more information on UTF8 with PHP and MySQL: http://www.shawnolson.net/a/946/unicode-data-with-php-5-and-mysql-41.html