You might find the following rmwp.cgi script useful for removing all WordPress files (except your customised wp-cofig.php). No reason why you shouldn't delete that yourself using FileZilla if you want to.
[code=rmwp.cgi]
#!/bin/bash
#
# rmwp.cgi
#
# this script removes wordpress files (except wp-config.php) and subdirectories
# from the directory in which this script resides
#
# Header tells browser what to expect.
echo Content-type: text/plain
echo
GLOBIGNORE="wp-config.php"
echo removing wordpress subdirectories and files specified ...
echo
echo removing subdirectory wp-admin ...
rm -r wp-admin
echo ... done
echo
echo removing subdirectory wp-content ...
rm -r wp-content
echo ... done
echo
echo removing subdirectory wp-includes ...
rm -r wp-includes
echo ... done
echo
echo removing xmlrpc.php, index.php and wp-\*.php files ...
rm {xmlrpc,index,wp-*}.php
echo ... done
echo
echo removing readme.html and license.txt ...
rm readme.html license.txt
echo ... done
echo
echo ... task complete
exit 0[/code]
That needs to go into the wordpress directory, set permissions to 700 and run in browser.
Removal of WordPress also needs associated tables removing from MySQL.
--------------
For installing WordPress I upload the ZIP file and use the following extractwp.cgi and setwpperms.cgi scripts to unzip and set file permissions.
[code=extractwp.cgi]
#!/bin/bash
echo -e -n "Content-type: text/html\n\n"
archive=`find . -maxdepth 1 -name 'wordpress-*.zip' -print | \
sed -r 's/^.*wordpress-([0-9]+)\.([0-9]+)\.([0-9]+)\.zip$/\1 \2 \3 &/' | \
sort -n -r -k 1,1 -k 2,2 -k 3,3 | awk '{ print $4; exit }'`
if [ -z "$archive" ] ; then
echo "Sorry, can't find any wordpress-*.zip archives in this directory"
exit 1
fi
echo "Extracting archive $archive …<br><pre>"
# test archive structure first, unzip if OK, move to cwd, remove the empty wordpress directory
unzip -tqq "$archive" && unzip -qa "$archive" && mv ./wordpress/* . && rmdir ./wordpress
errorstatus=$?
echo "</pre>"
if [ "$errorstatus" -ne 0 ] ; then
echo "Extraction not successful (return status $errorstatus)"
elif [ ! -x ./setwpperms.cgi ] ; then
echo "Extraction successful but setwpperms.cgi not found or not executable"
else
echo "Extraction successful, setting permissions …<br>"
source ./setwpperms.cgi noheader
fi[/code]
[code=setwpperms.cgi]
#!/bin/bash
if [ "$1" != "noheader" ] ; then echo -e "Content-type: text/html\n\n" ; fi
function makeadir ()
{ if [ ! -e "$1" ] ; then mkdir -m 750 "$1" ; fi }
find . -name wp-content -prune -print | while read wpcdir ; do makeadir "$wpcdir/uploads" ; done
find . -type d ! \( -perm 1710 -o -regextype posix-extended -regex '.+/uploads($|/.*)' \) -print0 | xargs -0 chmod 710
find . -type d -regextype posix-extended -regex '.+/uploads($|/.*)' -print0 | xargs -0 chmod 750
find . -type f -regextype posix-extended -regex '.*\.(php|pl|cgi)$' -print0 | xargs -0 chmod 700
echo "<table border='1' cellpadding='2' cellspacing='1'>"
echo "<tr><th>Type</th><th>Name</th><th>User, Group</th><th>Permissions</th></tr>"
find . -type d -printf '<tr><td>Folder</td><td>%p</td><td>%u, %g</td><td>%M</td></tr>\n'
find . -type f -printf '<tr><td>File</td><td>%p</td><td>%u, %g</td><td>%M</td></tr>\n'
echo "</table>"[/code]
To use these create your own wordpress subdirectory (which needn't be called "wordpress"), and upload extractwp.cgi and setwpperms.cgi to it. Set the wordpress sub directory permissions to 710, and these cgi script permissions to 700. Upload the wordpress ZIP file to this directory (permissions staying at 640), filename including version number as downloaded from the WordPress website. More than one wordpress ZIP file can be in the directory, the script uses the highest numbered version. The setwpperms.cgi script is essentially that written by Gabe with additions to create a wp-content/uploads sub-directory with permissions 750 (correct for uploaded content).
Run extractwp.cgi in your browser to extract files and set permissions. After that run the WordPress install script as normal.
After an automated WordPress version (or plugin) update running setwpperms.cgi in a separate browser tab before returning to the dashboard will reset permissions of updated files to the correct ones.
David
David
