I am so thrilled to write this announcement from the JJBean on Main Street, Vancouver. Anahita 4.0 Birth release is finally ready. You may update your 3.0 installations by doing a “composer update” command, but DO NOT FORGET TO MAKE A BACKUP OF BOTH FILES AND DATABASE. Also try updating a copy of your Anahita installation on a development or staging environment first to make sure everything will be alright.
So what’s new in this release?
We have added the foundations of tagging graph architecture to Anahita. We have also implemented two of the most commonly used tags: #hashtags and @mentions.
Hashtag is an essential type of graph that is used on social media and knowledge systems. In the Anahita 4.0 we have introduced a new type of node that represents a unique hashtag. It has a unique URL and it renders a list of nodes that contain that hashtag sorted by most recent or relevant nodes. Anahita can also display the trending tags for the the last N days which by default is set to 1. Here are some examples: #Coffee (recent, top) and here are the trending hashtags. You can even narrow the scope of the nodes with a particular hashtag. You can also filter a list of media nodes (topics, photos, etc.) by one or several hashtags. Here are the photos tagged with #Vancouver or #Gastown.
Actors, media, and comment nodes are all hashtagable in Anahita. There is a behaviour class that developers can use to make their own custom nodes hashtagable as well. If your member have prefixed the important keywords in their posts with a # character, the Anahita migration script will convert all those keywords into hashtag records. This process may take some time depending on the size of your community the content.
Another type of graph that we’ve added to the Anahita is the @mention tag. If you add someone’s username prefixed with the @ symbol to a medium or comment node, then Anahita will notify that person and creates a relationship between the person and the media (or comment) that contains the @mention tag. This graph has more purpose than simply notifying the mentioned person. For example the @mention graph can be used to filter all the nodes that a person has ever been tagged in. For example here are all the photos tagged with @rastin
3. Improved Group Actors
Admins and followers of a group can now add their own followers to the group they are administering or following. This feature is added to the com_actors component which means all the custom actor components that extend this component can inherit this feature.
4. Improved Search
The search layout has been improved and now the results are loaded and displayed using the infinite scroll pagination. Hashtags are also displayed in the body of the search results and clicking on them will take you to the hashtag pages.
5. Now with Less Joomla
A lot of Joomla legacy code has been removed from the administration back-end and core Joomla libraries. The two main legacy joomla components which are removed are the com_modules and com_menus.
5.1. No Legacy Modules
The legacy module manager is now completely removed from the system. Also we are no longer using the <module> tags in our layouts to create dynamic modules. All the Anahita layouts are now using standard Twitter Bootstrap rows and spans. All the module positions have been removed from the templates which has resulted to a faster rendering time since the pages now contain less html and nested layers compare to older releases of Anahita.
PLEASE NOTE: if you have custom apps on your Anahita installations that use the <module> tags in their layouts, please make sure to update them to work with the new release. Look at the layouts in the topics, photos, and todos apps as examples.
5.2. No Legacy Menu Manager
The legacy menu manager component has also been completely removed from the system and instead the menus are now simple templates in the base template under html/menus where you can overwrite them in your custom templates. Using the approach the menus render faster and they are localizable. You can also code custom logic inside those layouts, for example: hide a specific menu item from the registered users while showing it to the public.
PLEASE NOTE: Before updating to Anahita 4.0 please make sure to recreate your top menu using an overwrite in yourtemplate/html/menus/main.php we have provided a code example for you on how to create your new top menu.
We have removed the milestones from the Todos app. The process of migration will do a clean job of removing the data and features.
The focus of Anahita 4.1 will be mobile web. We do a lot of mobile app development in our company and we use Anahita as the back-end for the knowledge apps. A lot of the improvements that we make will be available to you as a part of default Anahita distribution.
- Upgrading the CSS framework to the latest release of Bootstrap
- Rebuilding all the UIs following a MobileFirst approach which means we will build the UIs starting with small screens and mobile devices and then accommodate larger screens if needed.
- Additional improvement to the RESTful APIs for developing mobile apps.
- Removing more legacy Joomla code.
Also here you can learn more about the Anahita 4.* vision page.