Skip to content

Tag: Joomla

Reinstall JoomlaWatch

JoomlaWatch is a great Joomla monitoring component and provides live statistics as to who is visiting your sites. This tool can be used with or without Google Analytics and in many ways I find it to be better than Google Analytics. My biggest problems to date with the component is that it is extremely difficult to upgrade and the documentation is lacking.
Several months back I had been running JoomlaWatch v1.2.6 and decided to update to the latest version at the time, v1.2.12. Looking on the JoomlaWatch component, I was unable to find an upgrade button. As such, I decided to download the latest version and attempt to install it through Joomla. This failed claiming that JoomlaWatch was already installed. Based on this information, I determined that an upgrade was not possible. Looking at the extracted JoomlaWatch zip file, I decided to read the upgrade.txt file. It said:

When you are doing an UPGRADE from some older version
Uninstall from the admin backend #!ERASES!# all the database tables that belong
to JoomlaWatch. But, you can backup these tables with tools like phpMyAdmin, or some
database tools that comes with your webhosting. After the upgrade, you can restore them back.

So what tables do you need to backup, how do you back them up, and how do you get everything working after the upgrade?

The Joomla Transition

I would like to start by thanking everyone for the feedback on the new site! I have taken your comments, questions, and suggestions and made several modifications. One common problem appeared to be the use of the comment feature and as such I have switched to a different application and welcome any feedback on its functionality. I have been doing extensive testing on multiple browsers to ensure that everything is working properly and it this point I believe the only outstanding issues are the voting AJAX functionality on IE6 and the mobile browser layout of the site.
I decided it would be a good idea to start my blogging experience by talking about my website transition. Over the years, my site has changed from HTML+CSS to PHP then into a wiki and now a CMS. PmWiki was my favorite type of website to deploy, but I wanted to try something new. The main reasons for this include the ease of installation, the ability to edit pages through the web browser, the wide range of scripts (called cookbooks), and the functionality to write code in order to overcome limitations of the system. A couple drawbacks to PmWiki included the “hacks” needed to get some features to work (i.e. SSL for edit and login functions only), the need to learn or constantly look up the wiki syntax (problem of every wiki), and the non-Web 2.0 look and feel. With over five years of experience in PmWiki, I feel I have mastered it and while I will likely continue to use this product for side projects I wanted to try something new that is hopefully easier to use for advanced functions.