mikejandreau

I upgraded 17 blogs from 2.5.1 to 2.6 issue free. Not a single problem on any of them.

I noticed this happened, but only on one of my blogs.

The others all remember me correctly, with or without the SSL support.

Not a big deal, since Firefox does all the remembering for me. Just gotta click the login button.

I’d suggest making your .htaccess writable by the server (777), then re-set your permalink settings.

I upgraded all 17 sites I manage that use WordPress, to 2.6 this morning, without issue on any one of them.

The new features are awesome. I love the “nagging – update your plugins!” number. Pretty cool stuff.

To start, I’m not sure why there’s any difference between a .org and a .com, from a functional standpoint, but that aside:

If you have phpMyAdmin available via your .org hosting, you can get the content back easily. You’d just need to login to phpMyAdmin (available through most webhosts), and do an “export” on the wp_posts table.

Once that’s done (save it to your local PC), go into phpMyAdmin for your .com host, and import the saved .sql file.

You may, however, run into an instance where you can’t import it, because of duplicate key entries, which happens a lot in this sort of thing.

The way around *that* is to change the key values in the .sql file, which would trick MySQL into not duplicating the unique key field.

Your host for the .com domain should be able to help you get this all set, pretty easily.

Glad I could help.

The “old” server you were on used localhost. The new server doesn’t. That’s so, in case, we need to move you to a new MySQL server, we don’t have to update your connection strings. We use the CNAME configuration to simple change where your *.startlogicmysql.com points.

You’d need to figure out, first, which database your WordPress is installed in.

Looking at your account (I work for StartLogic’s parent company), you’ve got two Databases that could be the “right one”.

djmedley_wp_1
djmedley_wp_2

Your DB_HOST would be: djmedley.startlogicmysql.com
Your database and username for the database can be gotten here: https://members.startlogic.com/webControl/mysql/manage.bml

Once you fix your config file, you should be all set.

Delete what you’ve installed, and install via InstallCentral (available on IPOWER)

Then, once installed, and working, do the upgrade from there.

It may be something weird between WordPress and the ISS Windows server you’re on.

Or, delete the whole thing, and start over again. Not knowing the password isn’t a big deal, you can just request it again via the admin login page. I’d suggest starting over though.

I’d do it for you, since I happen work for IPW’s parent company, but don’t want to just arbitarily nuke your database.

They managed to hit files that weren’t 775 or 777, mostly every header, footer, and index file in every directory in every domain.

My host has been less than responsive (ignoring chats, and hanging up on me when I call)

Anyone have any ideas?

You probably want something similar to wp-navi plugin: https://www.ads-software.com/extend/plugins/wp-pagenavi/

That’s probably because you haven’t told it where to link to.

You’d want to use the “Create page” option in the gallery manager, to create a page for your site to display the actual images from the gallery on.

It should be made clear, however, that WordPress will only create the .htaccess file if the directory that houses WordPress is writable.

Having your entire directory writable isn’t the best idea. It’s easier to just upload a blank file called .htaccess, and make just it writable.

Exactly what was I looking for. Thanks!

You want ALinks; here

I use the “Redirection” plugin: https://urbangiraffe.com/plugins/redirection/

It sort of automatically creates 301s for any pages you want to redirect, and keeps a log of the number of times it’s redirected. Works really well.

Just keep in mind that the redirect won’t work until you delete the old page. Took me a bit to figure that out.

Sorry, I forgot to come back and post.
It looks like the DNS entry for your MySQL hostname got duplicated in our database during the move to the new datacenter.

I took care of it, and all three blogs seem to be okay now.

I’ll respond to your support ticket too, so you can e-mail me back directly, in case there’s still issues.