One idea: there is already a dashboard entry for the plugin to activate / deactivate it... why not make use of that and allow the admin to put whatever they want there for the language definitions?
Hmm, but there is a trick to it, the plugins folder should not have permissions 777 (read,write,execute) and the definitions file should have write permissions.
I'm not a point and click fan, but I think it would be helpful for many of the admins to not pop up a terminal and go editing around, but keep the user in the Vanilla friendly environment all the time (where you have permissions, validation checks etc.).
Comments
One idea: there is already a dashboard entry for the plugin to activate / deactivate it... why not make use of that and allow the admin to put whatever they want there for the language definitions?
Hmm, but there is a trick to it, the plugins folder should not have permissions 777 (read,write,execute) and the definitions file should have write permissions.
I'm not a point and click fan, but I think it would be helpful for many of the admins to not pop up a terminal and go editing around, but keep the user in the Vanilla friendly environment all the time (where you have permissions, validation checks etc.).
Just a thought,
/cd