Looks like I found the culprit that caused my PlugIns to disappear on my MT 3.33 installation. Turns out it was my old friend SELinux!
This had crossed my mind before but the fact that it was working at one point and then just ceased working caused me to dismiss SELinux as an issue. Maybe something was updated in the upgrade process that Fedora uses and altered the SELinux policy after the upgrades were installed. I'm using Fedora 6 on this new system which I'm still configuring Movabletype and other applications on before making this system my new web host.
I'm very surprised I have not ran into this issue on my current MT 3.2 installation.
I cannot take credit for the fix though seems that Sixapart advised the fix a while ago to a user who ran into this with Fedora 4 MT 3.2.
I found the following fix via a Google search on the user's Sixapart blog they recommended the fix to who was giving details of his upgrade from MT 2.66 to MT 3.2.
Here are the contents of what I found and it worked for me:
####################################################################################
Do you have SELinux enabled on this server? You can run "system-config-authentication" as root to verify that this is enabled. The settings of SELinux are what caused the PlugIns to not be seen by Movable Type.
In this file: /etc/selinux/targeted/contexts/files/file_contexts
there is this rule:
/var/www/cgi-bin(/.*)? system_u:object_r:httpd_sys_script_exec_t
That rule basically means that the /var/www/cgi-bin directory (and all subdirectories) have a "httpd_sys_script_exec_t" context. Meaning that CGI scripts can execute from this location.
In the case of the /var/www/cgi-bin/mt/PlugIns directory, each Plugin directory (and the /var/www/cgi-bin/mt/PlugIns folder itself) should have a context type of httpd_sys_script_ro_t. This allows read-only file access to the directory and files and also execute permission.
To adjust the context for the PlugIns folder, use this command:
chcon -R -t httpd_sys_script_ro_t /path/to/mt/PlugIns
####################################################################################
Now I'm continuing to go ahead configuring this new web server for testing and then roll-out!
I also posted this to Sixapart forums: http://forums.sixapart.com/index.php?showtopic=59878
I also just completed pointing this system to my other WAN static ip.adress on my other router, pointing my Apache web server to the second NIC I just installed a couple of days ago and I'm ready to resume configuring Movabletype to move the content over to this system. I also had to rebuild my blog pages and edit my styles CSS file to point to the proper ip.address I'm using for testing purposes.
Why do things like this get fixed late at night give you some energy to start configuring more until you hit a new issue and then you end up with very little sleep?
Well this time I'm going to go to bed like I should........ but let me do a few more things first.....
Leave a comment