These notes cover the steps to follow in order to upgrade major versions of the framework.
Follow the steps below if you're using version 1.2.x and want to upgrade to version 1.2.3.
Habitually minor release doesn't need a manual process but this one is an exception in order to fix the PHP class alias issue. Since release 1.2.0, class aliases have been moved from the theme to the core plugin. The idea behind this was to provide core aliases to the theme but as well to custom plugins.
But we have an issue. Defining class aliases into plugin is prone to conflicts between plugins and the currently active theme. After testing some ideas to avoid name conflicts, it was clear that plugins won't be able to define class aliases or put in other words, won't be allowed to define class aliases using the PHP class_alias function. Developers will have to use PHP namespace and its features for the development of their plugins.
Please note that plugin development is still in its infancy with the framework. Plugin development with full documentation will be available for release 1.3.0. only.
In the meantime, update your project and follow the steps below to get version 1.2.3:
composer updatefrom your project root.
bootstrap/start.phpfile by this one.
config/application.config.phpfile and update the
aliasesproperty with the array list from this gist.
Follow the steps below if you're using version 1.1.x and want to upgrade to version 1.2.0.
storagefolder at project root (same location as your main composer.json file).
storagefolder, create a
composer.jsonfile and set your
start.phpfile located inside the
bootstrapfolder at project root with this file.
functions.phpfile by the one found in the new installed themosis-theme.
bootstrapfolder from the new installed themosis-theme into your own theme.
loading.config.phpfile by the one found in the new installed themosis-theme. PSR-4 autoloading is used in this version. Update your custom classes autoloading statements accordingly.
application.config.phpare now by default defined inside the core framework at least for core classes. You can override their aliases or add yours for your custom classes. If you don't have any custom aliases, you can specify an empty array by default.
editorfields, check the new field documentation and update those fields as their arguments have been changed.
Check the change log page for a list of new features and fixes available. Also, the documentation has been completely rewritten for this release with more examples, make sure to check it out.
If you have an error with your views storage, your project is missing the constant
THEMOSIS_STORAGE. Please check step 5 above to fix this.
Made in Belgium