I have my breadcrumbs and other layout assets generated from custom Views that pull specific parts of the taxonomy structure.
Example Breadcrumb: Rehabnow.org (main link) > Wisconsin (Parent Taxonomy Slug View) > Appleton (Child of State Taxonomy Slug View) > Center Page (Current Post/Page)
But recently, the slug URL is not pulling correctly, and is adding "%0A%09%0A%09%0A%09%0A%0A" after the slug, example:
hidden link
On the content template using the view, there are no characters after the ] bracket closing the view, within the views there are no characters or spaces after the <wpv loop> which only contains [wpv-taxonomy-url] and has DIV wrapping and filter/search disabled.
It started randomly, and I have rebuilt the views, enabled and disabled every plugin, changed to the default theme, and dug deep into each taxonomy (which also do not have additional characters in the slug) and have found no solution.
Link to a page where the issue can be seen: hidden link
This center is using a custom template where I put the views code in the 'facility summary' box, as well as in the breadcrumbs.
- In the 'Facility Summary' box, the shortcode works properly, there is no additional text after the URL.
- In the breadcrumbs, SAME VIEWS SHORTCODES, the additional characters appear.
- The additional characters appear using the SAME VIEWS SHORTCODES in the 'Treatment Facilities Similar to Amethyst Recovery Center Near Port Saint Lucie, Florida' box as the URL is at the end of the H3 tag.
It seems like it only breaks when it's wrapped in an HTML tag, which I can't really get around as the 'Taxonomy URL' function doesn't add the required text after for SEO purposes.
I have tried to enter these in Custom HTML Blocks, Classic Blocks with Views Shortcode inside, and Text / Views Blocks, as well as minifiying the HTML in the Custom HTML block.
I expected to see:
The proper URL's listed as it does in the 'Facility Summary' content block.
These views/slugs are used elsewhere on the site on other content pages (State Pages, City Pages, Home Page) and are wrapped in HTML and work just fine.