Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On Thu, 2011-07-28 at 19:08 +0300, David Nelson wrote:
Hi Drew,

I'm no wiki guru but, IIRC, you need to enclose your code portions
within code tags, so that the wiki recognizes it as content to format
as code and doesn't think you're attempting a code injection exploit.
Maybe this link will help:

http://code.google.com/p/support/wiki/WikiSyntax#Code

HTH.

Hi David,

Nope, tried <code> earlier, also - doesn't matter

Trimmed it down to just one html block with a link which is for the
URL: 

http://wiki.documentfoundation.org/cgi_img_auth.php/e/ee/LiboConf-270x60.png

and that gives the same denial screen of 

---------------------------------------------
Spam protection filter
From The Document Foundation Wiki

Jump to: navigation, search 
The page you wanted to save was blocked by the spam filter. This is
probably caused by a link to a blacklisted external site.

The following text is what triggered our spam filter: <a href


Return to Gallery Buttons/Conference

-----------------------------------


Thanks,

//drew


-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.