migrated url compliance handling to the internationalization system

This commit is contained in:
JT Smith 2004-11-05 00:06:10 +00:00
parent 90419bb59a
commit d366eb736a
3 changed files with 20 additions and 1 deletions

View file

@ -31,6 +31,7 @@
- Fixed a redirect loop problem.
- Fixed a user profile vulnerability.
- Fixed a sequence ordering problem with the USS.
- Added internationalized URL handling.
6.2.8

View file

@ -7,6 +7,13 @@ upgrading from one version to the next, or even between multiple
versions. Be sure to heed the warnings contained herein as they will
save you many hours of grief.
6.3.0
--------------------------------------------------------------------
* If you're using languages other than English, you'll need to get
new versions of those language files before upgrading. The
language file format has a new requirement.
6.2.8
--------------------------------------------------------------------
* Due to a bug in the theme system, if you created any themes in any

View file

@ -2,7 +2,8 @@ WebGUI 6.x Plugin Migration Guide
---------------------------------
This document is provided by the WebGUI 6.x development team in order to help
you migrate your WebGUI 5.x plugins to the new API's.
you migrate your WebGUI 5.x plugins to the new API's. If you are not a WebGUI
developer then this file won't make a lot of sense.
CONTENTS
@ -170,4 +171,14 @@ We've switched to a new Plain Old Documentation (POD) format. See Ruling
WebGUI for details.
5.11 Internationalization and URLs
In 6.3 we moved URL compliance to the language file. We did this because the
non-latin characterset languages were having trouble with WebGUI generated
URLs. So now they can write in their own handlers to deal with WebGUI
generated URLs. If your language uses a latin character set, you can just copy
the makeUrlCompliant subroutine from lib/WebGUI/i18n/English.pm into your
language file.