ExtensionHub-Talk

Summary: Talk page for ExtensionHub.

Maintainer: Petko

Users: +1 (View / Edit)

This space is for User-contributed commentary and notes. Please include your name and a date along with your comment.

Feel free to add new threads here.

Asterisk and Caret in Hub table?

On page SiteAdmin/ExtensionHub could a key please be added for the glphs "^" and "*" e.g. SimplePlaylist^* or PmWikiInfo 2026-05-19^{^}

simon May 20, 2026, at 09:04 pm

Note: $RecipeInfo[PMWIKIINFONAME] ['Version'] = '2026-05-18' . PmWikiInfoNew; # PmWiki version numbering is done by date

Added to both the hub and design pages. Your line seems to have an unexpected space between the brackets, this fails the regular expression. Also the constant after date will be ignored. --Petko May 21, 2026, at 06:04 am

Thanks for the updates, I like spaces and white space, I don't expect the constant after the date to be included.

simon May 21, 2026, at 09:32 am

Moving to the core

I support this moving to the core

simon April 16, 2026, at 08:40 pm

Could we drop the compressed extensions feature? Having a hub.php file separate from the core/scripts files allows for a very lightweight decompression proxy; if it is in scripts, pmwiki.php will be called which will load config.php and it, and maybe 20 other scripts. Alternatively, we can have only the tiny zip proxy functions in extensions/hub.php which people will need to install. I now also prefer for the extensions directory to be outside of the pmwiki distribution tree -- so that the latter can be replaced and updated independently. --Petko April 16, 2026, at 10:31 pm

Having only uncompressed extension folders as installed software is fine with me.

simon April 17, 2026, at 03:07 am

Tutorial

Hi Petko, I was thinking of grouping all my snippets into one extension, but I'm having some difficulty. When you have some time, could you write a short tutorial to compile the main extensionsX.php which calls other pages (.php, .css, .js and standard pm-pages)? Thank you.
Furthermore, is it possible from the extension to add a custom skin (with a new Site.SkinElements page)?- Frank March 02, 2024, at 07:11 am

Sorry for the delay, I am in the middle of a quite intense project with not enough sleep. I have drafted the page ExtensionDesign that may help you start. Remember this requires PmWiki 2.3.31 or more recent, and I've just updated the Hub and 2 of the sample extensions today (to simplify the merging of the local and the default configuration arrays). Please do let me know if you have any questions or difficulties, or if you uncover bugs.

Yes, you can set the $Skin variable from an extension, and ship wiki pages, but if a wiki page already exists on the wiki, that page will be used and not yours. If you have a custom skin, you should distribute the skin pages with it, see for example how Triad does it - it is a different mechanism, you directly edit $WikiLibDirs. --Petko March 02, 2024, at 02:30 pm

Talk page for the ExtensionHub recipe (users).