>> > I think the sooner the better as it's valuable information for the dev >> > team. >> > It'd probably be a good idea to have a Wiki where we can document >> issues >> > that/common use-cases which are encountered. >> > Maybe we should have a Wiki on one of the php.net servers for such >> > purposes? >> > Andi >> >> Is anyone aware of a list with a, say top 10 PHP applications? >> >> When such a wiki is setup, how would you suggest to write such >> documents.. At least a generic guide would be good (e.g.: common >> pitfalls) >> Should I be documenting the per-project specifics as well? >> >> Evert > > Top 10 by what metric? If I had to guess based on market share, I'd say > (unordered): > > Drupal > Squirrelmail
SquirrelMail 1. remove session_unregister call 2. fix get_magic_quotes_gpc() call 3. Turn off unicode.semantics in webserver configuration or php.ini SquirrelMail scripts are designed to work with binary strings. Lots of SquirrelMail functions are not compatible with unicode.semantics=on. Some calls are not prepared to handle changes in crc32(), base64_encode(), fputs() and fwrite(). If scripts keep backwards compatibility, they will need wrappers for most of affected string and stream functions. Some unicode.semantics=on side effects can be fixed without splitting functions between PHP5 and PHP6, but unicode.script_encoding can't be set with ini_set() and must be declared on top of all affected scripts. -- Tomas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
