[thesuraj]

I have been desperately waiting for Pligg to release its final Version 1.0.0 since more than 2 months.
But instead, it is realeasing release candidates only, saying that it is final release candidate and final version will be released soon.

I want to know when will be final version released for sure.

[specialone]

Hi thesuraj,

In my opinion it could be a month or so and a few more Release Candidates away yet as i have personally found quite a few bugs present in RC5 version thats is currently available.

Wistie is also not multi browser compatible or WC3 Valid as yet and and quick example would be google chrome messes up certain sections of your site, also i found video plus javascript popouts don't work with chrome.

HTML VALID: 67 Errors, 4 warning(s)

CSS VALID: 6 errors

Other things i noticed were that a lot of urls when using URL method 2 produce 404 on certain areas of the site like paged top users etc and the actual 404 page links to homepage and advanced search mess up. These are just a few examples of many little bugs throughout RC5.

Then we have the issue of being forced whether we like it or not to 301 redirect all story urls if you are upgrading from an older version of pligg. http://forums.pligg.com/general-help...-url-path.html i asked for some consideration of not changing the story links but Yanki's reply indicates this change looks set to stay as the thread has never replied to again.

With other users reporting various other bugs it looks like we will have a while to wait yet before a final release can be made.

[chuckroast]

Originally Posted by specialone

i found video plus javascript popouts don't work with chrome.

Works fine with chrome.

[Yankidank]

1. W3C validation is overrated and really doesn't serve any significant purpose in determining the quality of a website. It's inaccurate in many cases and doesn't adapt well to new web trends and javascript.
2. We have reverted the /category/ urls so that now either /category/ or without it will work. The urls will no longer be using /category/ in URLs.
3. Most bugs being reported right now are from user errors, not script errors. People rush and don't bother to read any directions and probably 80% of bugs reported are caused by the user not configuring their site correctly or not taking the time to read a paragraph. The actual bugs that are being discovered are usually pretty small and we plan to patch insignificant problems through future releases.
4. Wistie works fine in IE, Firefox and Safari. Chrome holds less than a 5% browser market share (Firefox and IE both hold about 45% individually) and I don't suspect that the number will increase significantly. I refuse to spend any more of my time supporting multiple browsers for Wistie let alone every module that breaks on alternate browsers. It's annoying enough to get Internet Explorer to work the same as Firefox. If you find that a module breaks under Chrome you are more than welcome to fix the module and provide us with your changes. I've already provided 2 javascript editions of the Video Plus module to fix an audio issue.

[specialone]

Hi Yanks,

1. Cool

2. Awesome news

3. People rush and don't bother to read any directions - Agreed

4. Cool

[Neoseifer]

There's also some hard-coded texts that could not be translated without modifying php files.
I think there's also some characters encoding problems with some language (french for me), but I'm not sure because I'm using a modified RC4 version, upgraded to RC5.

[Yankidank]

Originally Posted by Neoseifer

There's also some hard-coded texts that could not be translated without modifying php files.
I think there's also some characters encoding problems with some language (french for me), but I'm not sure because I'm using a modified RC4 version, upgraded to RC5.

Care to point out the hardcoded language files? I've just moved over a few items in the last week into the language file.