WordPressPlugin (posted directly from my foswiki)

post a topic to your WordPress blog

Usage

This plugin registers a restHandler that allows you to post a Foswiki topic to your wordpress Blog.

Only one blog can be configured at this stage, and must be set up by the administrator in configure, and the user must be an author.

If you hit post on a topic more than one time, it will post it multiple times – so be a little careful :).

Examples

to post the webstatistics topic to the configured wordpress blog, craft a URL like:

http://t42p/trunk/bin/rest/WordPressPlugin/post?topic=Sandbox.WebStatistics

Installation Instructions

You do not need to install anything in the browser to use this extension. The following instructions are for the administrator who installs the extension on the server.

Open configure, and open the “Extensions” section. Use “Find More Extensions” to get a list of available extensions. Select “Install”.

If you have any problems, or if the extension isn’t available in configure, then you can still install manually from the command-line. See http://foswiki.org/Support/ManuallyInstallingExtensions for more help.

Info








Author(s): SvenDowideit@fosiki.com
Copyright: © Sven Dowideit – http://fosiki.com
License: GPL 3 (Gnu General Public License)
Version: 3758 (2009-04-29)
Change History:  
Dependencies:
Name Version Description
WordPress::Post >=1.04 Required
Home page: http://foswiki.org/bin/view/Extensions/WordPressPlugin
Support: http://foswiki.org/bin/view/Support/WordPressPlugin

Foswiki night builds of trunk and Release01x00 branch

I’ve just (finally) set up the auto unit test run, PerlCritic and release build for the Release01x00 branch, and fixed the trunk builder.

Foswiki trunk gets built every 6 hours, and Release01x00 every 12 (based on my Sydney TZ).

If the unit tests fail, and email will be sent to the foswiki-discuss mailing list – no news is good news. See the build output areas:

  1. Foswiki trunk
  2. Foswiki 1.0 release branch

where you will find the output log files, the built tar.gz and zip files and each of the component packages that make up a release.

new FugueIconsContrib

https://i1.wp.com/www.pinvoke.com/icon/image/fugue.png?w=840

I created the FamFamFamContrib Icons package for T(m)wiki and Foswiki a year or three ago, and now have added a FugueIconsContrib package today – containing the fabulous iconset by Yusuke Kamiyamane.

Now we have 2 possible icon sets to replace the very odd and aging DocumentGraphics topic – the only thing holding us back is a mapping from the old %ICON{}% names to new.

I’ll dig up the work I did last year some time and see if we can finish it 🙂

Howto protect foswiki attachments without slowdown

I was just asked on IRC how to protect some attachments without forcing all requested attachments to go through the viewfile cgi script (as that causes your foswiki images and css to load incredibly slowly), and here’s the howto I answered with:

I was just asked on IRC how to protect some attachments without forcing all requested attachments to go through the viewfile cgi script (as that causes your foswiki images and css to load incredibly slowly), and here’s the howto I answered with:

I coded foswiki 1.0’s viewfile script to work as an apache ErrorDocument, so If you can find a way to trigger a 404 or 401 error, you can get apache to run viewfile –

ErrorDocument 404 /foswiki/bin/viewfile
ErrorDocument 401 /foswiki/bin/viewfile

If you place your pub dir somewhere outside where apache serves files and then softlink the non-protected webs into apache’s path (so it serves them full speed), then the secured webs will generate a 404, triggering the viewfile ErrorDocument – which will thus serve the file only to authenticated users

This will work irrespective of the authentication choices in your foswiki setup – and as the files that require securing are outside apache’s file serving areas, can be considered as secure as possible.

As an added bonus, any request to a file that does not exist will show a foswiki error page, rather than a static html.