This is a discussion thread (the wikipage feels not discussion-ready)
www.limesurvey.org/manual/Plugin_shop

The plugin shop is meant let users sell their own plugins, themes, question templates and demo surveys to other users on limesurvey.org.

For inspiration I suggest two stores of opensource tools:
apps.nextcloud.com/
wordpress.org/plugins/

For me the biggest issue is the compatibly info about plugins. The "and higher" info has to be put beside.
If the shop is open to plugins below LS 3.0 there has to be a easy way, to filter between the three branches.

Wordpress shows the important infos right away.


Nextcloud app store shows which plugins are official developed in the community and are constantly used and checked with all releases.

Always nice to see a link protection is place.

The metadata concept for Nextcloud apps might be another inspiration.
docs.nextcloud.com/server/12/developer_manual/app/info.html

Metadata Wordpress plugin:
developer.wordpress.org/plugins/the-basics/header-requirements/

Hi jelo!

Great feedback! Also feel free to add it to the manual discussion page! (Each mediawiki page has a discussion page.)

www.limesurvey.org/manual/Talk:Plugin_shop

I already put some information on wiki, but :

1. Allow to have different url for "plugin shop" , something like repository in fedora or debian

2. Allow to get any plugin (not in an official plugin shop) by url
or (see yunohost.org/#/apps )

After : plugin can be updatable like comfort update (with or without a key : plugin update url choice).


yunohost and spip have this system. The 2 are preconfigurated with "official and stable" plugin repo, but allow anything else.

[edit]
And 2 last current idea : information like 'copyright', 'update link', 'version compatible' come from a file in the plugin. Then even a plugin set up manually can be updatable.
Maybe we need different directory for "own plugin" and "url plugin" , didn't know.

Another remark : need a Survey Theme + a Question Theme

If we can have same base code for each : it can be great. Then maybe use a config.xml for plugin too. Then have same basic part on all config.xml

This config.xml need something like : <type>(plugin|survey|question)</type>

Yes, we need same config.xml structure for all extensions, so the extension installer can be more simple.

You prefer XML over JSON, Denis?

try to do that with json, you'll need external libs or a lot more code:
github.com/LimeSurvey/LimeSurvey/blob/ma...anifest.php#L83-L100

XML is a real query language, that open many possibilities.

olle wrote: …

You prefer XML over JSON, Denis?

No, not exactlly (i don't care).

But : theme and question already use XML, then plugin can use XML.

I think all metada can follow the same rules :
github.com/LimeSurvey/LimeSurvey/blob/45...a/config.xml#L14-L27

for each "extensions"

Yeah. What about the security problem with XML?

Edit: Details here: stackoverflow.com/questions/24117700/cla...oughout-php-versions

we already deal with this problem since 2.50