Patricia

I’m having the same issue. I checked the database – I cannot find any information added that connects the uploaded images to the categories. So, nothing shows in admin category area. No image in category overview; nothing when you click edit.

The images are ulpoaded however (wp-content/plaatjes/terms-images/category).

WP 3.1.3
PHP 5.3.2
MySQL 5.0.7

Hope you can help!

I had the same problem. It’s because the previous/next links are based on the publish date and time of the post. This plugin posts all posts from a feed at the same date/time and now WP is confused and will only show one of them in the single posts navigation.

The work-around is to use the drip feature and set it to publish 1 post every 1 minute. That way you still get your posts published relatively fast and you no longer have the navigation issue.

Can you access your website administration? I don’t mean your WP admin, but the back-end of your domain. Your hosting company should have given you the details when you opened an account.

If you don’t have that info any more, contact your host about it.

Once you can access your website admin, you want to find out how you can edit your database. Since there are many different server programs, it’s hard to be specific. But a lot of them have a tool called phpMyAdmin. (In case you’ve got cpanel: there is a phpMyAdmin icon on the main page; in older version you have to click the MySQL databases icon first and then scroll to the bottom of the page that opens to find the link.)

Access your database through phpMyAdmin. Select the WP database from the leftside dropdown menu. You should see a table with at least 15 rows; the bottom one is wp_users (there might be something different in front, but it definitely ends on users).

In the next column you’ll see an icon looking like a little menu. This is the browse button. Click it and it will open all the data inside the users table.

The first row will contain the administrator data. To edit this, click on the pencil icon. You’ll see your login name, email address and a line of hashed code which is your password. You can change these and then click the ‘Go’ button underneath.

If you want to change your password here, just delete the hashed stuff. Type in the password you want (no dictionary words or combinations of your name, initials, birthdate etc!). Then select ‘MD5’ from the dropdown menu that’s next to the password field on the left. This will encrypt your password again after saving it.

Once you’ve done this, you should be able to access your WP admin again.

If you cannot find any tool to access your database, ask your host about this. They should be able to help you out.

Best of success!
Patricia

I got the same problem – in my case it wasn’t weboptimizer (not using that one) but Cimy Swift SMTP causing the 500 internal server error. After deactivating posting comments was working fine again.

This is on a WP 2.8.4 installation by the way. Pre 2.8 I haven’t noticed this plugin to cause problems.

Hmmm… unfortunately it isn’t a perfect solution. It doesn’t really work well when a post has several child categories which belong to different parent categories. Then there’s only 1 parent category displayed – looks like the last one found.

Too bad I’m not very good with PHP. If anyone knows how to improve this code snippet, I would be most grateful!

// Adds category classes for each category parent on single posts
      if ( $category = get_the_category() ) {
              $p_cats = get_category($category[0]->category_parent);
			  the_post();
			  if ($p_cats) {
			  $c[] = 'p-category-' . $p_cats->slug;
			  }
      }

It seems abandoned. I wrote them about a year ago to say I’d be happy to purchase the PRO version, but no response and the PRO page on their site never got completed. So I doubt they are continuing this one.

I cannot get it to work with 2.7 either. Bummer, this is the 2nd FAQ plugin I was content with to ‘disappear’. Neither of them being open source so nobody can continue development it seems…

Had the same problem. Clearing the browser cache fixed it for me.