Raphaël Luta wrote:
I would personnally say that the best way would be to define a new FusionEncodingPortalURL that behaves just like PathInfoEncoding except that it adds the follwoing string : _ns/_ns: instead of simply _ns:
It would change anything for j2 since it specically looks for '_ns:' as an identifier and will allow Turbine to recognize a new _ns parameter which it would care about but at least will not break the othher parts of the URL.
The Fusion assembly script needs to use the FusionPortalURL instead of any of the regular ones.
What do you think ?
Looks Turbine friendly to me. Are you going to write it ? Im going to try releasing 1.6 today.
I thought we would first go through Release candidates for 1.6 before announcing an official "1.6" release ?
If we could get the fix in now I'd be glad to incorporate it in the release
I can write it easily but I don't have currently the environment to test it :) I've not yet run Fusion...
I'll commit a patch later this evening.
-- Raphaël Luta - [EMAIL PROTECTED] Aptiwan, l'intelligence du réseau - http://www.aptiwan.com/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
