lelion
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: WP 2.2- Stumped! No options in AdminPS You might wanna know this as well:
DreamHost keeps special backups (‘snapshots’ of your files), in the main dir of your acount. It’s called .snapshot, more info: http://eightface.com/2005/02/dreamhost-hidden-feature/
Now, this is about your files. There you might find intact copy of your WordPress before the upgrade! Remains only to know where the MySQL backup they made before the one-click-install of WP 2.2! (ask them)
Having the intact version of WP files AND the MySQL database, can produce miracles and restore the WordPress you had ‘as it was’, which would be very nice:)
Hope this helps, keep us updated!
—
PPS You website http://www.trailofants.com/ now works, as I see, with default theme installed?… 🙂
Forum: Fixing WordPress
In reply to: WP 2.2- Stumped! No options in AdminWell…
I do not trust anything which starts with ‘One-click-something’ 😉
Not that it won’t work, no. It will, most of the times. But the point is that when dealing with automatic backups / upgrades / etc., you do not have any control on what exactly happens, and this is important. *If* something wrong happens, you can (having full control) make the necessary steps to fix thing; if all is automatic, then you do not know what happens…
I use DreamHost and I am pretty happy (for now) with their service. I have 2 WP blogs installed… err, no, actually, 4, but I did manual install, and I try to make complete backups of MySQL and files before any upgrade.
OK, for now, I’d suggest to ask DH support — ask them if they have a ‘snapshot’ of your system, say, 3 days old (I guess, trouble began AFTER that, right?) If they have, ask them to restore it. It should restore things to back as they were before you tried the upgrade to 2.2!
It should restore files & MySQL.
If this doesn’t help, then you may try to ask them if they have backups of: MySQL database 3 days old; and files for your wordpress, 3 days old. You may want to try a delete of current files + mysql, and then restore the WP from these 3 days backups.
How does this sound to you?
Forum: Fixing WordPress
In reply to: add padding to images in editor…i use both image float left and right so modifying css sheet is not acceptable…
Why it is not acceptable? Just add the styles to the admin .CSS file, and what is floated letf and right in your theme, will be floated left and right in the admin area as well:)
Shoulddn’t be so hard; if you need specific advice or want to show us an example, whould be nice:)
Cheers!
Forum: Fixing WordPress
In reply to: Uploads directory.Anyone, any advice on that…? Please? 🙂
Forum: Fixing WordPress
In reply to: Strange Characters — —This is a problem with incorrect encoding… WordPad is not the best choice when restoring databases 🙁
Better use Dreamweaver, which supports various encodings, and copy -> paste from it. Or any other editor, which supports UTF-8, and many other encodings… I can’t say if there’s a way to automatically fix the wrong characters in the database.. If you keep the original MySQL backups/files, better open them with the correct editor and make the copy paste again:)
Forum: Fixing WordPress
In reply to: image problem in dashboard when i delete images via FTPWP thinks they are THERE because you didn’t delete them via WORDPRESS but outside of it, via ftp! If you put them back via FTP with same names/locations, you’ll see them in WordPress and can delete them safely from there; or you can delete the ‘placeholders’ of the deleted images from WP; it doesn’t matter 🙂 Just opt for one of these two options and mark the thread as RESOLVED 😉
Cheers! 🙂
PS WP doesn’t have ‘cache’ for the images; the images names/places are in the database, because you uploaded them via WP; but you didn’t delete them via same way that’s the reason WP still ‘thinks’ they are there! 🙂
Forum: Fixing WordPress
In reply to: WP 2.2- Stumped! No options in AdminIf you reverted back to 2.1.3, and THEN trouble began it means you didn’t revert back correctly, or so I believe. You must have intact: copy of MySQL database backup, at the moment before you made the upgrade; and copy of all of your files at the same moment. You delete the new files, copy old ones; then you restore the database; and after that, your website should be exactly as it was before moving to 2.2; if it’s not then there’s a wrong step somewhere, or so I believe… Maybe someone with more experience can help with this… 🙂
Forum: Fixing WordPress
In reply to: Uploads directory.Anyone, some help on that, or… it’s hardcoded and now in WP 2.1.x and 2.2.x and above, we can’t anymore declare an directory for uploads which is ABOVE the wordpress dir?
Is my only chance to file a ticket in the trac, or there’s some workaround?…
I am sure that a lot of people use upload directories which are outside the WP install, so what do we do…?
In 2.0.5
../(in options -> misc -> uploading)
meant:“Go one dir higher” so
../my-uploads/correctly stored uploads in: http://www.server.com/my-uploads/ …Now, since 2.1.x and higher,
../my-uploads/still uploads everything in the correct dir on the server, but produces invalid URLs like:
www.server.com/../my-uploads/…it’s even strange that they work…Thx for any advice on that:)
Forum: Fixing WordPress
In reply to: the word ‘Array’ is appearing everywhere in the dashboardActually, I am on DreamHost and I have PHP 5.x/MySQL 5.x so our versions are different, but the bug with the ‘array’ I saw on your blog really puzzles me… 🙂
Anyone any help on that?…
WP 2.2 is supposed to run fine on PHP 4.3.x &
MYSQL 4.0.x, right? So why in this case there’s the word ‘array’ all over the place and the blog is not working?…Forum: Fixing WordPress
In reply to: Uploads directory.I’d like the answer to that question, too.
I used in WP 2.05:
../directory_for_uploads…after upgrading to WP 2.1x and 2.2x, this doesn’t work anymore, so now if I make the option
../directory_for_uploads, then what I see in the urls becomes something ugly like:http://www.mydomain.com/../directory_for_uploadsWhy did the model change after 2.1?
How do we specify now a HIGHER-level dir for uploads?
I tried everything, absolute paths starting with http://www.mydomain.com, server paths like “/home/myusername/”, I tried everything, nothing works, I can’t simply make the path to be one level higher than the wordpress dir :(((
Reason I’d like this to work is that I run 2 blogs on one domain, and I want all uploads to be in the main dir, like:
http://www.mydomain.com/wordpress-uploads/
and not in
http://www.mydomain.com/blog1/wp-uploads/
and http://www.mydomain.com/blog2/wp-uploads/…or something of the sort…
Thx for any help!
PS I can hack the WP files, but it’ll mean for me more difficult upgrades all the time, so a better solution is what I search for 🙂
Otherwise… I guess, we’ll have to post a bug ticket somewhere?Forum: Fixing WordPress
In reply to: Prevent indexing of feed pages?Yes, I’d like to know the same… feeds are ok for rss readers, but for google, .php pages are ok 😉
Anyone? 🙂
Forum: Installing WordPress
In reply to: Upgrade from 2.0 to 2.1 got stuck –Good news 🙂
I’d make next time the upgrade manually, though 😉 I’d better trust myself following a step by step process of backup + upgrade than a machine script somewhere doing so 😉
Forum: Fixing WordPress
In reply to: Just a side question about how WP assigns IDs…Thank you for the replies, fellas 🙂
I am much calmer now 😉
As to the people who have 1-2-3-4-5-6-7 etc. sequences, I’ve seen them running latest WordPress, so I guess, it’s the other reason – they never uploaded a picture using the built-in upload manager :)))
Thanks again! 🙂
Forum: Fixing WordPress
In reply to: Missing in admin panelyou’re welcome 🙂
Forum: Fixing WordPress
In reply to: Missing in admin panelYes it is OK just to re-upload some files, if you upgraded, nothing will be changed after that:) Disabling plugins is also a good idea – check if it works:)