UTF8 pages are not being found in searches in 3.4.13 Especially annoying since my 3.4.13 skin doesn't work in my branched version, for unknown reasons.
Is it possible to turn of the utf8 handling in boltwire completly? Basically, I would like utf2url and url2utf to check: if( !$BOLTutfHandling ) return $input; Then I would simply have to convert the filenames into utf8 characters and be on the lookout for markups that rely on \w+, converting these to reluctant .*? where neccesary. I would be free. Freeeeeeeeeee. There isn't actually a single place in the boltwire engine when I actually want the utf2url function. On Aug 13, 4:11 pm, DrunkenMonk <[email protected]> wrote: > Got a test site up using 3.4.13, you've reverted a bug I thought you > said you'd fixed, but I may be mistaken. There are two issues. > > in engine.php > if (get_magic_quotes_gpc() == 1) { > foreach($_GET as $field => $value) $_POST[$field] = > stripslashes($value); > foreach($_POST as $field => $value) $_POST[$field] = > stripslashes($value); > } > > all <input name="bob[]"> style inputs are destroyed with this (when it > suddenly decides that I have magic quotes enabled. Sigh.) since they > result in $_POST having nestled arrays. You get: > > var_dump($_POST['bob']) yields: > string(5) "Array" > > Secondly, POST and GET are still being combined into POST, which I'm > pretty sure you said was not intended. > > --- > > Although I do not understand why you want to override the magic quotes > setting at all, really. If it's set to On in php.ini (which is > deprecated anyway), shouldnt you simply accept that? Boltwire should > work fine and be internally consistent anyway. > > Meh. I found the setting in my ini file and shut the darn thing off, > anyway. I matters naught to me now. > > Hope you've all had as warm a summer as me. > > On Jun 24, 5:28 pm, The Editor <[email protected]> wrote: > > > Sorry for all the emails today... Decided to spend a morning trying to > > clear out my inbox and fix our few outstanding bugs. I think > > everything is pretty much up and running in this release. My apologies > > for the delay in getting the utf titles fixed and the <br /> tags in > > the preview display. But given the fact it's been more than 6 > > weeks--the fact we just had these two issues is pretty good. I also > > fixed a few other things while tinkering, including some reworking of > > how POST values are treated. > > > Hopefully this release solves all our remaining issues, and we can > > start looking to 4.xx. From the changelog: > > > Simplified core's handling of gui scripts. > > Added a class=fmt for images in the default css. > > Fixed embedded scripts, which were inserting extra line breaks. > > Fixed odd bug in BOLTprocess function. > > Fixed utf encoding of page titles. > > Fixed bug inserting line breaks in previewed content. > > POST values are now preserved through the page redirect process and > > available on target pages. POST arrays, are displayed as a csv list > > for use in function parameters. > > > Please let me know if there is anything truly pressing that we work on > > before the switch to the next series. Otherwise I'm inclined to make > > this our final release. A week or two for testing and spotting > > problems first of course. > > > 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.
