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

collision between FontAwesome 4 and 5 in backend #571

Closed
medarob opened this issue Jul 24, 2023 · 3 comments
Closed

collision between FontAwesome 4 and 5 in backend #571

medarob opened this issue Jul 24, 2023 · 3 comments

Comments

@medarob
Copy link
Contributor

medarob commented Jul 24, 2023

For a while now, the following problem exists:
When you have two extensions and each one uses a different FontAwesome version in the backend.

example:
Mask still uses FontAwesome 4. (I just noticed the usage of the extension friendsoftypo3/fontawesome-provider in the system and it seems it is required by mask)
We have another extension installed which uses FA5: https://github.com/DirkPersky/typo3-rte-ckeditor-fontawesome

If I chose an icon for a mask element the following will be shown on pages, which have an RTE field:
grafik

This should be the circle icon.

It seems that the icon unicode value has changed (and probably also the syntax) in FA5.
So, FontAwesome 5 is now used in the backend because of the other extension.

Solution/Suggestion
Is it possible to add an option in the mask configuration to choose the FontAwesome version which should be used in the backend, so that mask supports FA5 (and maybe FA6 for the future)?

I know, that this happens only if two or more extensions with different versions of FontAwesome are used.

@medarob
Copy link
Contributor Author

medarob commented Jul 24, 2023

ok, that seems to be a duplicate of #485 ?

@nhovratov
Copy link
Collaborator

Yes, seems like it.

@nhovratov
Copy link
Collaborator

Closing as of duplicate.

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

No branches or pull requests

2 participants