Make token names consistent

Hi @jurgenhaas,
Created MR for patch #3. and missed occurence.
It cover 1 and 3 from #5.
For point 2, update command will works, right ?
Thanks.

Thanks a lot @_pratik_ for the MR and the enhancements. There is only one little comment in the code that needs your attention.

As for the update of existing models, unfortunately the existing update command doesn't cover that. The update command recognizes changed in the config forms for the plugins, but the changed token name is being used in config values. So, what's required is an update_hook which goes through all the models, check all the config fields if a token with [current-form is being used and replace that with [current_form. In the eca.install file there are already a few hooks which do similar thing. Using one of them as a blue print should help a lot.

Hi @jurgenhaas,
I am little occupied with some other priority work. Unable to focus here.
I thought to inform, to not keep you waiting.

Thanks.

I've resolved the one code issue and added the update hook which updates existing models. For that reason, we need to back port this fix into 1.1.x and 1.0.x so that those models don't be missed out from this update.

Thank you guys for the work.

Good idea to us an update method. This keeps the code clean.

Thank you. Merged this into all 3 branches.

Why backport? This issue is a task, not a bug fix. Futhermore, despite of having the update hook, there is a risk of breaking compatibility. Therefore, this should've only committed into the current feature branch (1.2.x).

Automatically closed - issue fixed for 2 weeks with no activity.