Oops sorry about that... I was a bit hasty with that last set of fixes to the replace table. Still not sure why I don't get those error messages on my windows system. Must be some apache configuration or something... Was working fine here.
Re-uploaded the release with some additional rewiring of the warning system to work with the msg system more closely. But with a few changes. Now processed msgs get mingled with the warning when it aborts. To get just the warning message do [messages warn] or [messages id]. I've tried various configurations and they seem to work ok--but it required pretty massive rewiring of the whole system. There is always the possibility something didn't get connected quire right... I also uploaded a tutorial on the new system. Perhaps not complete but a good start, and certainly more than we had. :) http://www.boltwire.com/index.php?p=docs.forms.messages As for the problem--I actually think this IS what we want. It shows up in the page exactly how it shows up the edit box. Same as if you entered < -- which I suspect before would have automatically converted to < in the display and in a text box. Now, in either case, you get exactly what you put in. If we want to convert to a literal non-breaking space, we would just need to get a markup rule for that. So when you edited it, you can retain the in your edit box. But in general I think our first goal is to get the page display and what shows in the edit box to be as close as possible (apart from markup). And then secondarily to have the source page close as well. As for your reservations about the string replacements, I'm open to suggestions but I think these changes are a move in the right direction at least. We have 1) streamlined the process by running everything through a single BOLTsaveEscapes function 2) both page content and page data are handled essentially the same. 3) much of the past quirky switching behavior (of which you pointed out some) has hopefully been corrected. 4) we've actually only added one char replacement (&) which is called for by the specs. Also here's an explanation of the replacements I made: Non editors/admins [form] => [fo`rm] to protectt form creation Non code pages: & for xhtml compliance. < for security reasons All pages ~~ to evade conflicts with the escape code $ to evade certain php quirky problems \r and \r\n => \n cross platform compatibility ~data~ to block artificial creation of data and then ' and " are unescaped on the odd chance they got escaped somehow, somewhere... I'm not sure I want to delete any of these... Please give the new release another try. I'm looking forward to feedback. Assuming it works a bit better this time... 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 -~----------~----~----~----~------~----~------~--~---
