1.3.0 - Update for multiple predefined classes and option to use both text input and predefined classes

[JoryHogeveen]

CHANGELOG: 1.3.0

• Feature: Change dropdown to checkboxes for multiple class selection
• Featute: Option to use both defined and text input classes
• Feature: Migrate classes when predefined classes are available
• Improvement: Do not show previously defined classes that are removed in the settings page when a widget is not updated yet
• Fix: Only show stored classes if the field-type in the setting page is correct
• Fix: When predefined is selected, show previous text input classes if they are defined
• i18n: Added Dutch translation
• Backend: "dropdown" setting is changed to "defined_classes"
• Backend: "hide" type is now "0" in the settings instead of "3" -> "3" is now used for the "both" type

TODO:

• Update other translations
• Versions of other files (main plugin file version is updated to 1.3.0 + DB version is updated to 1.3)
  • I didn't quite understand the version-system of the other files so I'll leave that to you!

TESTS (worked in my tests - please also check!):

• Testing migration from 1.2 DB version to 1.3
• Import/Export functions (also import from 1.2 DB version)
• All classes in widgets will keep working. Selected classes on dropdown will be migrated to the new multicheckbox option
• Merge previous dropdown classes with the new classes.
• Full migrations functionality for text-input classes and predefined classes.
  • When text-input classes are defined, check if they exist in the predefined classes, if so, add them and remove them from the text-input classes (only for type "predefined" and "both")
  • When text-input type is selected, check if there are predefined classes selected, if so, add them to the text-input field.
  • Do the above also for display to make sure classes will not be lost when a different type is selected.

[cleverness]

I can't find any issues so I'm going to go ahead and merge this pull request. Thank you so much for your work, it's a great feature to add.

[JoryHogeveen]

No problem!

[JoryHogeveen]

Oh before I forget. Please check the versions of the other classes. I didn't change anything there. Also, there are some changes in the translations, so the other languages will need to be updated.

EDIT: The .mo file for the Dutch translation will need to be added aswell since I couln't find a simple way to add it to Github. Shall I email this to you or will you generate one yourself?

[cleverness]

Email it to cindy@cleverness.org please. I won't be able to update the other translations myself since I rely on other people updating and sending them to me.

I usually don't bother changing the version on other files unless I modify them (and remember to update the version).

[JoryHogeveen]

I will send you the translations a.s.a.p.

About the versioning. Why not use the same file-version as the plugin-version? And then the file didn't change, don't update the version of that file. This way you can allways see in what plugin-version this file was modified. Right now the file-version doesn't say anything because you have no idea of how these versions relate to the plugin-version. What do you think?

[cleverness]

That's what I try to do (in general). It's something I often forget to update though when updating a file. I don't update things enough to be seem to be able to get into the habit of doing that.

Thanks for the translations.