After clicking the “Save Changes” button at the bottom of the settings page, the page should refresh. At this point, there should be a notification banner at the top of the settings page saying:
Settings successfully saved. Undo
If you get:
Settings did not change, nothing to save.
then, whatever you tried adding to the templates is getting stripped out. Since both property and typeof are allowed attributes for the a, img, span, h1, and h2 HTML tags, it’s likely you are trying to use an unsupported HTML tag within the templates.
By default, Breadcrumb NavXT provides Schema.org BreadcrumbList compliant markup under the RDFa vocabulary. You shouldn’t actually have to add the property="itemListElement" typeof="ListItem" as it should have already been there. You may want to reset your Breadcrumb NavXT settings to the “factory defaults” via the Import/Export/Reset form in Breadcrumb NavXT Settings page Help menu/dropdown.
Is this an overlay message or does it appear at the very top, via some AJAX? If so… it might very well be that I never saw it when it vanishes after some time. Cause we have like more than half a dozen custom post types and that includes a lot of scrolling.
I even changed the code in the wp_options in the database directly, both in the normal and the backup table, and it always got overwritten.
Search console started like end of June with mentioning some cases… 61 on 27th of June, but as of yesterday that number rose to over 1.9k articles with that element missing. I did not change a thing during that whole time, and before June it was alright. Well and that’s why I tried to add that missing element in the template. It was not in the template in the WordPress backend, and it is not in the source code of the website.
And another thing that is confusing, the tpls in the backend have “li” elements, but the source code on the website nonetheless shows span.
Anyhow thank you for your answer.
The message appears at the top of the page, just like any other ordinary message within the WordPress admin (Breadcrumb NavXT doesn’t stray too far from the base concepts that the WordPress admin area already uses).
I would avoid manually editing the wp_options table entries, it’s a great way to inadvertently break things. If you want to try a “hard reset” of the settings, you can drop the two bcn_options entries from the wp_options table. At that point, Breadcrumb NavXT will use the default settings.
In general, you should not be using li elements in the breadcrumb templates. Instead use bcn_display_list() instead of bcn_display() for the calling code (or if you are using the widget, select “list” for the “Output trail as” widget option). Out of the box, Breadcrumb NavXT does not support the li element in the templates (it will get stripped out), there is a guide on how to add support to the li element (see https://mtekk.us/archives/guides/how-to-add-li-and-other-tags-to-breadcrumb-templates/), if there is some code lie that, the problem is the demo does not add the property or typeof attributes (that should be easy enough to do).
If the settings don’t seem to be saving/changes to them don’t appear to be reflected in the breadcrumb trail, then you should check the generated HTML of the breadcrumb trail and see if it is actually generated by Breadcrumb NavXT. If it is generated by Breadcrumb NavXT, then, you may need to hunt down where the custom code is that is interacting with Breadcrumb NavXT (hopefully it lives in a site specific plugin or your theme in the same file as the code enabling li elements in the breadcrumb templates).
Thanks for coming back to me.
Well changing the tables was kind of a last resort. I tend to make things work the way I need to. 😉 And I am thankful for plugins that offer some hooks. I wanted to use list elements as the CSS framework in use makes use of them and I did not want to add additional CSS for optimization purposes.
But I did not know that there is another way to call the plugin. Maybe you should add that to the instructions somewhere. I just did not visit the website before now. So thank you for the insight, this will help. 🙂 And I guess this info might have been communicated by you sometime around when this update happened, but yeah, I did not use the plugin back then.
Anyhow, thank you, also for maintaining the plugin.
