Canada place, Gastown, Vancouver
We’ve just accomplished the most challenging part of which had to do with removing legacy Joomla code from Anahita. We have removed the legacy user manager and ACL (access control list) from Anahita. Then we implemented a lightweight and native ACL for Anahita which only allows 4 access levels:
- super administrator
As you can see a social network doesn’t need too many hierarchies of user types. That is because a social network is a democratic and bottom-up system unlike content management systems that are built for top-down control (hence the word “management”).
User management is now all done in the front-end and uses native Anahita code.
Through the process we have also dropped 6 tables from the database. We have also made further optimizations to make the database schema more organized.
Unfortunately we are still depending on JUser object. That is because in the administration back-end still relies on a lot of legacy Joomla code. The good news is that there isn’t much happening in the administration back-end anymore and by version 4.3 we will rebuild all the administration features in the front-end and completely remove the administration back-end. Then we will be able to completely remove all the legacy Joomla code from Anahita.
In the 4.1.5 release we have made a lot of improvement in the com_people component and prepared it for the time that it will function independently from JUser object.
Make sure that you make a database backup before upgrading to this release. As you can see a lot of changes will be made to your database schema and by keeping a back-up you can recover from any unfortunate incidents. Otherwise enjoy this release. You will notice a performance improvement and there is less code on your server.
How to upgrade
To upgrade your installations:
- make a backup of your database
2. in the root of your Anahita installation run the following command to get the most recent code:
$ composer update
3. then run the following command to migrate up your database:
$ php anahita db:migrate:up
4. in the administration back-end go to the global configuration, turn cache off, save, turn cache on, save again. This will clear your cache.
5. login in the front-end of the site and see if everything is working. If you needed help, post your questions on our Tribe Support group so others can help you out.