Joomla is an easy-to-use content management system. This software is based on the Internet. By implementing this system on your host you will be able to store files, text, and display images in an organized way. Here, we will analyze various issues and problems of Joomla and try to give a solution for each of them, so study the article on troubleshooting Joomla errors on DirectAdmin carefully if you encounter any of these problems.
Joomla is an old site builder based on PHP, which is very popular, and the main reason for its popularity is its easy installation with a few clicks. That means you can program your website without any technical knowledge. Also, website designers and internet users prefer Joomla for website design. Because it is a free content management system and has a beautiful GUI that is easy to develop.
As you decided to install Joomla to build your site and work, you may encounter different problems and errors. Here, we will introduce and analyze some of them.
When you want to enable the cache plugin in Joomla 3.x, you may encounter the error ERR_CONTENT_DECODING_FAILED and stop rendering the page. The cause of this problem is that the cache plugin doesn’t properly support Gzip compression. Even if you enable it by the server.
Solution: You can disable Jzip-compression:
Go to System -> Configuration -> Server and GZIP-Compression to No
Tip: If you are unable to access the website’s backend anymore, you can find this setting in the /configuration.php file. The option can be set like this:
public $gzip = '0';
Three reasons may cause these problems:
1- There is no tmp directory or it is not located correctly in the configuration.php file.
2- The tmp directory is located but Joomla is not allowed to write to it.
3- Joomla is not allowed to write to one of the following:
directories: /administrator/components, /administrator/modules, /administrator/templates, /components, /modules, /plugins, /templates.
The last one is very common and usually happens when there is a problem with Joomla’s hosting environment.
Solution 1: You can create the tempt directory if it doesn’t excite and give Joomla the proper permissions to write to it, there is a quick and dirty solution that is effective but will render your website completely insecure. Chmod the following directories to 777 through the FTP client:
/administrator
/administrator/components
/administrator/modules
/administrator/templates
/components
/logs (not necessary to solve this problem but if Joomla has write permissions across the board then doing this will ensure that you don’t have a problem elsewhere on your website)
/modules
/plugins
/templates
/tmp
This is a temporary solution.
Solution 2: There is another solution but it is the best one and requires that you have FTP access to the website. Using the following commands, Apache can create files or folders in the server’s file system. Follow the instructions below:
– Use the Cpanel file manager to zip the Joomla website and name the resulting website joomlawebsitebackup.zip. The resulting file should be pressed into the main folder of the website.
– You should add 1_ to top-level folders and files in Joomla. That is, to remain the folder administrator to 1_ administrator and index.php to 1_index.php.
– you should create an unzip.php file with the following codes:
open('joomlawebsitebackup.zip'); if ($isZipOpen === true ) { $objZip->extractTo('/home/[yourcpanelusername]/public_html/'); $objZip->close(); echo "unzipping finished"; }other { echo "unzip failed"; } ?>
Go to yourjoomlawebsite.com/unzip.php. and run unzip.php on your browser. Then you will see the message contain telling you the PHP script has been unzipped.
Now test your website. When you became sure about the proper functionality, delete all folders and files that start with _1. once you are done, do another test, to make sure everything is correct.
Joomla is a type of CMS that provides a high percentage of memory and sometimes a lot of memory is needed to process a page especially if the page has a lot of third-party extensions. So when a client tries to run an extension, encounters an error about “Allowed Memory size”
Solution:
You should increase the PHP memory limit. You can increase the memory limitation in 4 different ways:
1- Increase the PHP memory limit at several levels: It can be done if your website is running on just a dedicated server or VPS. To do this, visit our website for cheap dedicated server plans.
2- Increase the PHP memory limit at the application level: It can be done by making a copy of the global php.ini
3- Increase the PHP memory limit at the .htaccess level: add the below line for this reason to the beginning of .htaccess file:
php_value memory_limit 512M
4- Increase the PHP memory limit at the code level: Add the following line to the beginning of your index.php:
ini_set('memory_limit', '512M');
This error will occur when you want to rename the username of the Joomla site and change the change_username.sh. So as a result, you will discover that Joomla hardcoded paths, especially username and as I turned back to the old username, Joomla says that it failed to connect to the database.
Solution: This problem can be dependent on the number of characters in the username. While this number is 16 character capacity for db usernames. This amount is 14 for DA in addition, 1 for underscore, and 1 for db name. Also, DA analyzes for valid usernames and also there is a setting for that in directadmin.conf.
For example:
max_username_length=10
So, if your username number is 13, as your limitation is 10, DA is going to consider it invalid and will not display it until you enhance the limitation in directadmin.conf. Keep your username below the limitation. change_username.sh script will not go through any of your PHP files. So, you have to set config paths manually.
When you try to move your site from Cpanel to DirectAdmin, it is successful. But, when you try to access any page suddenly you receive a 403 error.
Solution: The reason is that, upon extraction of the Gzipped backup which you move from Cpanel permissions of public_html changed to 750. But these permissions should be 755.
Here, we tried to make you familiar with troubleshooting Joomla errors on DirectAdmin. We divided the issues and give solutions for these problems. So read this article carefully. We hope this was a helpful article for you.
Tags
You can meet all your online needs with a simple one-step solution, this solution is Canada RDP or R...
Tags
In online businesses, maintaining customer security and brand reputation is very important, So these...
Tags
