Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AIOSEOP meta box appears when SEO for post types is disabled #1067

Closed
wpsmort opened this issue Aug 9, 2017 · 3 comments

Comments

Projects
None yet
4 participants
@wpsmort
Copy link
Member

commented Aug 9, 2017

If you uncheck all post type and taxonomy boxes under Custom Post Type Settings and then disable SEO for Custom Post Types then the AIOSEOP meta box is still output on the Edit Post screen.

This has been a bug for a while now.

Steps to reproduce this:

  1. Go to General Settings > Custom Post Type Settings and uncheck all checkboxes and disable Advanced Options then click Update Options
  2. Go back to Custom Post Type Settings and set SEO for Custom Post Types to Disabled
  3. Edit any post or page and you should see the AIOSEOP meta box

This problem should go away when we remove the SEO for Custom Post Types option - Issue #68

@arnaudbroes

This comment has been minimized.

Copy link
Contributor

commented Aug 13, 2017

@wpsmort
I've tested this with two different, fresh local test sites and a few versions of WordPress (ranging from 4.8.1 to 4.0) and All in One SEO Pack (ranging from 2.4.15.3 (PRO) to 2.0.0 (FREE)) and it seems that this issue has been there since the start with 2.0.0 in both versions.

@michaeltorbert michaeltorbert removed their assignment Aug 15, 2017

contactashish13 added a commit to contactashish13/all-in-one-seo-pack that referenced this issue Nov 25, 2017

@contactashish13

This comment has been minimized.

Copy link
Contributor

commented Nov 25, 2017

@arnaudbroes

This comment has been minimized.

Copy link
Contributor

commented Nov 28, 2017

@michaeltorbert I tested this. Needs code review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.