I was so encouraged by how well the fix to the slashes problem went, that I decided to tackle the < encoding issue. And I had even more surprizing success. At present I seem to have it working on my machine perfectly. Will probably put out a release tomorrow morning...
Basically we will no longer be encoding < with < in the source code. It does remove one backup layer of security, but if we are careful it should not actually open any holes. On the plus side, it gives the advantage of streamlining the code even more. And we can make the nice boast that now, essentially whatever you type in the edit box is exactly what gets saved in the source, and is what you see displayed in the html output. I really like that consistency. And there are virtually no exceptions (one or two very minor hacks to block a couple security attacks). This upgrade will require an update of your source pages, to convert existing < to <. But I have a script already created that will handle all of that for you automatically. Anyway, I'll get this out in the next release, plus a couple other fixes and tweaks. Last chance to discuss the pro's con's of the change, but we've had it on the agenda for awhile, and I'm pretty sold that this is the way to go... Cheers, Dan -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
