The ability to create search engine friendly urls has been available since the release of Joomla! 1.5. Joomla provides two methods for creating search engine friendly urls. The default option is without mod_rewrite which means that the urls still contain the index.php reference in the url. The second option involves removing this reference via the use of Apache mod_rewrite.
To enable url rewriting in Apache, the htacces.txt file needs to be renamed and there are several steps to follow.
This article on our knowledgebase will guide you through the correct procedure for renaming htaccess.txt to .htaccess.
To make small css edits to T3 templates, we usually recommend using the custom.css method as it is convenient (the file can be edited in the template administration area), the code is not affected when updating the template and it keeps your code separated from the compiled LESS files (which makes it easier to debug and keep track of if you need to troubleshoot your changes). It also gets loaded on each page using the template regardless of the selected theme, making it good for site wide structural changes.
However, as all T3 templates are built using LESS, it is also possible to override or add LESS syntax without it being wiped out when upgrading the template. This is a somewhat advanced technique and should only be attempted if you are experienced with LESS or feeling adventurous.
All our newer Joomla templates are available as a Joomla 3+ quickstart package and contain a copy of the JoomlaBamboo template demo site (there are some instances where the quickstart package differes from the demo site)
A Joomla 3+ quickstart package contains the Joomla 3+ content management system files together with the template, extensions and sample demo data.
Anthony has spoken before about why he chose Siteground to host the Joomlabamboo website, but during some recent googling I was even more impressed with the choice when I found that SiteGround hosts in excess of 100,000 Joomla sites and even operate their own in house Joomla security team. I was actually googling for something completely unrelated but stopped to check out this video about Joomla site security.
This video provides an indepth look at the 8 most common hacks of Joomla sites seen on sites hosted by Siteground and also (and importantly) how to prevent your site from becoming compromised.
One of the interesting new features in Joomla 3.2 is the ability to manage the Joomla CMS Configuration details from the front-end. This means that you can now change certain but not all website configuration parameters from the front end of your website.
In previous versions of Joomla, you are able to change the articles as well as categories and use that latest version only. In the latest version of Joomla 3.2, you can make changes and keep track of the changes, make comparisons or restore all changes that have been made. Content versioning is one of the key new features of Joomla 3.2.
I've received this odd error a few times now as I start to move some of our older non Joomla 3 templates from Joomla 2.5 to Joomla 3. Despite the fact that Joomla 3.2 is well and truly out, the updater tells me that I have the latest version of Joomla.
This usually happens when the Joomla updater is set to look for releases only in the long term stable stream. Joomla 2.5 is the current long term stable release and it will remain the case until Joomla 3.5 is released.
So even after I switch the Joomla updater to look for the short term releases (ie Joomla 3+) it still tries to assure me that I have the latest version.
Fortunately the issue is easily solved with a slight detour from the main Joomla update component to the update manager in the extension manager.
Now if you are like me, even after this update you may get a blank screen but fortunately this is also easily solved. Check out the How to Joomla post I published last week about how to solve a blank screen after updating to Joomla 3.2.
In the process of updating some of our Joomla template packages from Joomla 2.5 to Joomla 3.2, I've just come across an easily circumvented bug during the update process.
The error occurs during the installation of the Joomla 3.2 via the Joomla Update component and ends in the user being presented with a blank screen. In most cases a blank screen means that there is a php error and because error reporting is set to default the error is not displayed on the screen and so all we see is a blank screen.
T3 has a powerful, flexible and feature rich mega menu built into it's core. One of the features of the megamenu is the ability to create multiple columns in the dropdown menu. This article describes how to split a submenu into the multi column in your T3 based template menu.