Move "not maintained anymore" plugins to a separate section ?

gilcot 2018-10-10, 02:09 #16

Member since Aug 2018 · 12 posts · Location: France
Group memberships: Members

Show profile ·

Link to this post

In reply to post ID 62958

Quote by ryan.chappelle on 2018-10-08, 16:37:
Also would someone be able to explain to me the syntax that can be used for the pluginrepo data table when editing pages? I've seen this works

compatible : Frusterick, Lemming, Anteater, rincewind, angua

But I'm also looking for some sort of glob syntax and as I've mentioned above I've never been able to make it work correctly. And I can't find information on how extensible it is, for example I'd like to point out a plugin works with ">= Binky" or "PHP <= 5.6".

It's based on plugin just called repository:

Multiple versions can be given and code names can be used. Eg: 2009-02-14, lemming, anteater.

- Use a plus sign + if you think it's safe to assume that the plugin will be compatible with future releases of DokuWiki.
- Use an exclamation mark ! if the plugin is not compatible to a DokuWiki release (e.g. “!Greebo”).

Samana Johann 2018-10-10, 06:56 #17

Member since Jun 2018 · 175 posts · Location: Aural/Cambodia
Group memberships: Members

Show profile ·

Link to this post

May it not interrupt and lead astray: althought possible total different as used here on DW. My person got a little familar with another software maintaining of mods/plugin use. They used to have a topic for each mod in their forum which was also linked in the "plugin"-page. By viewing it, it always gave a good overview about the status and problems, since it was very central. Any fix but also contributions have been very accessable for the whole community. Maintaining and feedback seems to be very decentralized, focusing possible more on the plugin-contributors ease (causing on the other side to possible limited feedback). Since Wiki is the heart here and not a forum, it's maybe interesting to make the central place of exchange, contributions, discussion on a wiki-diskussion page at the plugin page itself, possible leading also to more contributions on the DW-wiki. But as said, not much idea of how things are used here and the function of the triangle between team, plugin-contributor and user, so just a very outwardy imput.

gilcot 2018-10-10, 13:01 #18

Member since Aug 2018 · 12 posts · Location: France
Group memberships: Members

Show profile ·

Link to this post

Quote by Samana Johann:
My person got a little familar with another software maintaining of mods/plugin use. They used to have a topic for each mod in their forum which was also linked in the "plugin"-page. [...] Since Wiki is the heart here and not a forum, it's maybe interesting to make the central place of exchange, contributions, discussion on a wiki-diskussion page at the plugin page itself, possible leading also to more contributions on the DW-wiki.

I also use web-app that works that way: there's are comments attached to each extension page.
That's possible with DW using comment plugin or similar :-)

Quote by Samana Johann:
[...] By viewing it, it always gave a good overview about the status and problems, since it was very central. Any fix but also contributions have been very accessable for the whole community. Maintaining and feedback seems to be very decentralized, focusing possible more on the plugin-contributors ease (causing on the other side to possible limited feedback). [...]

The approche used by DW is due to the fact that plugins may come from different repositories (in the case I mentionned earlier they are in a common/central repository.)
But each repository (hosted a GitHut or GitLab or BitBucket or other) is often attached to a bug tracking system... where you can view the status and the problems. So DW avoid reinventing the wheel...

andi (Administrator) 2018-10-12, 00:28 #19

User title: splitbrain
Member since May 2006 · 3539 posts · Location: Berlin Germany
Group memberships: Administrators, Members

Show profile ·

Link to this post

In reply to post ID 62958

Hey Ryan, good to see you again.

Quote by ryan.chappelle on 2018-10-08, 16:37:
It's been a while and I had done this but never actually opened it up but now I saw this thread and remembered. Anyway, I did end up setting up that demo site for old Dokuwiki versions and their plugins. At the moment it's pretty basic and lacks information about eg.: webserver setup for each version because of PHP≤5 vs PHP≥7 support, or cross-plugin dependencies.

This is quite cool. I don't know how users would use this, but it's a cool idea.

Read this if you don't get any useful answers.
Lies dies wenn du keine hilfreichen Antworten bekommst.

Michaelsy 2018-10-12, 09:02 #20

Member since Jun 2015 · 987 posts · Location: Düsseldorf, Germany
Group memberships: Members

Show profile ·

Link to this post

Quote by ryan.chappelle on 2018-10-08, 16:37:
It's been a while and I had done this but never actually opened it up but now I saw this thread and remembered. Anyway, I did end up setting up that demo site for old Dokuwiki versions and their plugins. At the moment it's pretty basic and lacks information about eg.: webserver setup for each version because of PHP≤5 vs PHP≥7 support, or cross-plugin dependencies.

I've put a link to your demo site on my own demo site. It's a work in progress too and maybe with a little different purpose than yours.

Greetings - Michael Sy.

By Patreon.com a few eurons can be fed into the code phasers of
the DokuWiki engine. Besides, Andi's posts are worth reading.

This post was edited on 2018-10-12, 10:03 by Michaelsy.

ryan.chappelle 2019-01-16, 13:18 #21

User title: Chilean DW Fan
Member since May 2008 · 220 posts · Location: Temuco, Chile
Group memberships: Local Moderators, Members, Newsletter Team

Show profile ·

Link to this post

Thanks for the welcome backs.

I admittedly am not sure who would be the final user of a demo site like mine (considering it's not anywhere near finished). My interest for it is more from the perspective of a digital archivist and as someone who knows in stuff like corporate environments it's not always possible to use the newest release stuff so it is important to have access to old versions of stuff that are known to work for a given timeframe; as such, I do intend to add over time is stuff like:

Server setup (eg.: pre or post PHP=7.0).

Differences between installing some specific DW versions.

What versions of plugins are compatible with what versions of DokuWiki (for example, users of DW pre-Weatherwax will need to fetch a previous version of plugin:tag).

HTTP mirrors of some plugins that are hosted on Github, so non-SSL clients can download them (one thing that from what I have seen the release DW still has not been able to solve).

@michaelsy - I'll try to crosslink back once I can get back home and reacquire the keys to the kingdom. Thanks!

☆ Chilean DW Fan!
→ my plugins for DokuWiki
→ GULIX, my area's LUG
→ Surviving earthquakes since Feb 2010!

FosseWay 2019-05-21, 18:27 #22

Member since May 2016 · 118 posts · Location: Canada
Group memberships: Members

Show profile ·

Link to this post

I'm also interested in doing something to improve the process of finding/choosing plugins which are recent/maintained/popular/working vs. those which are less so.

Yes, I am volunteering to do some work. Before I begin, though, I want to make sure that I am working in the right direction. :-)

Is the [anonymized] plugin popularity/usage data available publicly?

ach (Administrator) 2019-05-23, 20:02 #23

Member since May 2006 · 1958 posts · Location: Folkestone, UK
Group memberships: Administrators, Members, Super Mods, Wiki Managers

Show profile ·

Link to this post

Quote by FosseWay on 2019-05-21, 18:27:
Is the [anonymized] plugin popularity/usage data available publicly?

See the popularity page on the wiki. When you look at the wiki code, you will find that the popularity plugin has an API. You can find out most things by checking https://dokuwiki.org/lib/plugins/pluginrepo/popularity.php?key=version&foo=bar while all the keys are what you will also find in your own wiki's Popularity Feedback plugin.

FosseWay 2019-05-24, 22:13 #24

Member since May 2016 · 118 posts · Location: Canada
Group memberships: Members

Show profile ·

Link to this post

Thank you ach. I should really have found that myself, so thank you for the patient response.

I acquired a list of all plugins and their reported raw popularity. I found reference to plugin-specific data in ./lib/plugins/extension/helper/extension.php but haven't managed to get e.g. 'last updated' values yet; do you know if those are available via the API?

Looking at results plugin Search and Install tab, I wonder if too much weight is given to whole-word matching, and not enough to popularity and recency. To show what I mean, type 'list' into the tab. I would expect three popular list-related plugins to appear at the top: pagelist, filelist, and catlist. Instead, the top hit is a plugin called deflist. Its reported popularity score is 64 out of a possible ~100,000, and it was last updated in August 2007. On that basis, it surely does not deserve the top spot in the search results.

Please note that I have nothing against deflist! deflist is still available for download from the author's site - despite predating the 2008 foundation of GitHub - and looks as though it will still work. It has rich documentation, and I am considering installing it on my own wiki :-)

I don't have a well-formed proposal yet for what could be improved, but I hope that the example above shows what I am thinking.

Edit: searching for "changes" doesn't seem to return the Changes plugin at all! I found it using the word "recent". Can anyone else without Changes plugin installed see the same behaviour?

This post was edited 2 times, last on 2019-05-29, 03:12 by FosseWay.

Global DokuWiki Links