Introducing LocationGraph to Anahita

Introducing LocationGraph to Anahita

We have just merged our code with the master branch and now officially announcing the Anahita 4.2.0 Embryo release with LocationGraph. That’s right we can now tag actors (people, group, etc.) and media nodes with locations. Anahita allows more than one locations to be added to a node. Here is the LaunchAcademy location node on our website.

Tagging a photo with locations in Anahita

This is the first iterations of this feature which relies on Google maps services. We have considered Open Street Maps but this integration is yet to be implemented. LocationGraph was implemented ahead of schedule by request of few Anahita tribe members who’ve had contributed financially to fund the development of this feature.

The code is now on our Github repository. Being an Embryo release, this is a code that we will be using for a while on our website while making the final improvements and adjustments before it is stable and ready to be tagged as a Birth release.

That’s it for now. There will be more blog posts about this release.

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.7 Birth Release is tagged

A few more bugs that were found this week are fixed in this patch:

  1. fixed the issue which was breaking the actor social graph pagination
  2. fixed the issue which was preventing notification settings to be stored in default layout
  3. changed the label follow/unfollow to get/stop notifications for medium node Subscriptions
  4. medium nodes are enabled by default

To update, go to the root of your Anahita installation and type the following command:

$ composer update

Two critical bugs are fixed in Anahita 4.1.6

During the last 48 hours we discovered two bugs that we fixed right away.

  1. fixed the Remember Me bug
  2. fixed the bug which was preventing new users to update their password after logging in using a token.

Run the following command in the root of your Anahita installation to get the update:

$ composer update

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.