custom posts, wrapping it up

Hi allm,

You’re right, it’s just like I requested :). Thanks!

1. Yes, it’s 'the_seo_framework_supported_post_types', found here, it bypasses the needed check for Title/Editor.
This will add it to the sitemap, have an SEO bar, in-post box, etc.

2. Yes.
2.a. Exclude Post IDs with this.
2.b. Exclude CPT with this.

3.a.Contact) I still have to find time to debug this, but I think @senlin has already given me a good testing plugin :). So I’m OK for now.

3.b.Public) The plugin has always detected if the post is public, prior to checking the other values.
Your suggestions are spot on, but they’ve already been implemented, a very long time ago.

Please check out the full extend of this code, which is used to fetch a post type.

It has been there ever since I supported in-post Metaboxes, but it’s wrapped inside a function since 2.6.0 (causing the bug).

That’s why I got so confused on your previous posts :).

I hope this clears things up!

Hi Sybre,

I don’t know where you get all the time to help us all out. Your support is fantastic.

1. and 2. Thanks. That was what I was looking for.

I’ll wait and see what future versions do for “guessing” the right actions for custom posts. It might be that always guessing it right is impossible. In that case I might write a plugin to edit settings per (custom) post for this, using your ‘guessing’ as the default. I’ll wait first, and see how things evolve.

3. I’ll see how things evolve and see if it is still wrong in future versions. In that case I can always mail you the details of my example.

For now I have tried your plugin on a not-so-important website of my own, and will wait for a future version as I use custom posts of all kinds in all of my websites.

I have looked at your code for fetching a post type. If I read correctly you check for the “public” argument. Usually that will be ok, but in theory you can define “public” as false and still make a public custom post (or the other way round). The value of the “rewrite” argument might be a good alternative or additional indicator.

Anyway, thanks for all your help. I made a 5 star review some time ago, even before testing your plugin, and now I want to give more than 5 stars…

Have a good day/night or whatever it is when you read this.

??

I’ll set this to resolved.

Hi allm,

I’m unsure if the rewrite value reveals any usable information, as I don’t know what the result will be if it’s set to (boolean) false. I think that’s the value I should be listening to, correct?

Your enthusiasm is highly appreciated! I really adore it :). Thanks!

@Sybre,

Yes, that is how I have been using it. If rewrite is not false WordPress will generate pages from the custom post (so SEO is needed). If rewrite is false no pages are generated, so no SEO needed. In that case the custom post is probably used in some other way (in a shortcode maybe). The rewrite arguments might also be a factor that needs to be accounted for. I’m not 100% sure.

It might be a good idea if we get some more input here.

The example that I wrote about has public=false, rewrite=false, but it has title+content. It gets a SEO metabox and also SEO column with CSS error. Both are not needed in my opinion.

I’m enthousiastic about your plugin AND the way you handle support. I can only guess at how much time is involved, and if I can help here and there that’s fine. Let’s all work together and make this THE plugin to go to when you need SEO.

Hi allm,

That makes perfect sense, thanks! I’ll go ahead and try it out :).

About the time involved, last week I’ve spent over 100 hours working, including about 20 on the day I released 2.6.1 as it fixed a major bug. 20 hours went into other projects that week which gave me bread.
A total of 2600+ hours have been put into the whole plugin, excluding support.
The major refactor of 2.5.2 to 2.6.0 it took me about 220 hours :).
I’m pretty exhausted as of now, and I think you can notice it as I normally do my own research before replying :).
This reply until here took me about 4 minutes, but some can take me hours as I want all facts to be as correct as they can be. So this whole reply took me ca. 20 minutes, as we’re digging deeper:

The issue with SEO is that most of it is guesswork and guidelines, and people want to know the real answer. This is what makes up for the most time, “guessing correctly”, for others.
If you really want to know what’s going on, you’d have to work at Google. And then you’d probably have to sign a confidential agreement. So that’s a bummer.
According to this video, it seems that they live test search algorithms, so your site can fluctuate within a day (I think that happened two weeks ago)!

So it’s an ongoing project, that will never see the end of days :), and any help is greatly appreciated!

Its a big effort, that’s for sure! Hope you keep getting bread on the table. And hopefully some cheese as well. And a few karma points here and there… ??

Hi Sybre,

Fantastic! Version 2.6.2 fixes the custom post issue that we talked about. I’ll start testing the plugin on more sites now. If anything comes up, I’ll let you know.

Have a good day!