My first suggestion is going to be flushing your permalink rules, which can by done by visiting the permalinks page and hitting save without changing anything.
If that doesn’t fix anything, let me know and we’ll continue from there.
If you’re not able to edit them at all, even from the WP admin then that’s a new bug to me, and I have no present explanation. Most of the issues with the 1.x upgrade has been permalink based and 404 errors.
Hi Michael,
The permalinks reset didn’t work for me. Do you have any other suggestions?
Thanks!
From the looks of it, if I’m seeing the links right, you don’t even have permalinks enabled, which makes that an unrelated issue.
For example: http://ulyssespress.com/?p=4166 from the Genres page. If they’re not finding posts from that, I am not sure what’s going on, unless those post rows are no longer in the database.
Are you willing to let me into the admin to see if I can determine anything?
Sure. What’s the best way to contact you?
set up an account using michael@webdevstudios.com for the email. user/pass doesn’t matter. I’ll get the notification there.
Thanks! I’ll send the info over to you in a bit.
Alrighty, yours was surprisingly fun to debug. Not sure why.
Anyways, the missing UI parts for edit/view/etc was because of a minor anomaly of your post type slug had capital letters in it, which they shouldn’t have. Because of that difference, it prevented you from interacting with them, and affected the frontend queries.
I went through the post types you have, and made some adjustments, mostly in the lowercasing of the slugs. Based on the way the plugin is written, it actually made “duplicates” with the exact same settings, and then I deleted the “bad” ones without having to worry much about missing settings.
Thanks to you having that phpmyadmin plugin available, I was able to execute a couple statements that updated the post_type columns for your posts that had the capitalized version. Once I was done with that, the listings for them all showed the links that you’re expecting, and the frontend queries properly.
Hope that takes care of all the issues 😀
Thank you so much for taking your time to look at the WordPress template code. Things are in order now and the books show up. The only thing missing now is typing the markup and css back with the single.php file.
I assume there is a way to activate a widget that allows you to turn on that option? Something like a parent or single page template.
I’ll poke around, but thanks again! 😀
Not quite following with that last part, as our plugin doesn’t do anything with widgets or the actual template files.
The custom post type pages are not taking in the markup or styles from the single.php file. It use to, but not anymore after the WordPress update. Similar to page attributes, I would like to find something similar for post types.
Is there a way to add this feature, or how to change the code to use single.php?
Unless somehow the settings are affecting the template hierarchy, which they shouldn’t be, I am not sure what’s going on. Is there perhaps more specific template files being selected instead?
Check out the “Show Template” plugin to help confirm what’s getting used, if necessary.
I activated the plugin, but I don’t see the comments that are suppose to be generated in the footer.
Actually, I fixed it! When you changed the capitalization issue in the code, the single.php was still looking for a capitalized “Books”.
Correct code:
<?php if(get_post_type($thepost) == 'books'): ?>
as an alternative, you can create single-books.php to keep your logic/templates separated out. Other than that, good point and good catch.
