lelion
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Your Upgrade MethodI follow the instructions, too. I have only 3-4 plugins (incl. Akismet). If one of them will hapen to be incompatible with a newer version of WP, I’ll simply rename the dir /plugins/ to something else and then will try to enable them one by one:)
(Plus, with the amount of spam I get lately, I don’t think it’s a good idea to disable Akismet even for 5 mins;-)
Apart from the plugins, I always follow the basic principles when upgrading WP: backup files, backup database, delete old files, put new ones, run upgrade.php, that’s all:)
Cheers:)
Forum: Fixing WordPress
In reply to: Your Upgrade MethodI use not a lot of plugins, so I do not disable them lately… Just backup of MySQL databse, backups of the WP files, delete old ones, copy new ones, run upgrade.php:)
Cheers:)
Forum: Fixing WordPress
In reply to: permalinks appends ‘index.php’ to urls after server moveI can’t say why index.php is now appended to the URLs…
Can you check what’s in your .htaccess file, maybe the file changed, and this is the reason for the new URLs?…
Someone with more knowldge on permalinks might help, I hope…
Forum: Fixing WordPress
In reply to: Your Upgrade MethodWhen doing SSH, I feel like I have more control and know every step what it does:) Plus I do the manual backups before running the upgrade (copy files, backup database). I could make a batch script, of course (all SSH commands saved in a text file, and then run it… but then, where would be the fun of it… the manual upgrade?;-)
Forum: Fixing WordPress
In reply to: Your Upgrade MethodWell, while waiting for my soon-to-be tutorial, I can give you just some ‘directions’ 😉
You need PuTTY – get it here.
Launch it, use data provided by your hosting to connect via SSH:
Enter the host name (or IP address), OPEN session, you’ll see a black screen, then type your username to connect to your account, then type password. That’s it:)
Now type ‘cd’ to see list of directories. Type ‘cd name-of-dir’ to enter a certain dir. Type ‘cd ..’ to go level up. Type just ‘cd’ to go to the root of your account:)
Only other two commands I use are ‘cp’ and ‘rm’ to backup and delete files for my WP upgrades.
There are lots of tutorials on how to use SSH in Unix, though. Just search! 🙂
There is also very good documentation at wordpress.org, as to how you could perform upgrade using SSH. Check it out!
Be careful, you can delete everything in a second on your server account using “rm -rf”, so practice first (in a test dir on the server for example) and learn basic syntax of SSH commands – copy, delete, move from dir to dir, etc. 🙂
PS There’s also Midnight Commander, you can launch it by typing ‘mc’, it’s like Norton Commander in DOS, via MC you do everything and you do not need to know the commands by memory 😉
Forum: Fixing WordPress
In reply to: WP2.2 by default doesn’t establish proper UTF-8 connection to the dbDid you try wp-config.php?
Before I needed to edit wp-db.php to add SET NAMES and COLLATION there (UTF-8). I needed that to display correctly both in the blog and in the MySQL database cyrillic characters. Now I can do it via the wp-config.php file, which is a major relief:)
Worst case: You can edit manually the wp-settings.php file?…
Hope this helps:)
Forum: Fixing WordPress
In reply to: Strange Characters — —The new settings in the wp-config.php file (SET NAMES and COLLATION) are for those who had used an old trick in wp-db.php to make WordPress “talk” with the MySQL database in UTF-8, in case the server default is different (latin-1, for example).
If you had a blog and everything worked OK in it, then you DO NOT need to add ‘SET NAMES’ and ‘COLLATION’ in the wp-config.php file! You need to do this only if you used a modified wp-db.php file and want to stop ‘hacking’ this file in order to make the encoding/collation OK for the database:) Now you simply add this to the wp-config.php – and life is easier for us:)
Forum: Fixing WordPress
In reply to: Your Upgrade MethodI am not SSH savvy, too… 🙂
You basically need to know three commands:
cd (change directory, to move between remote dirs)
cp -r (copy)
rm -rf (delete)That’s all 🙂
“cp” is used to backup your WordPress files before starting an upgrade; “rm” is used to delete old WP files; “cd” you use to move between different folders…
To download the new copy of WordPress, you use “wget” and then “tar -xzvf” to extract files:)
I’d like to write a short tutorial on that, maybe these days:)
The good thing is that when using SSH, things are much faster – you do not download files locally, everything is done on the server, so no delays:)
And SSH looks a bit like good ol’ DOS 😉
Forum: Fixing WordPress
In reply to: Prevent indexing of feed pages?Thx! I’ll implement this tomorrow, then, and will check what will happen…
PS Going to read now… SERPS, of course:)
Forum: Fixing WordPress
In reply to: image problem in dashboard when i delete images via FTPSure, just joking:) Your explanation is much better, and more exact than mine:)
Forum: Fixing WordPress
In reply to: 2 ‘minor’ issues- Google Analyticator & Image UploadsYes, you can disable and not count the hits from yourself via Google Analytics control panel:)
It’s hidden somewhere in the options, just look deep (and use Google help on that) – you can simply add some IP address which won’t be counted (your home IP, for example)!
Hope this helps:)
Forum: Fixing WordPress
In reply to: image problem in dashboard when i delete images via FTPLook, I don’t mean to be rude, but should we all repeat ourselves? 😉
You UPLOADED the images using WORDPRESS! Everything you do using WordPress (write posts, add categories, upload images, etc.) is stored in the WordPress DATABASE.
If you upload images using WordPress then WordPress WRITES the name of the images and their locations to the DATABASE. It is OBVIOUS. Now, if you delete them via WordPress panel, it removes the data about the images (and deletes the images from the server, too); if you delete them OUTSIDE of WordPress (via FTP) and then login into WordPress, of course WP will have still intact the info about the images in its database and will show the data about the images in the admin panel!
But you have deleted them! Outside of it! So they are not THERE! But WP cannot KNOW that they are NOT there, as you didn’t remove them using WordPress, right?
Errr… Hope you get the picture better:)
Cheers, have a glass of beer, too:) (and read more)
Forum: Fixing WordPress
In reply to: Prevent indexing of feed pages?Thx, great, nice tip!
How can you say it’ll work?
I have robots.txt and may implement it today or tomorrow…
(Would be nice also for others to know…)
If you’re sure it’ll work, we may mark this example as “resolved” and help others as well, right? 🙂
Forum: Fixing WordPress
In reply to: Prevent indexing of feed pages?Yes, I think so, too. The feed example I posted contain SAME text as the posts, so why google should index it?
“” I can’t see how to solve this solely with robots.txt “”
I can’t, too, but would like too… Maybe a rule should be created, which will filter everything ending with “/feed”?
Anyone any ideas on that? 🙂
Forum: Fixing WordPress
In reply to: Your Upgrade Method(my method before):
(1) backup wp files from the server (FTP),
(2) backup MySQL database,
(3) delete all files, except for wp-content dir, .htaccess, wp-config.php, and any other files I may have modified,
(4) upload via FTP new wordpress files and folders,
(5) run upgrade.php script,
(6) check if the blog is OK, done:)(if you use a lot of plugins, a good idea might be first to disable them before upgrade and then re-enable them after that)
***
(my method now):
(1) backup wp files from the server (copy via SSH),
(2) backup MySQL database (wp-db-backup plugin),
(3) delete all files, except for wp-content dir, .htaccess, wp-config.php, and any other files I may have modified (delete via SSH),
(4) download latest WP version directly on server (via SSH) and copy them to my wordpress install dir,
(5) run upgrade.php script,
(6) check if all is OK, done:)My new method is faster, and more secure.
Basically, that’s it…
My $ 0.02, 🙂
PS I do not post a temp file, saying ‘We upgrade, please wait’ 😉 — upgrade via SSH can take just less than a minute, so why bother… Delete old files, copy new ones, run upgrade.php, that’s all:)