<html><body><div>Thanks for the suggestions. Yes, I am familiar with the isolation technique you described. Hopefully others following along can learn something, though, because you described it very well. :-)</div><div><br></div><div>So I took another approach to the problem this morning. I went to the sandbox page and entered in</div><div><br></div><div style="padding-left: 24px; ">(:rel:423:)</div><div style="padding-left: 24px; ">Testing "{$:rel}"</div><div><br></div><div>I was rather surprised to get back</div><div><br></div><div style="padding-left: 24px; ">Testing "423"</div><div><br></div><div>Yes!!!</div><div><br></div><div>So I went back to my original page, took out some extra stuff I had been experimenting with and it works! I can only imagine there was somehow some caching going on, though I don't understand how with constant page edits.</div><div><br></div><div>Anyway, I have my working solution to the original problem. Woohoo!</div><div><br></div><div>The next person who has to follow this process at 3am when everything's falling apart will be very thankful. :-)</div><div><br></div><div>Communities rock.</div><div><br></div><div><br><br>On 27 Sep, 2012,at 06:32 PM, Peter Bowers <pbowers@pobox.com> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="gmail_quote">On Thu, Sep 27, 2012 at 12:22 AM, Allister Jenks <span dir="ltr"><<a href="mailto:zkarj@me.com" data-mce-href="mailto:zkarj@me.com">zkarj@me.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><pre style="font-size:0.9em;font-family:'Lucida Console','Andale Mono','Courier New',Courier,monospace;line-height:1.2em;margin-top:0px;margin-bottom:0px" data-mce-style="font-size: 0.9em; font-family: 'Lucida Console','Andale Mono','Courier New',Courier,monospace; line-height: 1.2em; margin-top: 0px; margin-bottom: 0px;">(:Country: Transylvania :)
"{$:Country}"</pre><pre style="font-size:0.9em;font-family:'Lucida Console','Andale Mono','Courier New',Courier,monospace;line-height:1.2em;margin-top:0px;margin-bottom:0px" data-mce-style="font-size: 0.9em; font-family: 'Lucida Console','Andale Mono','Courier New',Courier,monospace; line-height: 1.2em; margin-top: 0px; margin-bottom: 0px;"><br></pre><pre style="font-size:0.9em;font-family:'Lucida Console','Andale Mono','Courier New',Courier,monospace;line-height:1.2em;margin-top:0px;margin-bottom:0px" data-mce-style="font-size: 0.9em; font-family: 'Lucida Console','Andale Mono','Courier New',Courier,monospace; line-height: 1.2em; margin-top: 0px; margin-bottom: 0px;">
<span style="font-family:Arial,Helvetica,sans-serif;font-size:15px;line-height:19px;white-space:normal" data-mce-style="font-family: Arial,Helvetica,sans-serif; font-size: 15px; line-height: 19px; white-space: normal;">"Transylvania "</span></pre></blockquote></div><br>In the above example I have added 5 spaces in a place where I saw a single space to emphasize what is causing the space before the closing quote.<br> <br>It appears that your particular installation has different behavior. That sounds like a problem with some sort of customization/recipe that you've installed.<br><br>First I would view the HTML source (CTRL-U when viewing the page via ?action=browse) and make sure it is actually a space and not some other HTML. That will give you a hint of what to look for.<br> <br>Then start disabling your customizations either one-by-one or in chunks (I usually use the /* ... */ comments for this because I can comment out half my config.php at a time to narrow things down quickly) and see when the behavior goes back to what you find on <a href="http://pmwiki.org" data-mce-href="http://pmwiki.org">pmwiki.org</a>. When you've narrowed it down to a single recipe or customization then we can proceed from there...<br> <br>-Peter<br><br>PS More detail (perhaps too much) on this debugging technique... (If you are an experienced administrator or developer then this will be old hat, but it may be helpful for some who are just getting started.) Let's say I have a config.php file with just 4 lines: <br> <br>===(snip)===<br>A;<br>B;<br>C;<br>D;<br>===(snip)===<br><br>I set up a page that clearly shows the problem I am having and make sure it is reliably reproduced. Then I comment out half my config.php:<br><br>===(snip)===<br> /*<br>A;<br>B;<br>*/<br>C;<br>D;<br>===(snip)===<br><br>Now I re-load the page in my browser. If the problem disappears then I know that it was either a problem with A or a problem with B. If it doesn't disappear then I comment out the other half of my config.php:<br> <br>===(snip)===<br>A;<br>B;<br>/*<br>C;<br>D;<br>*/<br>===(snip)===<br><br>Now I re-load the page in my browser. If the problem continues then it is more complex -- perhaps a per-page or per-group customization or something with my PHP installation or etc. But if the problem disappears then I know that the problem is with C or D. I comment out C:<br> <br>===(snip)===<br>A;<br>B;<br>/*<br>C;<br>*/<br>D;<br>===(snip)===<br><br>and try again. Now I' know whether the problem is caused by C or by D. I continue the process until there is a single customizaion or recipe that causes the problem to appear when it is active and causes the problem to disappear when it is commented out.<br> <br>This same technique can be expanded to be used for config.php with many, many customizations.<br><br>Note that sometimes the problem occurs because of the interaction of one recipe with another (in other words either recipe on its own is fine, but when you have the two together they don't play nicely). In that case this technique can actually confuse things rather than helping until you realize what's going on.<br></div></blockquote></div></body></html>