[pmwiki-users] markup parse issue
henrik.bechmann at sympatico.ca
Tue Feb 10 12:52:16 CST 2009
>>I've been thinking that perhaps we should define ":url(...)" as a
lazy form of [=...=]
That would be helpful (though somewhat specialized from your point of
view I imagine).
In the meantime I've remembered my workaround (from about a year ago):
$FarmPubDirUrl = '/shared/wiki/app/pub';
$PubDirUrl = '/wiki/pub'; #prevent unwanted conversion to full url in
style url(.. strings
#$PubDirUrl = $UrlScheme.'://'.$_SERVER['HTTP_HOST'].'/wiki/pub';
IOW if I use relative directory addressing for PubDirUrl and
FarmPubDirUrl (from which SkinDirUrl is derived) then the url(...
substitution takes place correctly. I presume presence of the $UrlScheme
is triggering the image element string substitution. However would this
use of relative addressing be a problem for https:// sites?
(Incidentally /shared/wiki/ is a symlink into the shared farm environment)
Patrick R. Michaud wrote:
> On Mon, Feb 09, 2009 at 08:09:04PM -0500, Henrik Bechmann wrote:
>> I have the following markup:
>> (:div2 class="header-content"
>> (I've added background-image to the $WikiStyleCSS array)
>> But PmWiki is parsing the image fragment as an element, and creates an
>> embedded image element thus:
>> alt='' title='' />)
>> ...which of course is a css error.
> I've been thinking that perhaps we should define ":url(...)"
> as a lazy form of [=...=] that protects its contents from
> being treated as a link. Then the above would work.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pmwiki-users