odiolitos
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminWell, from what I gather (I’m an absolute noob!), the wp-content directory is where your posts are, so you should be really careful with that.
If possible, download the whole wp-content as it is right now, and change the files in the server bit by bit. Maybe index.php would be my first choice, but again, I don’t know that much…
Regarding Filezilla, it’s quite straightforward: you enter your server data (name, port, user name and password), and treat it like a regular file navigator where the left pane shows your computer and the right one shows the server. Drag and drop works, too, so changing files is a breeze.
Good luck!
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminAaand… The “top bar” just came up unexpected, with the site’s name and a couple other tools, so I consider this thing solved.
There’s still some quirks to get straight (posts appear twice, etc.), but that’s not the subject…
Thanks a million for your help.
Summary:
If this has happened to you, try reuploading a fresh install of WordPress (excluding /wp-content), and pay special attention to 0-size files.Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminOk, I had obviously left some file or other out… I did an automatic reinstall from the “update” section, and the site’s visible again!
The site’s name is still not in the dashboard, but at least the it’s up again. Yay!
I’ll keep this open until I make sure everything’s running fine, and then I’ll mark it as solved, if that’s ok.
Again, thanks a lot for pointing me in the right direction!!
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_admin@esmi: That’s another weird thing: the site’s name is missing, too (so I can’t see the dropdown)
@kmessinger: Yup, that was something I thought, but it seems to be ok…
Thanks!
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminNo prob, esmi… Your help’s always welcome!
I switched to Twenty Eleven (which had a different size loop.php), but that still didn’t work. I reckon some other silly little file’s missing or not quite right in /wp-content… I’ll keep looking.
Another strange thing I noticed, and this may be a clue to someone, is that the “view blog” button is missing in the dashboard.
Again, thanks a lot!
@sirps: My guess is a faulty wordpress download, just like me. Check all the files are the proper size with Filezilla (or any other FTP client), and maybe you can get things right… I really don’t think it’s WordPress, but some server/connection glitch while downloading the upgrade. Good luck!
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminOk, now I’ve got a different problem which may or may not be wordpress- related: I’ve got my control panel and everything, but when going to the site (Odiolitos.com), nothing but a blank page comes up. Any ideas?
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminYay! I think I got it!
Seems like some of the files had uploaded as 0 size (namely, those in wp-includes and wp-includes/pomo)
What I get now is a message urging me to update my database, which makes total sense.
And… I got my site back!!!!
I’ll just check that everything’s ok.
Yet again, thanks a million, esmi!!
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminAfter overwriting all the 0-size files in wp-includes, I get a different message when trying to login through wp-admin:
Fatal error: Class ‘NOOP_Translations’ not found in /home/d468554/public_html/wp-includes/l10n.php on line 486Maybe I’m making some advances. Maybe I’m just messing the whole thing up that bit more. I’ll keep trying.
Oh, and sorry if this seems like my diary: I just want to be able to retrace my steps later on.
Thanks for reading!
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminI also tried opening wp-settings.php on my browser, and got a different message:
Warning: require(ABSPATHwp-includes/load.php) [function.require]: failed to open stream: No such file or directory in /home/d468554/public_html/wp-settings.php on line 21 Fatal error: require() [function.require]: Failed opening required 'ABSPATHwp-includes/load.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/d468554/public_html/wp-settings.php on line 21
Not being very savvy, I gathered the idea was to see if wp-includes/load.php was there. It is, but is empty when viewing it through FTP. I’ve also noticed many files showed a size of 0… Could this be the source of the problem?
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminMeh, no luck… Guess that would have been too easy! I’ll substitute them for the 3.3 files to go back to where we were before.
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminOk, so I’m trying now by uploading the 3.2.1 files (save for wp-content) and keeping my fingers crossed
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminSo it seems things are really bad, I guess…
Should I re-install wordpress and start from scratch? (which I’d have to find out how to do) What do you suggest?
Oh, and thanks yet again. You’re really nice. ??
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminSurely! It is… Is that good or bad?
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminYes… In fact, I did the whole thing again, just to make sure.
Forum: Fixing WordPress
In reply to: Updating to 3.3 broke site, can't access wp_adminOh bother… I still get the horrible:
Fatal error: Call to undefined function wp_initial_constants() in /home/d468554/public_html/wp-settings.php on line 26And nothing else when I go to /wp-admin
Oh, and thanks again.