Oh rats about the plugin installer! All right, I'll fix this for the next release. Somehow. Thank you! Also for helping debug the UTFpage names. I'll look into these. Very helpful. As for moving to % encoding, yes, we need to. It will solve some problems. Just changing it crashes BoltWire. May not be an easy thing to fix. I'll try. I realize we need to make this switch soon before you get too many page names set up.
Cheers, Dan On Sun, Feb 22, 2009 at 6:48 AM, Linly <[email protected]> wrote: > > Bug report: About the plugin install message. > > When I install another old plugin, I always got the message from the > sandbox plugin. The installation was success, only the message not > right. > > Cheers, > linly > > On Feb 22, 5:08 pm, Linly <[email protected]> wrote: >> Hi Dan, >> >> Do you think it's time to use real percent-encoding not the >> "_c3_af..." ? Since the site admin has the right to set "utfPages" >> true or false. >> >> linly >> >> On 2月22日, 下午1時27分, Linly <[email protected]> wrote: >> >> > The plugin message is excellent. Great. >> >> > About the UTF pagenames, I've test these in FireFox3: >> >> > * Success: create, edit, title, copy, delete >> > * Failed: rename >> >> > While "section edit" is ok in FireFox but failed in IE6. >> >> > The # problem is solved. Now the form can use "target {p1}.#" to >> > create auto numbered page names. Wonderful. >> >> > I noticed that every utf page name will write a data something like >> > "{info.tags::中文}" showing in the footer where I put tags area. But the >> > data did not in the page "info.tags", strange. >> >> > The "utfPages: true" setting also break the "utf-8 tags" function. >> > While turn "utfPages: false", the "utf-8 tags" would work again. >> >> > One thing should note. If the page name contains a space, it will >> > replaced by time stamp {now}. Don't know this is bug or not. >> >> > Cheers, >> > linly >> >> > On 2月22日, 上午10時14分, The Editor <[email protected]> wrote: >> >> > > This release tackles one of the big items on my 3.xx list--messaging >> > > from plugin installations. To try it out, upgrade to 2.50, then >> > > download the sandbox plugin and enable it (go to action.plugins and >> > > click sandbox. Then try uninstalling. Let me know what you think! I >> > > like it... >> >> > > Eventually we will want to add message pages to our other existing >> > > plugins, but until then there should be no problems installing old >> > > plugins. I think this is a really good solution. >> >> > > Several more bugs also fixed in this release. Mostly things introduced >> > > by other recent upgrades. Things are looking good. Linly--you will >> > > want to test out the improved UTF pagenames. Minor changes. just helps >> > > BoltWire know what to do with pages like test.some_page and other >> > > things that glitched before. Not perfect still, but closer... >> >> > > From the changelog... >> >> > > * Added some line breaks to html output. Shouldn't affect display. >> > > * Fixed a small bug in the displayTemplate function causing unintended >> > > line breaks. >> > > * Improved mail function's body parameter (auth bug from last release). >> > > * Fixed small typo in displays (extra line returns). >> > > * Fixed bug with lists and sorting. >> > > * Reworked plugin install process to allow for messages from a backup >> > > file. See this update plugin: solutions.system.sandbox to demo how to >> > > works. Still works the same with old plugins. >> > > * Fixed bug in plugin uninstall button. >> > > * Smarter handling of UTF page names. >> >> > > 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 -~----------~----~----~----~------~----~------~--~---
