I solved this error. The problem is I’ve used a mix of upper and lower case characters in my WordPress General setting URLs. To fix this condition, I must use lowercase URLs in my WordPress General setting URLs.
Still no idea that why and how this happened all of sudden. But here is the 2 Solutions I found which is working: Applying anyone will work 1. Comment these two – //define(‘DB_CHARSET’, ‘utf8’) and //define(‘DB_COLLATE’, ”) 2. Use Latin1, (‘DB_CHARSET’, ‘latin1’) However, I am suspecting some attacks on our sever where blogs are hosted … Read more
I wasn’t thorough enough initially. Old wp-config.php files were found in my downloads folder. It looked like these files came from the zip file Duplicator created when copying my live site. These files contained config information to my live site database. After deleting them, the problem has gone away.
Somethings wrong with your permission setting. Login to your server via SSH. You can login using your terminal. I’ve created a blog about how to connect to your server via SSH if you’re using windows. Run the following commands: chown www-data:www-data -R * # Let Apache be owner find . -type d -exec chmod 755 … Read more
I had this problem when I moved a wordpress site to CloudWays which used varnish. I had to find the varnish configuration section and specifically exclude the timthumb.php script from varnish. This solved my issue because each call to timthumb.php to resize an image must be processed and it cannot be cached. I hope this … Read more
How to change wordpress port number to 8000?
This depends on the hosting company configuration, and the best thing you can do is to contact your hosting company so they can explain the rules they use for loading PHP.ini files.
Most likely, you have created custom permalinks that are in conflict with default WP permalinks. Unfortunately, WP doesn’t validate permalinks rules, and it is very easy to create conflicted permalinks rules. Rules have priority hierarchy, and when resolving any request, WordPress goes through the list of rules, until it matches first one. It is possible … Read more
The solution was to allow using .htaccess in /etc/apache/apache2.conf by changing from AllowOverride None to AllowOverride All. More about it here So that section related to my local website now looks like: <Directory /var/www/local.webiste.com/public_html> Options Indexes FollowSymLinks AllowOverride All Require all granted Allow from 127.0.0.1 </Directory>
Front-end pages messed up due to HTTPS