Font Awesome Update v6.0.0 #192
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
July 31, 2024 07:36
…t Awesome 6 is set as the default.
This was referenced Jul 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I want to contribute something to the WordPress theme development community, especially for those using the wonderful Codestar framework that I am also using. With my changes, we can now use Font Awesome v6.0.0 as the default package. As you know, this package includes up-to-date brand icons like the Twitter X icon, which is highly needed. The details of my changes are as follows:
Changes made:
I have configured the Font Awesome version using the options below. Font Awesome 6 is loaded by default, so no further action is needed for that.
add_filter( 'csf_fa4', '__return_true' );ORadd_filter( 'csf_fa5', '__return_true' );