So we need a "BITS"(BoltWire Issue Tracking System), right? :) I have a plugin can create a todo list, and swatch the status of the items from "todo" to "done" or "stop", or vice verse, but it lacks of priority, voting, or rating.
Cheers, linly On 3月13日, 下午5時00分, Hans <[email protected]> wrote: > I still get the same issues with rendering of {+p} in search fmt= > For instance markup [(search fmt="* [[{+p}]] {+p1}")] will output > raw % encoded strings for utf-8 higher characters. > [(search fmt="* [[{+p}|+]] {+p1}")] works as the page title is > processed, but any {+p} in a template fails. > Can you confirm this Linly? > > I am repeating reporting this issue, till Dan gives me some acknowledgement. > Dan, do you keep a list of bugs and issues to be addressed? > > IMO the problem is in function displayFmt, where line > $fmt2 = str_replace('{+p}', $item, $fmt2); > should be replaced by > $fmt2 = str_replace('{+p}', BOLTurl2utf($item), $fmt2); > > To fix another problem with that function: > In addition line > foreach($outarray as $item) { > should be > foreach((array)$outarray as $item) { > for cases where $outarray is not supplied, to prevent a variable type error. > Or enclose the foreach loop in > if (is_array($outarray)) { > . .... > } > The $outarray var is set in the function as $outarray='', which is an > empty string, so you get a wrong variable type if £outarray is empty. > > Cheers, > ~Hans --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
