Gallery 3 Project migration – progress 07/23

While having late evening tea I want to share the progress made with GD Theme.

This is the first Alpha (download link).

To replicate look and feel of my test site you would need the following plugins from Piwigo site:

  • Additional Pages – needed for root page support
  • Extended Descriptions – allows embedding slideshows and building custom pages
  • GThumb+ – nice thumbs layout

Plugins can be installed from within Piwigo admin area.

Theme would need to be manually unpacked and copied to themes folder.

It is barebones version with only one colorpack – slateblue

I do not plan to support embedded framepacks at this time but instead take approach of GThumb+ plugin – once installed, it customizes how thumbs are styled and constructed.

PS: for some reason GThumb+ does not support Thumbs in album view, so there is some opportunity there to expand, but I really like the feel of it.

I do plan to release several Thumb plugins to accommodate various designs, but it would be at later time.

Also there is a plan to either be able submit root page template into Additional Pages plugin or allow user manage it independently.


Posted in Gallery 3 Development, Piwigo, Technology | Leave a comment

Gallery 3 Project migration – progress 07/11

To keep you updated on the progress, GD theme is taking its form
Few previews:

Posted in Gallery 3 Development, Piwigo, Technology | Leave a comment

Gallery 3 Project migration


As you know by now Gallery 3 Photo engine is hibernating. I decided to explore alternatives. Please note that unless I comfortable, I will be keeping my main gallery live while building up pieces using my new engine of choice.

As a long time G2/G3 user and seasoned plugin and theme developer for Gallery for past many years, while have a sad feeling, I have wisdom of knowing how things work and what to expect.

In this series, I will be posting my short notes on my experience migrating my photo site to new engine.


  • Ideally 1:1 replacement – which means…
  • Keep it private, private … Ability to host locally, i.e. gallery engine is not linked to any particular host or OS. LAMP or WAMP stack.
  • Ability to create custom themes (everyone wants to be unique or at least have variety of choices how gallery looks like)
  • Ability to create plugins. I would expect gallery engine to have number of plugins already available, but I do want to have ability to customize/extend it further nevertheless
  • Ability to move my content with as little effort as possible (local import, self organizing of the files)
  • Light resource requirement. Ability to import large photos.
  • and ability to use shared hosing which
  • Not as important for me, but should allow multilingual support
  • Image and Video upload support
  • User, User groups and permission setup

“Shared” Solutions

there are plenty of “shared” photo storages on the market and “public” storage is ok for you take a look at the following:

  • off course, you can always use FB for the whole world to see and for FB to monetize :)
  • Or Google flavored – Picasa

“Local” Choices

There are many around, but I would consider

Making personal choice

In the end it all comes to personal choice, so take it with the grain of salt and evaluate if solution works for you…


For few years now WP has Photo Gallery support. It is blog integrated and is very simple to use and customize. However if you have large number of photos to post this option may not work for you.
Being familiar with WP and using it as a blog engine but as  I am not planning to merge my blog and my photo gallery, I am going to skip on reviewing it here.


I was keeping eye on the project for some time and I do like it. Project is well established and have plenty of plugins and themes.

Install was  easy and I was able to import most of my photos… until large files were to be processed… and it failed… Turns out ImageMagic with my shared hosting just did not have enough juice to be able process images even on basic level to extract metadata.

Please note that it could be a that there are some tweaks required (I did some changes in G3 for it to work in the same scenario, but this is exactly what I am trying to avoid in my review process).

Bummer… so I would still recommend to take a look at ZenPhoto and consider it as a possible solution for you… but for me, I am moving on…


Well established, but too “old-looking”. This project is still going strong and active, but to my taste it is “legacy” solution. While it still have a lot of nice features, way it is organized is just not for me.


If you do not mind French here and there, take a close look at this little beauty. :)

Let’s look at my checklist above:

  • It is not 1:1 replacement, but close enough
  • I can host locally on the LAMP stack without changing hosting
  • I can inherit or create custom themes. In fact, it is somewhat easier with Piwigo
  • I can create plugins and there is plenty of existing one.
  • Local import and self organizing of the files is supported
  • Light resource requirement. Ability to import large photos.
  • I can keep my shared hosting
  • Multilingual support
  • Image and Video upload support (additional plugins may be required)
  • User, User groups and permission setup

Now the experience:

  • Deployment was a breeze – you can do full code deployment or use “pull” method and all components would be downloaded for you, you just need to deploy one file and setup your database. Rest will be done during setup.
  • I have uploaded my var folder from G3 and run Sync. All photos (2000+) was imported into gallery tree and appear in the gallery. No hiccups, no resource issues.
  • There is G2 import plugin you can install and try. It may even take G3 photos, but I did not try it. If G3 is the issue, someone may try to adjust G2 version to take G3 content especially if you have a good amount of metadata you need to bring across. I opted out to import images only.
  • Aside from few default themes installed by default, you can pull number of other themes from repository along with various plugins. There might be some things missing which I am used to with G3, but I do not consider it an issue as I can migrate missing parts myself.
  • If you are looking for GreyDragon Theme – I started process of migrating it over Piwigo and will make it available in next month or so. If you’d like to help testing it, please let me know. Just do not expect full port immediately.
  • If you are looking for any of my plugins which do not have equivalent at Piwigo already, please let me know and I will consider the port.


  • There is a code repository if you like to have access to raw stuff
  • Along with bug tracking system
  • Looking for ideas for your new gallery look, visit showcase section.

Americans beware, or not :)

Piwigo is started by Pierrick Le Gall, French and you would find some number of posts or plugin’s descriptions in French.

Do not be discouraged by this :) people in Europe can speak 2-3 languages fluently and usually English is one of them. So have question or two, visit forum and ask.

PS/Edit: Read above with smile. How Pierrick highlighted in his comment below, Piwigo is international project and anyone will feel right at home regardless what language they speak.


I am on my way to move my gallery to Piwigo. You can find it at this temporary URL.

You can follow visit this blog for more details as I will be posting updates and in some near future will be making GreyDragon available for testing and then official download.

Once I migrate the content, theme and necessary plugins I will replace my G3 powered Gallery. In the mean time you are welcome to visit and share your comments and ideas.


Posted in Gallery 3 Development, Piwigo, Technology | 27 Comments

How to upgrade mySQL on CentOS

By default CentOS 6.5 would be installed with MySQL 5.1 (it puzzles my as 5.1 is archaic, but well…). I was interested in updating my MySQL engine to 5.5 and just happen that when it become a necessity. So after browsing various sites, forums and trying different repos, everything boiled down to the following steps…

DISCLAIMER: These particular steps were tested when upgrading default MySQL 5.1 part of CentOS 6.5 with Plesk 12.


  • you are familiar with SSH
  • and have SSH root access
  • Webtastic repo is used
  • Prior MySQL installation exists (check $ rpm -q mysql mysql-server)

Core update

  • Enable repo – Webtatic EL6 for CentOS/RHEL 6.x
    $ rpm -Uvh
  • Install 5.5 side-by-side, replace engine and resolve dependencies
    $ yum install mysql.`uname -i` yum-plugin-replace
    $ yum replace mysql --replace-with mysql55w
  • And the last step system DB structure need to be updated
    This is very important especially if your Plesk backup start failing with the error

    Not all the data was backed up into XXXXXX successfully.
    mysqldump: Couldn't execute 'SHOW FUNCTION STATUS WHERE Db = 'XXXXX'':
    Cannot load from mysql.proc. The table is probably corrupted (1548)
    $ service mysqld start
    $ mysql_upgrade -u root -p

    If for any reason this fails with error

    Looking for 'mysql' as: mysql
    Looking for 'mysqlcheck' as: mysqlcheck
    FATAL ERROR: Upgrade failed

    try the “backdoor”

    $ mysql_upgrade -uadmin -p`< /etc/psa/.psa.shadow `

    If after that error still present itself try to force upgrade by running the same command with extra key

    $ mysql_upgrade -uadmin -p`< /etc/psa/.psa.shadow ` -f

At that point you all set but it is recommended that MySQL service is restarted

$ sudo service mysqld stop
$ sudo service mysqld start
$ sudo service mysqld status
mysqld (pid NNNN) is running...


Posted in CentiOS Maintenance, Scratch Pad | Leave a comment