• I am looking for some expert help, maybe some hand-holding too!

    I was getting 404 errors on posts this week, so tonight I tried to upgrade while keeping my customization. It didn’t work, mainly because I kept getting a “permission denied” message on my FTP.

    Recently I had to have my host restore my 1.5 files and perhaps they didn’t change the permissions for me.. not sure, really. But since I could not change files via FTP, I just went for the automatic (Fantastico) install they have … and my files did show up ok, but not *all* my customization.

    In trying to replace the old content I messed things up again and now get fatal error after fatal error. ??

    I did use the guide and found it very confusing, even contradictory, where keeping old content and swapping out new files is concerned. (Last time it was a breeze!)

    I could really use some expert help.

    jean

Viewing 9 replies - 1 through 9 (of 9 total)
  • As a “normal” non-computer geek person, I found the upgrade to 2.01 to have been very difficult and left me with all sorts of problems that I don’t have a clue as to how to resolve. I have a very simple, hardly changed kubrick theme with only a couple of additional plug-ins (and I removed them all, and they did not re-install well).

    All this to say, I could use some expert help as well and have absolutely no idea where to even begin to look for it.

    I know this is not helpful, but I am hoping that by chiming in, someone will notice.

    It’s hard to guess where to start when so many of your error conditions are outside of WordPress.

    You mentioned ftp problems and permissions issues. Before you get too far into saying WP screwed you up, I’d suggest you spend time with your host and make sure you can upload the current WP version without errors. Until that point, we have no clue what may or may not be there — and, more importantly, if it is all set to the proper permissions.

    I’d also leave the plugins out of the equation for a bit unless you’ve hardwired them into your theme.

    Thread Starter jrotem

    (@jrotem)

    I wasn’t being accusatory (gee!). I am just looking for help. I had a functioning blog (restored) until I tried to upgrade per the instructions. I am suspecting a database problem but was hoping someone at least could tell me where to go from here.

    My blog is getting now getting this error:

    Fatal error: Cannot redeclare user_can_create_post() (previously declared in /home/rotemd2/public_html/news/wordpress/wp-includes/functions-post.php:331) in /home/rotemd2/public_html/news/wordpress/wp-includes/capabilities.php on line 356

    Can anyone tell me what it might mean?

    I wasn’t being accusatory either (golly!) — I was actually suggesting a plan of attack.

    It was either the host restoring the files from WP 1.5 that really set things off or maybe fantastico (which can have issues even on a clean install) installing a new installation over an old one on the same database (I’m guessing the same DB was used for both).

    My suggestion, which is far from the ideal solution, would be to start over. I’m not sure if you have a database back-up or not or what your situation is, but maybe restoring 1.5 and then doing the proper upgrade to 2.0.1.

    The instructions are very explicit in that you have to deactivate ALL plug-ins and it also tells you that you can keep the wp-content folder intact. I hardly know the intricacies of WP’s database in 1.5 compared to 2, but I imagine it may be jumbled up somewhat. Hopefully your 1.5 DB is still intact, maybe fantastico used a different DB than the existing one?

    A very bad situation, but I hope it works out well for the both of you!

    Michael.

    Ok, I too had an issue with the upgrade from 2.00 to 2.01. I uploaded the update. Ran the wp-admin/upgrade, got the ok message saying if I got that message everything was ok. Well, now when I go browse the blog, I get “Sorry, no entries matched your post”. Willing to kind of start over, I tried a new post, and published it, and still get the same message. I had posted earlier today, as is evident by the calendar link, but can’t get any posts to show up. The url is https://www.redneckramblings.com .

    Thread Starter jrotem

    (@jrotem)

    Niziol,
    I did deactivate the plugins kept the wp-conent folder intact and tried following directions from 1.5 to 2.0.1 but along the way … ah well. I’ll try to get my host to restore it as it was, again.

    Also when I checked the guide by Podz (which was recommended in another thread) it said that overwriting the files will not be good enough and can cause problems but i didnt see that in the WP instruction. That was confusing because i had already overwritten files.

    i am sure that the mess with the denied permissions was a big part of why things didnt work out — I suspect it left me with a mix of incompatible files.

    I’ll have to get in touch with my host but then I’ll be back at 1.5 again and I’m more leary than ever to upgrade.

    Thread Starter jrotem

    (@jrotem)

    Yay! I took a chance and once more upgraded using the automatic (Fantastico) upgrade with my host.

    I replaced the sidebar file with my backup one and it’s restored — w00T! and same with footer. Only this did not work with the header, which is giving me a header-ache ?? So I need to look for info once again on how to go about replacing the header with my personal header.

    My individual post links still get an error, which started this whole saga, but at least the blog is more or less up ??

    jean

    Good to hear! I know for myself, my best learning experiences are figuring out how to fix whatever I screwed up! ??

    Podz’s guides are excellent I think, very good, learned from experience instructions. The permissions issues probably did set all of this off, if you have issues with files that you’ve uploaded like that again, talk to your host and see why the permissions might be acting wonky.

    Happy blogging,
    Michael.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Upgrade Made a mess — pls help’ is closed to new replies.