Hello!
I've inherited a customized Limesurvey website. It's quite old, around 2.06, and we're going to upgrade it to 4.x
The original developers added models and controllers by placing PHP files directly in corresponding directories, like application/model

Can plugins/extensions add models / controllers etc?

Is there a documented / proper way to do so?


Experienced Drupal developer, pretty new to LS extension development. Want to make all the customs be in extensions, for easier upgrading.
Thanks in advance!

Not controller easily (if i don't make error) but you can replace or use your own with beforeControllerAction (i never use my own, only replace).


For model : sample gitlab.com/SondagesPro/coreAndTools/reloadAnyResponse

Is there a documented / proper way to do so?

Not really …

There are discussion about adding real Yii extension, but no dev to do it cleanly.

www.yiiframework.com/extensions?version=1.1

Maybe you can create one and adding it via config.php file ?

PS : remind 4.X is not really stable currently …

wrt 4.x stability .. I'm not scared. I'll put in some PRs for ya. That being said, what's not stable about it? Known issues or things to watch out for?

There are many open bugs that can be showstoppers, depending on your survey. At the moment I would not recommend to use LS 4.x in production.

However, if you are still in development phase and have a couple of months until you are going into production, you might want to go with LS 4.x rather than LS 3.x LTS. Once LS 4.x is finally stable, LS 3.x LTS will probably run out of support (LS usually is not keeping older versions alive for a long period, like Drupal).

So the decision depends a little bit on your timeframe. I would not expect LS 4.x to be ready for production in 2020. I'd rather guess that it might be end of first quarter, beginning of second quarter 2021. I might be pessimistic though.

If you need

- Expression Manager event (create new function, add variables …)
- Pseudo crypt system (pseudo because crypt Y and N with the same key on all surey … you have way to find key easily if you get the DB).

You have to use 4.X

Else : your plugin work near same in 4.X and 3.X, just need a config.json for 4.X

Then : for plugin dev : it's easiest in 3.X, because if you have a bug : you can be sure it come from your plugin, not from core …