Hi all. I just used BoltWire v3.3.2 and found several issues as the following, hope there's no duplication.
#Bugs? * Searching patterns like "aaa && bbb" will find nothing. It works well in v3.11 * I cannot create a new field via the form in page "action.data". It works well in v3.3.1 * Default system messages defined in "site.message" and translated in page "site.language.xxx" will not displayed as translated if there's a sub-embeded text using something like $1. * <p> is usually generated mistakingly, especially in mult-line paragraphs. For instance, the page http://www.boltwire.com/index.php?p=docs.handbook.markups in the official site contains several bad <p>s. The pattern is like this, given a source: aaaaaaaaaaaaa aaaaaaaaaaaaa aaaaaaaaaaaaa bbbbbbbbbbbbb bbbbbbbbbbbbb bbbbbbbbbbbbb , which is expected to be parsed as the following: <p>aaaaaaaaaaaaa<br/> aaaaaaaaaaaaa<br/> aaaaaaaaaaaaa</p> <p>bbbbbbbbbbbbb<br/> bbbbbbbbbbbbb<br/> bbbbbbbbbbbbb</p> is mistakingly parsed as the following: aaaaaaaaaaaaa<br /> aaaaaaaaaaaaa<br /> <p>aaaaaaaaaaaaa</p> bbbbbbbbbbbbb<br /> bbbbbbbbbbbbb<br /> bbbbbbbbbbbbb<br /> * The displayed content is normal when previewing a page on action=edit, but the source code is unexpectedly overparsed at the same time. For example: o & to & o < to < o > to > o `$ to &#36; o $$ in /=$$=/ to &#36;&#36; o $ to $ o ==[[message]]== to ==<div class='message'>......</div>== #Version Changes? I don't whether they are bugs or just have been changed in newer versions. * site.plugins always detect nothing even when there was a file in farm/plugins * The skin "xxx" is sucessfully applied when the site.config is set "skin: xxx" but not applied when '$skinPath = "xxx"' is written in field/index.php * Skin vars are said to be defined in page "code.skinvars" according to the page http://www.boltwire.com/index.php?p=docs.layout.skins from the official site, but it doesn't work. The page "code.skinvars" seems to have been replaced to the page "code.snippets" wasn't it? #Other suggestions * There are still several encoding problems when an edited page is stored, for example: 1. It seems that < in source code is encoded as < and < is encoded as %26lt;, but %26lt; is unexpectedly to be stored as <, which is identical to the previus. 2. `< is displayed as %26lt; 3. The `$ in <code>..</code> is displayed as $. I suggest that instead of the escaping: < --> < --> %26lt; --> (error), esacpe < --> < and "& --> &", which makes a recursion so that it can be infinitely written without problem: < --> < --> &lt; --> &&lt; --> ... * Instead of having < escaped, the pages "code.*" are stored just as source code, which causes serious display error on action=undo or action=history, and may be unable to restored to an ealier version. * Deleting system pages (which exists in boltwire/barn/system) makes the page empty, instead of deleted, as people may expected, so that the original system page will be applied. Moreover, deleting "code.skin" will corrupt the whole site. * In most web forums, blogs, or wiki systems, going back to "previous page" after sending a form with texts edited will show the edited texts. However, BoltWire shows the texts of the current source of the page being editing, which overwrites the edited text and the editor's work becomes in vain, if there was an error so that the editing submitted hasn't been saved (unfortunately, it happens quite often...). * It seems that texts in /= ... =/ /*...*/ <code>...</code> are expected by most people to be fully displayed as origin, thus should the rules be prior than the rule of ` ? * Although BoltWire is powerful, I found that it takes a lot of work to simply embed a piece of "pure txt" or "pure html" -- with no Boltwire markups or variables parsed -- in a page. Hope there's a way to do the work, for example, using <![CDATA[ ... ]]> for "pure txt" and <body>...</body> for "pure html". If there's a concern of security, just filter out the dangerous tags like html, head, meta, script, link... P.S: I'm not a native speaker. Please don't blow my poor English, thanks a lot. -- 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.
