Anahita 4.3.9 Birth Release is out

We have fixed a number of bugs in authentication and session management in this maintenance release. You can see the change log for yourself. To get this update, run this command in the root of your Anahita installation:

$ composer update

Acknowledgements

Our special thanks goes to Anahita tribe member Nick Swinford for reporting bugs and providing PRs on GitHub. We’re so grateful to have him in Anahita tribes.

Our sincere apology for the email flood

We’ve been fixing our email notifications for the last few days. Problem was that php was timing out in the background for the groups with 1000+ followers. So the answer was to enable the crontab to process the emails. To prevent the pending notifications in the database to be sent out, we enabled all the notifications in the database. Unfortunately that wasn’t enough and looks like a lot of pending notifications that you were supposed to be receiving through the last year got sent out all at once.

We take complete responsibility for our mistake. We really have nothing to say other than an apology and doing our best to prevent such an incident next time.

Update: Nov 11th – 1:13 AM

Still working with the Rackspace engineers to fix an issue. We rebooted the server to prevent more emails to get sent out. Unfortunately an update in Cenos is having conflict with Rackspace systems and we can’t even login to bring the site back up. Stay tuned for more updates.

Update: Nov 11th – 3:30 AM

It is 2.5 hours later and we are still working with the Rackspace team to bring back our server. This has been one of the toughest nights we’ve had in the history of Anahita project. A notificationmageddon and a server reboot issue right afterwards. We are getting there though. Stay tuned for more updates.

Update: Nov 11th  – 4:00 AM

We’re back online. Rackspace support team and engineers were amazing and very helpful. We really appreciate the time they put to debug the issue. Thankfully it is a long weekend which means we have work to do to fix the notification bug. The silverlining is that it’s better if it happens to us first instead of your projects.

This was one of the most challenging nights in the Anahita history. Knowing that, we’ll get over this too.

Eating your own dog food, can sometimes make you really sick!

Update: Nov 11th – 2:20 PM

Rogue notifications are stopped now. Thank goodness for the long weekend which allows us to focus on fixing this issue which was the result of a code logic bug and server configuration. We’re going to simulate and fix the issue on our development machines and post a report for you. That’s so you’ll be prepared if you had to deal with a similar scenario in the future for your projects.

In other words, we sometimes break things here so you don’t have to.

Update: Nov 11th – 11:50 PM

There was no bug in Anahita. It was our server configuration which lead to the rogue notification issue and an error in our migration script. All issues are solved now and server is performing as expected. Situation is rolled back to green now.

Anahita 4.3.8 Birth Release is Available

This release comes with a number of bug fixes, enhancements, and a bit of extra speed. You can go over our change log to see it for yourself. In summary:

  1. the bug that prevented users to stay logged in has been fixed
  2. added blockquote tag to the editor
  3. did some house cleaning in the code which resulted into a slight speed enhancements too.

How to upgrade

If you are upgrading from version 4.2 or earlier please read this article which shows you how to upgrade your code, data, and apps.

If you are upgrading from any of the version 4.3 releases  use the following command in the root of your installation to get the updates:

$ composer update

and then

$ php anahita site:symlink

There is no need to run any database migrations.

Anahita 4.3.7 Birth release comes with google reCaptcha to protect you from bots

Google reCaptcha plugin for Anahita
Google reCaptcha plugin for Anahita

Looks like Anahita is getting noticed by bots, so we decided to include a new plugin in our list of packages to protect your Anahita installations from them. The new plugin adds invisible Google reCaptcha to the login, registration, and add Group forms.

If you are upgrading from previous 4.3 release, simply run the following command in the root of your Anahita installation:

$ composer update

There are no database migrations in this update.

Installing the Google reCaptcha plugin

Just like installing any other Anahita apps, use the following command to install the Google reCaptcha plugin:

$ php anahita package:install recaptcha

This command installs the plugin on your Anahita installation.

Then login as a Super Admin and go to the plugin edit page:

Site Settings > Plugins > Google reCaptcha

You need to sign up with the Google reCaptcha service and obtain a Site Key and Secret Key. After adding those values, set the plugin to enabled and save.

Open a new browser window in incognito mode and go to the Anahita’s login page. You should be able to see reCaptcha badge in the lower right side of the screen. Try logging in; you should be able to login with no difficulties.

We are using the invisible Google reCaptcha service. It is smart enough to tell if a user is a bot or not in the background. If the user is suspicious, then it will launch a challenge window and asks some questions before allowing the user to login.

Acknowledgements

Our special thanks goes to Anahita tribe member Nick Swinford for collaborating with us on development and testing the reCaptcha plugin.

Anahita 4.3.6 Birth Release is available

This is a maintenance release with bug fixes in the Subscriptions app. Upgrading your installation is quite easy. If you have installed Anahita via Composer then use the following command in the root of your installation to get the updates:

$ composer update

If you are using the Anahita master branch on Github, just use the following command in the root of your Anahita installation:

$ git pull

There are no database migrations in this release. If you encountered any issues, please start a topic on the Tribe Support group.

Here is the change log for the 4.3.6 release.