Reddie's weblog

Sometimes, you hang on to the old stuff as long as possible. One of my clients had an joomla 1.0.15 site, which didn't change that much over time, so we hadn't taken the time to migrate to 1.5. Time to make a change...

The remaining step for my migration to Joomla 2.5.1 was to install my extensions and ckeck if all is working.

Installed the most recent version of Easyblog and ArtBook. ArtBook is using Joomla content for display, so no additionel steps were needed besides checking the module parms. For Easyblog I had to export the easyblog tables from my old database, change the prefix to my new database's prefix and import it in the new database. Installing Easyblog's modules and chekcing the module settings and that was all there was to it. Really. Found another twitter module (again from RocketTheme) and published that and for now... I'm done.

Now that I got my templte working it is time to start fixing things in my joomla 2.5.1 installation. Following the guide / log from the SP upgrade extension, we'll see how far we get with the basic stuff and then it's time to start replacing the not upgraded stuff like editors, extensions and plugins.

Well. A RocketTheme template with the Gantry framework proves too much for the SP upgrade migrate-template option so it is time for plan B.

Plan B is: install the original RocketTheme template in the joomla 1.6+ compatible version, then replace images, css files and settings back to my changed layout.

So I migrated my site from joomla 1.5.25 to joomla 2.5.1 with SP upgrade. This extension also made a template migration. Let's see if we can install it and get my layout back.

Plan A, migrating from Joomla 1.5.25 to Joomla 2.5.1 did sort of work, but not good enough that I was happy with the results.

Time for plan B.

Plan B is simply migrating NOT with jUpgrade, but with SP upgrade, a commercial migration tool, which hopefully, - they promised on their website- will leave all article ID's and such intact, therefor less to fix after migrating.

Today, I started with my first trial migration from Joomla 1.5.25 to Joomla 2.5.1.

Used my own site for this, I kind of want to be on Jomla 2.5 asap.

Since I am seriously thinking about upgrading to Joomla 2.5, I need my own company website up-to-date. Time to update Easyblog to the newest, joomla 2.5-ready verion: 3.0.7796.

It was as simple as it said it would be, just install through the back-end and all is said and done.

Today was a nice day to try and update a Joomla 1.7.5 site to Joomla 2.5.1.

An ideal site to start with as it has only a couple of menu items with single pages and besides the JCE editor only one extension, Easyblog, with, really, only one blog-itme.

So what can go wrong, huh? Apart from some hickups, basically nothing and all is running smoothly.

 

Since the automated update manager in my joomla 1.7.3 website suggests updating to the newest 2.5 and I thought that was a big leap since it was only released yesterday, I wanted to update to 1.7.4. So I did, the old-fashioned way, by downloading the patch, unzipping it on my local machine and update it through ftp. Worked like a charm.

Joomla 2.5 has been released on January 24th, 2012.

On the same date, Joomla 1.7.4 was released as a security update. The funny thing is, one of my live sites with Joomla 1.7.3 gave me version 2.5 through the automated update process (didn't go for that just yet) but my test environment with Joomla 2.5.0 RC1 reported no updates.

I was kinda hoping that one would have an automated update to the stable version. No such luck :-(

Today, I've updated my Easyblog to the newest 3.0.7073. First thing to notice is that I cannot add a tag to this post. D'uh...

But otherwise, everything looks okay.

 

I totally skipped Joomla version 1.6 but since I had to convert a site for a client from XHTL/CSS to Joomla, I couldn't resist and installed Joomla's newest version 1.7.

Op "Independence day", 4 juli 2011, is WordPress 3.2 uitgebracht. Deze release wordt geacht sneller te zijn dan vorige releases en het admin dashboard heeft tevens een nieuwe frisse look.

Today, I've updated a site from WP version 3.1.3 to 3.1.4.

I've built a template in WordPress for a client and it is my first WordPress experience. Now, I can see in the WP dashboard that it needs an update to version 3.1.3, so how about doing that today...

Today, I updated my Easyblog component to the newest version, 2.03647. Brand new admin look, and did some changes on the layout, too.

Updated my own site. Several components had newer versions, like Easyblog, RSFirewall, RSSeo and the JCE editor. So now we are up-to-date once again.

Another update of EasyBlog and layout problems fixed. Turned out they adjusted something in their language fields and of course, those changes aren't made in your own template files. So could fix it, but not amused...

After updating to version 1.8.152, I  lost some layout-thingies. ANd here I was, figuring I'd covered that when I created my own theme. Apparently not so gotta fix that, after I update to the newest version...