My name is Joe. I like to think of myself as a web-developer but then during the day, I'm more of an analyst than a developer. I've been writing websites and scripts commercially since 1997 and I'm using this website to store notes as I go along.
I specialise in taking over incomplete and/or bespoke systems which have little or no documentation. I like workarounds and solutions and persist in the knowledge that anything is possible, I only have to believe. I thrive on the challenges that the rest of the crowd so easily give up on.
This website has just undergone an upgrade and is still being developed. I'll grant my loyal visitors that the site doesn't look any different but as a bit of a geek, I can assure you that almost every file has been upgraded!
Thanks for visiting! I hope this website is, as always, of some use to you!
- Joomla CMS v2.5.11 (Joomla.org)
- jComments v2.3.0 (JoomlaTune.com)
- PlayThru v1.1.8 (AreYouAHuman.com)
This article is a follow on from my article JComments 2.3.0 with ReCaptcha (Joomla 2.5.x) but instead of using ReCaptcha, we're going to use an alternative called PlayThru by AreYouAHuman.Com.
The kCaptcha used by the jComments extension is easily automated and no longer blocks spam comments.
So I have come up with what I consider a pretty stable solution. I adapted it from various legacy solutions when using Google's ReCaptcha.
This article details a method we used on a search form in a SQL Server Reporting Services (SSRS) environment. The requirement (amongst others) was that the report ran in less than a few seconds.
Analyzing the report through the ReportServer databases (internal auditing) only showed how long the SQL query would take to recover the data and present it in a report, which would average about 0.4 seconds.
We're obviously not interested in shaving off time from 0.4 seconds; no, we're more interested in the fact that 0.4 Microsoft seconds seems to translate to about 10 minutes in the real world. Where do the extra 9 minutes come from? Not the SQL as this runs in 00:00 seconds in SQL Server Management Studio. Not the internal processing and rendering as the report server says it did this in 0.4 seconds. So where's the problem?
- Joomla CMS v2.5.14
This article is a note on how I fixed an issue on a client site. The website had a redirect on the login which would go to a page accessible by "registered" users but only "Super Users" could actually login. "Registered" users would not be able to login, despite their status in the admin panel saying "enabled" and "activated" (not blocked).
If I used a test account, none of the Joomla groups, not even "Administrators" could login. However set the same test account to a "Super User" and they would be able to login. Was the problem authentication? Restricted access to a component? A load of blab on ACL managers?
In our case, the website had recently been migrated from Joomla 1.5.x to 2.5.x. I asked to examine the database and a quick scan in the assets table revealed 3 assets had the parent_id = 0. Only one asset can have that and that is "root".