Since Joomla 3 was released, content articles have had an option which can be selectively enabled to allow version control - saving a specified number of previous versions where changes are made to the content or settings of an article, and permitting rolling back to older versions.
This article will explore how to enable and use the version control system, a later article will explore how you can effectively version control all your editable content with a couple of handy plugins.
One of the hidden gems which appeared with the 1.6 version of Joomla is the Redirect Manager - a simple system which allows you to identify and fix broken links. Before the Redirect Manager was introduced, the only way to find and fix broken URLs was to use a third party extension, an SEO scraper such as Screaming Frog, or looking in your server logs.
Although the redirect manager has been around since 1.6, many people don’t know it exists, let alone use it to improve the optimisation of their websites. Often, if you just want to be able to identify and fix broken links you don’t want to have to install extensions with lots of other features which could potentially slow down your site or cause other SEO-related problems - especially if you don’t need the extra features!
A question we are asked time and again by business owners who have a Joomla website is when should they migrate to the latest version. It's a difficult question to answer because no one size fit all method can be applied due to the variety of different ways Joomla can be used, but here are some of the key decision points to help you plan when you should migrate your Joomla website.
Security is something that always seems to be in the headlines - especially when it comes to websites and servers being hacked or organisations losing important data. The Joomla! project takes security very seriously, and over the years has led the way for millions of websites around the world to take advantage of these advances.
The latest version of Joomla! which is currently a short term support (STS) release - 3.2 - introduces some pretty significant features, one in particular which we will be implementing for all customers moving forward - two factor authentication.
The web is, undoubtedly, a wonderful resource, it allows us to quickly and easily find information on almost anything. When it comes to servers and websites, however, it can be incredibly dangerous if you (or worse, the author) do not know what you/they are doing.
I was browsing to see if there's a better way to reset a users password from PHP than the method I usually use, and stumbled across this tutorial. Quite frankly, my chin hit the desk at the advice being offered.
In all fairness to the person who posted the tutorial, they have attempted to mitigate some of the serious security concerns, but despite that, it's still a security nightmare. What makes it worse, is the comments below indicating that some users are blindly copying and pasting the PHP and following the steps without even a base understanding of how it works.
In this post we'll be looking at what the tutorial suggests, and why it's a bad idea.