I often find when I’m writing a WordPress Plugin, especially when it is used in the Admin area, that I need to use a Session Variable to communicate selection/filtering criteria from one screen to the next. One WordPress Plugin that I have found works very well for this is Simple Session Support by Peter Wooster. This plugin allows you to set and test (isset()) standard PHP $_SESSION variables.
The new auto update feature that arrived in one of the recent releases of WordPress may seem like a good thing on the surface, but can cause terrible problems. I recently had one of my websites completely destroyed because of the auto update that was applied. Ask anyone who has been around IT for a while and they will tell you, the first thing that you should do before applying a software update is take a full backup of your files and your database before applying the update. When you are using auto update it just does it for you and you don’t have the opportunity to take the backup first. I would always recommend applying software updates to a test environment first, to make sure that it is not going to break anything, before applying it to your main production website.
Here is how you turn the auto updates off. Go into your wp-config.php file in your website route directory and add the following lines down towards the bottom of the file, just before it says “That’s All. Stop Editing”:
/** Disable Auto Updates of the WordPress software */ define( 'AUTOMATIC_UPDATER_DISABLED', true );
I recently built this site on a little DigitalOcean.com “Droplet” server and went through the process of manually building a WordPress environment from scratch. It was the first time that I have ever installed WordPress this way and on the whole it went very well. Digital Ocean has published a number of excellent instructional “how-to” documents and the one I followed was “How to install WordPress on Ubuntu 14.04“. The process went very smoothly right up to the point where I changed the Permalink setting so that the URL was build using the Page Name rather that the page number. As soon as I did this the whole system locked up and I kept getting the “403 Forbidden” message no matter what I tried to do.
The problem came down to be the .htaccess file (which is a hidden file found in the root directory of the website) that is generated by WordPress when you make this Permalink change. The generated .htaccess file is :
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
The solution came down to adding an extra line of code in the .htaccess file so that the final file looked like:
<IfModule mod_rewrite.c>
Options +FollowSymlinks
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
Once I added the “Options +FollowSymlinks” line the 403 Forbidden problem went away.
Copyright © 2024 WordpressNotes.org.
Recent Comments