Anahita 4.2.3 Birth release update is available

A number of issues are fixed in this release:

  1. starting using SwiftMail and Anahita’s Mailer class instead of legacy joomla mailer
  2. improved the code that sends out notification mails
  3. updated email regex according to the latest w3c specs
  4. added tags url attributes for people, actors, and masonry photos so they can be filtered by hashtag, mention, or location
  5. updated robots.txt file
  6. fixed add/remove location locatable target url bug

Use the following command in the root of your Anahita installation to get the updates:

composer update

The new Anahita Delivers Location Graph and More

Anahita Location Graph

We’ve just tagged the 4.2.0 Birth release on Github and thanks to financial contributions of 3 companies in Anahita tribes, we have finally implemented the location graph and search in the core framework. This feature was planned for future releases, but due to popular demand we decided to implement it ahead of time.

How to upgrade

make a file and database backup of your Anahita installation and then enter the following commands in the root of your Anahita installation to upgrade:

$ composer update
$ php anahita site:symlink
$ php anahita db:migrate:up

Please note: If you have a custom template, you need to rename the directories html/com_html/content to html/com_pages/page because the component com_html has been renamed to com_pages.

What’s new?

Here are the updates in the Anahita 4.2.0 Birth release:

Tag actors and media nodes with locations

Photo Locations - Anahita Location Graph

In this release actors and media nodes can be associated to location nodes. In Anahita you can associate more than one location to an actor or media node. Locations have unique urls that display recent and top nodes associated with them. Checkout these location pages:

Continue reading “The new Anahita Delivers Location Graph and More”

Anahita 4.1.8 Birth release is out

Lost + Found cafe, Gastown, Vancouver

Lost + Found Cafe, Gastown, Vancouver

Greetings from the beautiful Vancouver. This is a maintenance release with the following fixes:

  1. fixed issue with the db table coalitions problem. Now all the tables are set to utf-8 and Engine=InnoDB
  2. fixed issues in the Invites app tokens and UIs

To get the updates run the following commands in the root of your Anahita installation:

$ composer update
$ php anahita db:migrate:up

Anahita 4.1.5 delivers native and lightweight access control

Canada place vancouver

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:

  1. public
  2. registered
  3. administrator
  4. 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”).

Manage people in Anahita front-end

User management is now all done in the front-end and uses native Anahita code.

Anahita database schema in version 4.1.5

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:

  1. 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.

Anahita 4.1.4 Birth release is available

English Bay, West End, Vancovuer

Greetings from the hot and sunny Vancouver. We have a new maintenance release which fixes some really important bugs. To get the updates please SSH to the root of your Anahita installation and type the commands:

$ composer update
$ php anahita db:migrate:up

Here is the change log for this release:

  1. fixed validation of whether an edge had the same node at both ends
  2. migration script to remove all the edges in the database which had the same node at both ends
  3. UI refinements
  4. migration script to change todos_todos table to InnoDB
  5. added an editable placeholder for the photos which had no title or description

Stay tuned for some exciting news that will be announced this week.