mariacharmer

Nevermind, I figured it out.
This was the error I was getting: Fatal error: Cannot redeclare class Wickett_Twitter_Widget in /home/content/N/a/i/Naica2005/html/flabmag/wp-content/plugins/jetpack/modules/widgets/twitter-widget.php on line 256

I just went onto my server and deleted the .php file.
It’s part of Jetpack which strikes me as odd considering the jetpack is something wordpress offers yet somehow their recent update was conflicting with it?
Strange.

Here is my website: flabmag.com

Actually, I am still have an issue with widgets I want to appear only in the ‘about’ page sidebar and not on the main blog page. I figure out how to get widgets I want to appear only on the main blog page (login, categories, links) but how do I get the reverse affect?

I tried this code: !is_page(‘blog’)
Because I want it ‘everywhere’ (about page) EXCEPT the BLOG PAGE.
It didn’t work….

I’m using the new Photocrati Supertheme. It provides a footer widget area but that merely let’s you place a widget configured the way they have it – vertically aligned – in the footer of the blog page. I want the login meta to propagate on every page…essentially in the footer of every page. That’s why I assume it would be the footer.php because I added our company info and links to it just fine but had to use that file. So it must be that file.

Mainly I want the login link in the footer because I hate having to go to the blog page to click site admin to go back into the dashboard to add content or change something. If it were in the footer on every page would be very convenient for myself and the other admin.

My question is: What code do I use to get the Login and register to comment links that are on blog page to also propagate in the footer?

Yes, I saw this:
!is_page(‘about’) — everywhere EXCEPT this specific WP ‘page’

I figured it out. Actually using the !is-home tag worked!
Yay.

Huh…I replaced this code snippet (I assume you meant this part):
/images/custom-login-logo.gif) !important; }</style>’; }
with this:

/images/MBR_banner.png) !important; }</style>’; }

It didn’t replace the default WP logo on the login page…Did I do it incorrectly?

So I tried the auto upgrade through dashboard for this site. I got this message:
The update cannot be installed because WordPress 3.0.1 requires MySQL version 4.1.2 or higher. You are running version 4.0.30.

Installation Failed

I called Godaddy. Their suggestion was to create a new database with their easy installer and then restore the old database to that new database. I told her how you guys here said that would break the database. She said: “Well you will have to do some reconfiguring…” LOL, whatever that means…so am I stuck? Is it possible to create the new database and restore the old one based on php4.0.30? I guess I’d lose images, links, audio etc and maybe my theme wouldn’t work but If I have all the text that would satisfy me because I have all the visual/audio content in folders on my server and back up to disc.

Any ideas? I known you say not to listen to them but what’s the alternative?

Mmm they told me about that. I have a few other WP websites in subdomains within the main root folder. It’s that first WP blog that I just upgraded that is based on php4. All the others are under php5.

How do I update that one site? Is it creating a new php.ini file to place in the root folder for that particular blog? Will that help?

Well, it’s done. Sort of. This old database was based off PHP4. I couldn’t upgrade to WP 3 because it require PHP5.

Godaddy would not help me upgrade the database to 5. Said it would mess up the content because it was based off 4? I’m not sure that’s correct. But I guess this is better than nothing.

Thanks for all your help!

Well reuploading all the files worked. Interestingly when I logged into the dashboard it now gives me the “A new version of WordPress is available! Please update now.” prompt. This is WP 2.3.
Should I go ahead and auto update or keep going through this process?

On the WP Codex page re: Upgrades it suggested doing this:

NOTE: If you did not delete the wp-content folder, you will need to overwrite some files during the upload.

The wp-content folder holds your WordPress Themes and Plugins. These should remain. Upload everything else first, then upload only those WordPress files that are new or changed to your new wp-content folder. Overwrite any old versions of default plugins with the new ones.

The WordPress default theme has changed so you will want to upload the wp-content/themes/default folder. If you have custom changes to the default theme, those changes will need to be reviewed and installed after the upgrade.

I did so for that first upgrade to 2.1 and it worked fine. So I did it as well for version 2.3. However the theme we were using, really old Nosebleed theme, was not the default anyway…and all I did was upgrade the Askimet and hello.php plugins.

Everything else I did exactly as I did the first time.
Hmmm? Maybe delete the files again and start fresh and reimport 2.3 files?

Well…I spoke too soon.
I just did the upgrade to version 2.3 (going from 2.1 to 2.3 as was suggested). It says i am upgraded but now the blog is not showing up:
https://www.thenaica.org/wordpress

I didn’t delete any of the pertinent files only replacing wp-admin, wp-includes and the ancillary php files EXCEPT config.php

hmmm now what happened?

Relief! Just did upgrade for 2.1 and all the content is there. So relieved! Thanks again for my unbearably dumb questions.
But I’ve learned all sorts of new things about WP and databases. So that’s good.

THANK YOU!
I am sorry for being a pain in the ass. LOL.
I really appreciate all of your help.

https://thenaica.org/wordpress/wp-admin/upgrade.php

Regarding above link: I clicked on it. Told me it was only one step. I clicked the upgrade tab for it to do the one step. Told me I was done. Logged into admin for blog…it’s still version 2.0.5. Nothing has changed. Clearly I have to upgrade the files on my server because this “one step” isn’t doing anything.

What’s the difference between upgrading old files and doing installs anyway. Seems logical that you would have to overwrite old php files associated with older versions of the blog, no?