Update to 0.9 made all my links give 404 errors

Deleting the two options before the upgrade was the correct thing to do so that they get re-converted.

I agree at this point everything should be getting done from the dev site until we know we can get the options converted and registering properly. If push comes to shove, I have zero issue with manually converting the settings to what should work, with my own import testing to make sure it worked.

Hi Michael,
I just upgraded to 1.0.2 on my dev site and my taxonomies are still not associated with the custom post types the way they used to be in the past.

Should I do this manually or what?

Thanks.

Hi Michael,
Just remembered something that I wanted to tell you, may be it’s affecting my site.

When I first created my custom post types, I had the names starting in capital letter, and then at one time when I updated your plugin things went bad and I think I read that you changed all custom post types to begin in small letters, so I had to place the following code in my functions.php file for it to work again. And it’s still there now.

if(!get_option('custom_type_updated')){
global $wpdb;
$wpdb->query("UPDATE $wpdb->posts SET post_type = 'questions' WHERE post_type = 'Questions'");
update_option('custom_type_updated','true');
}

Is that code doing anything now?

Regards,
Mamdouh

Nothing that would be affecting what our plugin does.

Mamdouh, would you be willing to let me in and see things firsthand at this point? I’d really love to get this resolved for you, and being able to log in may facilitate that being done quicker.

No problems Michael, but I am currently working on my dev site that’s on my PC and not on the live site.

Do you mean you want to access the live site itself?

Thanks for your care.

It would have been for wherever the problem was presently existing, which sounds like it wouldn’t be accessible from where I am right now.

I had the same problem on the live site when I upgraded to 1.0.1 so I reverted back to 0.95 to fix it.

Hello, I updated the plugin to the latest version last night and all my custom post types went 404. I only realized this today (about 12hrs later) and reverting back to the older version (Version 0.8.5 in my case) fixed it for me, in case someone else has the same issue. I reverted without attempting to re-create the types with the latest plug-in.

Michael Beckwith, maybe I should use the “Get Code” option and paste those in the functions.php file, and de-activate the plug-in to avoid potential upgrade issues?

What do you think?

You can use the get code stuff if you wish, though that treats the plugin as just a code generator, but that’s also not necessarily a bad thing either. It would be preferable on my end to figure out what stumbling blocks you ran into though Hubert, so that I can determine if there’s more I need to do with where the plugin is at now.

elmalak

Is the missing association determined because the checkboxes are no longer present? or because the taxonomies are no longer listed alongside the post types in the admin menu? If it’s just missing checkboxes, then I suspect it’s associating and saving properly, it’s just not re-showing them as being checked, which I believe was part of a 1.0.2 change. I’d need to be able to see some parts of your settings to make sure it’s working as it should be at this point.

Hi Michael,
It’s mainly because the taxonomies are no longer showing below the custom post types in admin, that’s why I figured out it’s not working.

I don’t mind giving you access to the site admin so you can see what you need, just let me know how can I send it to you safely.

Regards,
Mamdouh

I haven’t had time to look at it with debugging on, but it seems like the latest version of the plug-in doesn’t read or interpret the old post types properly, but they are still saved properly.

Hubert, there was an array key change that needed to be made, so if your current new options don’t match up, then it’s not going to register parts correctly. Re-converting the settings should get the keys matching up again. Just need to delete the new options one way or another so the convert happens again.

Is there a way for the plug-in to do it? I could follow instructions and update that myself, but it’s a bit confusing for users who would otherwise expect things to just self-update.

In the meantime, I’m back to the old version, so there’s nothing urgent.

Mamdouh, send credentials to michael @ webdevstudios.com and reference the thread here, please, so I know context.