We want to close down the SobiPro part of limesurvey.org: www.limesurvey.org/index.php/community/extensions

All extensions should be moved to LimeStore.

OK,

I can start to do it : BUT
1. Some extension didn't have config.xml (not needed)
2. Some templates are not 3.X compatible

Great!

1. Which extension? All extensions should have a config.xml file. You can create a dummy one otherwise.
2. It's OK to publish extension from 2.06 and above.

Great to see the progress here. A short questions: How about adding the version of a plugin/theme to the download/title of a ZIP file. Otherwise you may end up with several "massaction.zip" files if you use a plugin for long and for different Limesurvey versions and you always have to check which version it is compatible with at the XML file.

Mazi wrote: Great to see the progress here. A short questions: How about adding the version of a plugin/theme to the download/title of a ZIP file. Otherwise you may end up with several "massaction.zip" files if you use a plugin for long and for different Limesurvey versions and you always have to check which version it is compatible with at the XML file.

Good idea, I'll fix that.

ollehar wrote: 1. Which extension? All extensions should have a config.xml file. You can create a dummy one otherwise.

Yes, but none have one here. And i don't have access to all (i make can make a fake config.xml for mine, but not for other).

Se www.limesurvey.org/index.php?option=com_...5:AuthCAS&Itemid=729 or www.limesurvey.org/index.php?option=com_...olethAuth&Itemid=729 or www.limesurvey.org/index.php?option=com_...ememberme&Itemid=729

Some are not really for limestore : www.limesurvey.org/index.php?option=com_...100:limer&Itemid=729

ollehar wrote: 2. It's OK to publish extension from 2.06 and above.

They don't have config.xml

I'd like to go live with LimeStore beta pretty soon, maybe next week. It will only include freely available extensions, not purchases, since the legal agreement is not ready yet. We can talk about it more next team meeting on Tuesday.

OK try to make some config.xml to SkeletonQuest, validate skelvanilla to be free , and try to put some other plugin (with beautifull logo …)

When making an error : (for example adding space in Plugin name) : come back to form : but this one is empty.

It's hard for us

Another one
When making the system (adding picture, description etc …) can be great to preview the final page.

I'll add it to the bug report in Phabricator.

Question: It's important that customers easily can reach the extension developers for questions and feedback. Should the author email in config.xml work as a default communication point?

Or, rather the authorUrl web page.