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.
If we could get the fix in now I'd be glad to incorporate it in the release
--
David Sean Taylor
Bluesunrise Software
[EMAIL PROTECTED]
[office] +01 707 773-4646
[mobile] +01 707 529 9194
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
