Bump…..Still hoping someone can help with this please…..
The style.css file in the custom theme – especially the comment block at the top of the file – may have become corrupted in the original version. I’ve known this cause a theme to “fail” before now.
Thanks esmi – I checked that, but I’m actually using the very same CSS stylesheet (styles.css) – I’m just uploading it to both the /default folder (currently in use as the chosen theme) and also to the custom folder to keep that folder current with the hopes that this problem can get fixed and I can go back to using it…..
So since it (and all the other theme files) works in one folder I have eliminated any file corruption as a possible source of the problem…
My best guess is something else in the WP core files may have gotten corrupted? But I am not sure what admin file controls the appearance of available Themes under the Appearance preference pane….
There’s a mixture of file & functions involved. The easiest option would be to re-upload a fresh copy of the complete wp-includes and wp-admin folders.
Well, now I’m worse off – I re-uploaded a fresh copy of both the wp-admin and wp-includes folders, and now I’m getting two fatal errors from wp-includes/load.php on line 337 – have searched for a fix for that but none of the offered solutions are working….
So now the site is not coming up at all, just the error, and I can’t get into the backend admin……aaarrrrgh….
I just tried a complete, fresh reinstall of WP (was at 3.0.1 before, now at 3/0/4)…..
The error message is gone, but I get a completely blank page for both front end (site) and backend (admin)……
Does anyone have any suggestions, please?
Hi Esmi
Yes – I did a manual upgrade – but I was still getting a fatal error:
Call to undefined function: wp_embed_register_handler() in …/wp-includes/default-embeds.php on line 33
I have it back working (just now) but it was a real struggle – here’s what I wound up having to do – which meant modifying a couple of core files and the functions.php in the WP default Theme, TwentyTen (which for the record I hate)….
I had to comment out the lines in both /wp-includes/default-embeds.php (line 33) and /wp-includes/load.php (line 337) – that got rid of the fatal errors but still left me with a blank white screen – so I went into my phpMyAdmin and deactivated all the active plugins per instructions I found in the Codex….
Then I got a fatal error in the functions.php file of the /themes/twentyten theme so I commented out the offending line there (line 16 – had to do with set_post_thumbnail).
THEN I was able to login and go to Appearance to activate a different theme (my own) and VOILA my original custom theme showed up and let me activate it…..to be on the safe side, I am also keeping a duplicate set of all current theme files in a folder called /themes/default, and I modified the /wp-includes/default-constants.php file to specify “default” as the default theme, not twentyten…..
TOTAL PITA but now it’s back working, at least for now – the changes I had to make to some core files worries me…..and it also greatly bothers me that WP only comes with that hideous TwentyTen theme which apparently has a flaw in the functions.php…..
I don’t think I’ll upgrade for a while…
Once I was able to deactivate all the plugins via phpMyAdmin, then I believe WP was trying to load normally, but since (at that point) it was set to use TwentyTen as the default theme (since I did a fresh install and twentyten is specified as the default them in the default-constants.php file) it wouldn’t load because it was getting a fatal error in the /twentyten/functions.php file
The error was something about a call to an undefined function on line 16, the one dealing with show_post_thumbnail (sorry I can be more clear, I didn’t copy that one to save)……but since I don’t use WP’s thumbnail function, I just commented out that line.
Once I commented out that line WP loaded normally (although it wasn’t using my theme) but I was able to see the site and get logged in, at which point I went to Appearance and chose the correct theme.
So it seems to me that if a fresh install of WP 3.0.4 can’t load TwentyTen without a fatal error, it stands to reason that there is still a conflict somewhere.
There are no errors in Twenty Ten. I can only guess that your copy was corrupted or customised.
It was from a fresh download and install……and I did not customize it, but it’s possible it was corrupted…..although I don’t know how…..
In any case I’m grateful for your help as always……
