EveryCal+1 v2.1.0 Released

Announcing EveryCal+1 version 2.1.0. Changes include:

  • FullCalendar library updated to 1.6.4 – includes new visuals
  • New options to use CDNJS for FullCalendar
  • The Event List shortcode now uses the settings feed icon instead of the fixed calendar icon
  • and added support for CiviCRM events

Thanks to the team at Tadpole Collective for their support and testing of the CiviCRM extensions.

As always you can read more about the plugin on the EveryCal+1 page or through the WordPress.org plugin repository.

0

WordPress Apache 2.4 Varnish Tutorial

I’ve just published a new tutorial titled Apache 2.4 Varnished CHROOTED PHP-FPM WordPress Virtual Hosts. The tutorial outlines how to configure an Ubuntu Server 12.04 LTS to run:

  • Apache 2.4 with the Event MPM
  • Individual user virtual hosting
  • Each user having a CHROOT’d home directory
  • PHP5.4 with APC
  • WordPress (naturally)
  • Varnish Cache
  • and a few other things (such as MOD_WSGI)

It’s really, really long so have fun reading!

0

EveryCal+1 v2.0.0 Released

Just a quick announcement post to say EveryCal+1 v2.0.0 has been released.

New features include:

  • Support for widgets
  • Mapstraction allows extra map providers
  • Fix issue with HTML entities rendering as for example: &

You can read more about the plugin on my EveryCal+1 page and download the plugin from the WordPress plugin repository.

0

MySQL & Logrotate: Error running shared postrotate script (replication)

Recently I setup MySQL replication between a few servers. I setup replication for all databases so everything is copied to all replication servers. After doing this I kept getting daily emails with:

/etc/cron.daily/logrotate:
error: error running shared postrotate script for '/var/log/mysql.log /var/log/mysql/mysql.log /var/log/mysql/mysql-slow.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

Google is wonderful and pointed to this and this which both point out the issue is usually caused by the debian-sys-maint password being incorrect. If you’re not using replication then just follow one of these guides. If you are using replication then keep reading.

Setting the local servers debian-sys-maint password to the password listed in /etc/mysql/debian.cnf does stop the error on that server. But it causes the error to occur on the other servers in the replication set (because the password change is replicated). What you need to do is make the debian-sys-maint password in /etc/mysql/debian.cnf the same on every server in the replication set and of course make sure that is the real password for the debian-sys-maint user.

0

Analysis of OurSay w/ Julia Gillard

Over the last few days I’ve been doing some public opinion analysis based on the questions and comments on the OurSay Google+ Hangout with Julia Gillard. I’ve written up a separate results page with some graphs, a spreadsheet of word frequencies and a revised top 10 list of questions using a weighted score.

Update 26/JULY: I’ve added a little more discussion about the change in opinion / sentiment. I didn’t write this to begin with because I wanted to think about what the results meant before writing an interpretation.

0