• Resolved Aldo

    (@ab_lu)


    Hello

    After updating to 7.0 we got this notice:
    Found 10 unknown legacy settings: Spost_page_hierarchy_type, Spost_post_hierarchy_type, Spost_attachment_hierarchy_type, Sauthor_name, Spost_wp-types-group_hierarchy_type, Spost_wp-types-user-group_hierarchy_type, Spost_wp-types-term-group_hierarchy_type, Spost_acf-field-group_hierarchy_type, Spost_acf-field_hierarchy_type, Spost_berufswelten_hierarchy_type

    After running the migration task, it keeps visible.

    Any idea?

    Thanks
    Aldo

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Havlik

    (@mtekk)

    After reloading the page is it still visible? The cause is the change is what is saved into the settings database. In the past settings ended up just accumulating (Breadcrumb NavXT would try to clean up things it knew about, but things like post types disappearing wasn’t handled well). Now, since only non-default values are stored in the database, when merging in the database values with the defaults, if there are extras, a message is presented to the user in the settings page.

    Specific to these settings being mentioned in your message, these messages should go away after refreshing the page (a page refresh after the settings migration is complete). These specific settings changed (from the string type to the enum type), and I’d only expect these to maybe show up only immediately after a setting migration (though the original cause of that behavior should have been fixed). Please let me know if this is showing up after you reload the page (would indicate the settings migration didn’t run properly on your site).

    Thread Starter Aldo

    (@ab_lu)

    Thanks for getting back.
    But, no. They persist after reloading.

    Plugin Author John Havlik

    (@mtekk)

    What happens if you change a setting and then press the “Save Changes” button, does the message go away?

    BTW, I’m opening a GitHub issue to track this: https://github.com/mtekk/Breadcrumb-NavXT/issues/263

    • This reply was modified 2 years, 11 months ago by John Havlik. Reason: add GitHub issue link
    Thread Starter Aldo

    (@ab_lu)

    @mtekk Thanks! Making a change and saving the settings page made the notice go away.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Found 10 unknown legacy settings after update to 7.0’ is closed to new replies.