• Resolved mhowl

    (@mhowl)


    Hi,

    I encountered an error after updating my plugin and WP to the latest version.

    The error is as follow –

    Notice: Undefined index: rewrite_withfront in /home/xxx/public_html/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 265

    Notice: Undefined index: rewrite_hierarchical in /home/xxx/public_html/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 266

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

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

    (@tw2113)

    The BenchPresser

    Nothing that will prevent the usage on your website, and until myself or someone else finds a good way to get around issues with PHP’s empty() function with regards to string ‘0’/’1′, I’m stuck with letting it show through. I tried fixing it previously but it introduced other issues.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    That said, I am willing to help hot fix the issue, if you really want. Do note that I have version 1.1.0 pending release and the hotfix would need to be re-applied to that version as well, because it’s not going to be fixed there.

    Thread Starter mhowl

    (@mhowl)

    Hi Michael,

    No problem. Thanks for your reply!

    Although I didn’t face this problem before updating my WP to 4.2.2.

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Issue shouldn’t have stemmed from a WP core update, honestly, unless you turned on WP_DEBUG since. That’s the only way it’d really start showing through.

    Thread Starter mhowl

    (@mhowl)

    Thanks Michael.

    I switched off debug mode and the error stopped showing.

    Thanks for pointing that out!

    Plugin Contributor Michael Beckwith

    (@tw2113)

    The BenchPresser

    Note to others: not a proper fix, but if you need to stop them from showing, that’s the way to do it. The offer stands to hotfix for anyone coming along in the future as well.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Error after updating Plugin’ is closed to new replies.