John Havlik

That screenshot is helpful. It appears to be the legacy widget that is getting pulled in there. I’ll have to dig into what may be causing the widget to not load (hopefully it isn’t something weird that Elementor is doing like whitelisting widget versions).

Within a search results page, as long as the call to bcn_display() is before the loop/outside of the loop, it should figure out that it is on a search results page. If you trying calling this within the loop, it is likely to not figure out that it is a search results page.

• This reply was modified 1 year, 5 months ago by John Havlik.

Yeah, this was previously reported in this thread: https://wordpress.org/support/topic/function-_load_textdomain_just_in_time-was-called-incorrectly-11/. A fix is in the development branch (on github), a release will show up some time before the end of the year.

You are likely breaking a translation string for Breadcrumb NavXT/adminKit, hence the error. I don’t know what theGP_remove_comments_are_closed_here function looks like, but my guess is you’re returning NULL (or simply failing to return anything) on the Breadcrumb NavXT translation strings. Generally speaking, filters should not break the API (you should not be returning NULL for something that must return a string).

Interesting, ultimately, it still sounds like something (MailPoet in this case) is breaking the WordPress API. That said, the function that gets tripped up here is slated to get refactored soonish (next major release), in the meantime, a check is being added to prevent the warning.

I’m tracking this in the following github issue: https://github.com/mtekk/Breadcrumb-NavXT/issues/302

The “Primary Category” feature is not something that is part of WordPress itself (Yoast is adding that). You’ll need extra code to tell Breadcrumb NavXT to use the primary category. You can use the bcn_pick_post_term filter to do this, there are also plugins that exist that allow you to specify what term/category Breadcrumb NavXT uses (Order Bender, and Breadcrumb NavXT Paths).

As for where the breadcrumb trail is showing up on your site, that is likely due to differences in how the theme handles posts and pages. It looks like in both cases the breadcrumb trail is placed below the title, it’s just on posts the title is below the post image while on pages it is above the post image. You’ll likely need to modify your theme/the location where bcn_display() is called within the theme to get the breadcrumb trail where you want.

This is most likely caused by overly aggressive ModSecurity rules. You will need to work with your webhost to identify the rules causing the problem and adequately adjust them. I expect that the HTML within the breadcrumb templates is causing the overly aggressive rules to trigger.

@coriolis_too thanks for digging into this farther. Given the error I was expecting something like this but was lead astray by the line number PHP was giving.

@juliemoynat thanks for fixing the translation and notifying the translation team. I’m not sure why your replies were deleted from the thread, I think they provided important context.

@audrasjb thanks for getting the fixed translation string approved and following up on this. It looks like there may be an opportunity to improve the translation tool and WordPress itself here. WordPress should check for PHP errors when loading a translation package, similar to what it does on plugin activation. Additionally, the translation tool could warn on strings that would cause a sprintf/printf error, the tool already identifies these printf tags in the original string (maybe it could even prevent such a translation from being approved).