FTP

  • Adding a new Joomla Super Administrator via phpMyAdmin

    Sometimes the Joomla site owners get a bit paranoic after a time, due to lot of hype about site security. Basically is nothing wrong with, a good site security is based on keeping your accounts secure. But what about when you are hired to do something in a Joomla site and you got ALL access (including FTP and database access) but you discover, that the Joomla account you received is only an Administrator. You can do a lot as an Administrator - but often not enough! Don't tell me, that this never happened to you - unless you are a Joomla rookie. What you can do?

  • Akeeba Backup

    Generally, backup is something you need to breathe, not just use, if you are in this business. It's the number one security tool. Having a fresh and usable backup can be a life saver in a number of situations, not only when your site is hacked, but on a great number of other situation, beginning from human error (accidentally deleted key parts of site - or just forgot to pay your hosting bill) to situations out of your control, as a hardware/software failure. And is essential to have an easy to use tool to move your site around - from local development environment to live hosting, or from one server to another. Enter Akeeba Backup (former Joomla Pack), a must have tool for any Joomla webmaster.

  • Block unvanted visitors using their IP address on your Joomla site?

    Sometimes you need to block a certain IP address, a group of addresses or certain hosts from accessing your Joomla website. Reasons may include:

    • It's a hacking attempt coming from that IP
    • Someone is scraping content from your website
    • A brute-force attack (in most cases a DoS - Denial of Service - attack is originated from that IP (there are too many requests coming from a particular IP
    • Someone continuously spamming your website
    • Some content from your site (images, media files) are hotlinked from your website.

    The solution is simple, but is advised to apply first other tools to stop these bad guys - overuse of this tip can slow down your site considerably, use it ony if you don't have anything else - or you are in hurry to stop an ongoing attack.

  • How do you change the password for your Joomla database

    This is a two step process, and here I'm assuming that you are clever enough and you are hosting with a company that offers cPanel Wink. On other hosting environments the process might be slightly different, but the basics are the same.

  • How to install Joomla to GoDaddy

    Even if hosting Joomla on GoDaddy can be challenging, and anybody ever built a site on their servers will tell you to turn to some better Joomla host, many people still choose them because of the excellent price/offering ratio. Here are a few tips that will help you get Joomla running on GoDaddy with minimum fuss.

  • How to upload pictures to the site?

    The use of pictures in Joomla is a bit different from the methods you are used before, so you need to learn new habits here. But the first problem is usually not that, but how to upload those pictures to the site.

    First of all we strongly recommend some additional components to your Joomla site, if you don't have done allready.

    On the top of these recommended add-ons are the file/FTP managers joomlaXplorer/Ninja eXplorer/OSE Filemanager and the WYSIWYG editor JCE. We will use both recipes here.

  • Invalid Token, in store config - when try to upgrade VirtueMart

    Time-to-time I am hitting the wall with this, even with 100+ VM sites in my portfolio, and parts of VM core having my signature. Here are few tricks wich usually solves the problem.

  • Move your config file outside of webroot

    This is a core hack. Files you change as described on this page will be overwritten during updates of Joomla!

    This tip explains how to move your configuration.php file outside of your webroot as well as making it unwritable by the server. That makes it nearly impossible for someone to corrupt or gain access to the information in the file.

  • XML Parsing Error at. Error

    After moving a site to a new server I found this error in the backend - at least one error per page, but casually even more.

    XML Parsing Error at. Error

    No error number, no line number... What a heck!