You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I have multiple collections that use the same fieldsets for things like content (including the field that SEO Pro pulls the description from) as well as images. When I view entries on the front end from collection A (Press Releases) I get the meta tags I would expect (description, og:image, etc.). When I view entries on the front end from collection B (Stories) I get all of the meta tags I would expect EXCEPT the description tags (description and og:description). Section defaults are set up the same for collections A and B.
Furthermore, if I modify the section defaults for collection B I am still unable to get the meta description fields populated. I can instruct collection B to fallback to the default site description and still no descriptions show up on the front end. Similarly, I can instruct collection B to use a hard-coded string as a description and still no descriptions show up on the front end. For whatever reason, it seems as though collection B just does not want to display meta description tags regardless of how it's set up, despite collection A having no troubles and virtually the same configuration.
I'm happy to provide any additional information that might be useful here.
The text was updated successfully, but these errors were encountered:
Hello, I have multiple collections that use the same fieldsets for things like content (including the field that SEO Pro pulls the description from) as well as images. When I view entries on the front end from collection A (Press Releases) I get the meta tags I would expect (description, og:image, etc.). When I view entries on the front end from collection B (Stories) I get all of the meta tags I would expect EXCEPT the description tags (description and og:description). Section defaults are set up the same for collections A and B.
Furthermore, if I modify the section defaults for collection B I am still unable to get the meta description fields populated. I can instruct collection B to fallback to the default site description and still no descriptions show up on the front end. Similarly, I can instruct collection B to use a hard-coded string as a description and still no descriptions show up on the front end. For whatever reason, it seems as though collection B just does not want to display meta description tags regardless of how it's set up, despite collection A having no troubles and virtually the same configuration.
I'm happy to provide any additional information that might be useful here.
The text was updated successfully, but these errors were encountered: