Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Styling category_description #364

Closed
donaldjenkins opened this issue Nov 22, 2018 · 1 comment · Fixed by #453
Closed

Styling category_description #364

donaldjenkins opened this issue Nov 22, 2018 · 1 comment · Fixed by #453

Comments

@donaldjenkins
Copy link

It really would be nice if one were able to apply a tag and a class to category_description. This is the one element lacking to make to make content produced by the plugin completely customizable.

@klemens-st
Copy link
Collaborator

Agreed. We can implement it easily after merging #288.

@stale stale bot added the wontfix label Jun 17, 2020
Repository owner deleted a comment from stale bot Jun 22, 2020
klemens-st added a commit to klemens-st/List-Category-Posts that referenced this issue Mar 18, 2021
In addition to neccessary method updates and new shortcodes:
category_description_tag and category_description_class,
the category_description() function has been replaced with
the get_term_field() function because the former automatically
wrapped output in <p> tags. The default <p> tag has been retained
by updating the default LCP template.

Fixes picandocodigo#364
picandocodigo pushed a commit that referenced this issue Mar 22, 2021
In addition to neccessary method updates and new shortcodes:
category_description_tag and category_description_class,
the category_description() function has been replaced with
the get_term_field() function because the former automatically
wrapped output in <p> tags. The default <p> tag has been retained
by updating the default LCP template.

Fixes #364
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants