WP DEBUG shows warning after activation

  • Resolved piccart

    (@piccart)


    9 years, 1 month ago

    Hi there!
    first of all, many thanks for your plugin, I use it in several websites and I love how is simple an yet has everything which is actually needed to create post_types and taxonomies. ??

    the situation is that I’ve switched on WP_DEBUG for other reasons, and I’m getting a couple of warnings related to CPT UI:

    Notice: Undefined index: rewrite_withfront in /XXXXXXXXXXXXX/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 324

Notice: Undefined index: rewrite_hierarchical in /XXXXXXXXXXXXX/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 325

Notice: Undefined index: rewrite_withfront in /XXXXXXXXXXXXX/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 324

Notice: Undefined index: rewrite_hierarchical in /XXXXXXXXXXXXX/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 325

    this is my test website, and I haven’t actually created any taxonomy nor post_type with your plugin.
    the plugin is updated to the last version (unfortunately I had debug mode off before updating so I don’t know if the error is a new thing..)
    I’ve tried deactivating and reactivating cause maybe there was something missing from the activation hook after updating, but no luck..

    everything seem working fine anyway, and if I turn off WP_DEBUG I won’t even see the alert. but I thought you would like to address this issue. ??

    cheers!

    https://www.ads-software.com/plugins/custom-post-type-ui/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    They’re only notices so they won’t affect anything.

    If I recall these specific ones correctly, it’s something I can’t “properly” fix because I still have people coming in from the old setting scheme. The way the settings were stored pre-1.0.0 involved string numeral zero, which was used to indicate boolean false caused issues with registration params when trying to check for empty/undefined values. All of the settings for new installs or amended/updated settings store intended boolean values as string “true” or “false” so that I can properly check against for empty values.

    Thanks for letting me know in case I missed them though. If you need to get rid of them, change the rewrite/rewrite slug fields to something else, save, and then re-edit back to original value and I believe it should take and stop showing the notices.

    Thread Starter piccart

    (@piccart)

    ok perfect!

    yes I imagined they were only very minor warnings.
    i just wanted to ensure that you were aware about it. ??

    I mark this as solved.
    thanks!

    so, when comming from old settings, what do you suggest?

    redo a new_cpt, then change old_cpt to the new_cpt, that will fix the notices?

    regards, pescadito

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    No need to completely redo things, just edit the related setting fields, and then re-set them back to what you want them to be. Should get them filled in, but I do honestly try to prevent them. There are a couple that I simply can’t prevent due to how pre-1.0.0 settings were done.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WP DEBUG shows warning after activation’ is closed to new replies.

Tags