Themes
All themesNo clustered themes yet.
Market
Svg Icon matters only if the evidence supports a paid workflow around preventing client-site regressions before updates or edits go live, not a list of isolated fixes. The current commercial thesis is: Page-builder and editor changes can break layouts, CTAs, or client pages after updates. The entry wedge is to run pre-update checks, detect visible regressions, and produce client-safe rollback guidance.
Commercial opportunities need traceable source links before they are treated as build-worthy.
75.3% of this page's analysis has direct source links.
0 rows here require auditable proof before promotion.
0 rows have source counts but still need direct links.
Build an agency visual QA and update safety plugin for site builders and agencies: Page-builder and editor changes can break layouts, CTAs, or client pages after updates. The first wedge is to run pre-update checks, detect visible regressions, and produce client-safe rollback guidance.
The unmet need is not the individual complaint. It is the recurring business workflow: Page-builder and editor changes can break layouts, CTAs, or client pages after updates. Current stage: commercial watchlist.
No clustered themes yet.
Pain still appears around bugs, compatibility despite praise for quality, reliable.
Pain still appears around support despite praise for quality, easy.
Owned praise to avoid copying: reliable, support.
Weakness evidence: 1 unresolved support thread(s).
Watch for positioning evidence as more conversations are collected.
Error: Failed to initialize filesystem usage for creating self-hosted assets.: users show security, bugs, compatibility pain that may indicate a product gap.
Font Awesome · Error: Failed to initialize filesystem usage for creating self-hosted assets. mixed Multisite fatal errorMultisite fatal error: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Font Awesome · Multisite fatal error When trying to activate the plugin on a new multisite, got the message: Plugin could not be activated because it triggered a fatal error . mixed Can’t edit post_content in Classic Editor if plugin v5.0.1 or v5.0.2 is activeCan’t edit post_content in Classic Editor if plugin v5.0.1 or v5.0.2 is active: users show security, bugs, compatibility pain that may indicate a product gap.
Font Awesome · Can’t edit post_content in Classic Editor if plugin v5.0.1 or v5.0.2 is active Hi Support With version 5.0.1 we experience the issue as described in the thread: “Conflict between Font Awesome 5.0.1 and Toolset types 3.5.2”. mixed Plugin broke after 5.0.1 updatePlugin broke after 5.0.1 update: users show bugs, compatibility, performance pain that may indicate a product gap.
Font Awesome · Plugin broke after 5.0.1 update We get a message in WP admin that says: Failed to determine Font Awesome version when setting up self-hosted assets. mixed Issue with 5.0.1Issue with 5.0.1: users show bugs, compatibility, support pain that may indicate a product gap.
Font Awesome · Issue with 5.0.1 Hello there, Since updating to 5.0.1 we got an error message in the admin page : The Font Awesome plugin caught a fatal error. complaint Dangerous, written by clownsAn expired Font Awesome Pro license caused PHP fatal errors and took sites down instead of failing gracefully.
Font Awesome · my sites went down due to PHP Fatal error complaint Works SometimesWorks Sometimes: users show bugs, support pain that may indicate a product gap.
Font Awesome · Works Sometimes I have 2 sites that are almost identical running on the same server environment. complaint Comportamiento anómalo del plugin Font Awesome en WordPressThe user reports hundreds of thousands of internal HEAD requests from the Font Awesome plugin saturating CPU and affecting site availability.
Font Awesome · centenares de miles de solicitudes HEAD hacia el mismo archivo CSS complaint Poor patronising customer servicePoor patronising customer service: users show support pain that may indicate a product gap.
Font Awesome · Poor patronising customer service Font didnt work within the plugin it was linked to and then when I asked them about it, was told I wont help you unless you pay, read the instructions or ask the forum. complaint Multisite Fatal ErrorFont Awesome activates on most sites in a multisite network but throws a fatal configuration error on one site despite reinstall attempts.
Font Awesome · when I activate the plugin, I get: The Font Awesome plugin caught a fatal error praise updated: refunded meupdated: refunded me: users show bugs, performance, support pain that may indicate a product gap.
Font Awesome · updated: refunded me Update: They refunded me after issues so I revised my rating. complaint Conflict between Font Awesome 5.0.1 and Toolset types 3.5.2Conflict between Font Awesome 5.0.1 and Toolset types 3.5.2: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Font Awesome · Conflict between Font Awesome 5.0.1 and Toolset types 3.5.2 When I upgraded to 5.0.1 my text editors were set to hidden for my page editor and custom field that is used in the accordions. complaint FA icon picker not workingFA icon picker not working: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Font Awesome · Check the console for additional error information.”. complaint Unresponsive Tech Support / No Refunds AllowedUnresponsive Tech Support / No Refunds Allowed: users show bugs, compatibility, pricing pain that may indicate a product gap.
Font Awesome · Unresponsive Tech Support / No Refunds Allowed I purchased FontAwesome PRO, but it would not work with my theme. mixed objectcache.noticeobjectcache.notice: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Font Awesome · objectcache.notice Hi I’m getting this in my log file: [11-Mar-2025 23:55:35 UTC] objectcache.notice: The cache key font-awesome-last-used-release is incompatible with prefetching and the group transient should be added to the list of non-prefetchable groups. mixed 404's happening, even with plugin installed404's happening, even with plugin installed: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · 404's happening, even with plugin installed Hello, While I am here I thought I’d drop a note about another thing I found regarding favicons and perhaps this plugin. mixed Favicon only showing in Back-EndFavicon only showing in Back-End: users show bugs, compatibility, missing feature pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · Favicon only showing in Back-End It seems I am having the same issue as a few of people here. complaint Issue with 5.0.1 (Size Issue)Issue with 5.0.1 (Size Issue): users show bugs, missing feature, support pain that may indicate a product gap.
Font Awesome · Issue with 5.0.1 (Size Issue) Currently the Size setting is not changing the size of the Icon. complaint Couldn’t save those changesCouldn’t save those changes: users show bugs, missing feature, setup pain that may indicate a product gap.
Font Awesome · Couldn’t save those changes I just can’t save my settings. complaint Incompatible with page builderIncompatible with page builder: users show compatibility, missing feature, setup pain that may indicate a product gap.
Font Awesome · Incompatible with page builder After hours and hours of investigation and dead ends, I discovered that it is the Font Awesome plugin that causes Elementor and Elementor Pro editors to grey screen. complaint Why is it render blocking?Why is it render blocking?: users show performance, support pain that may indicate a product gap.
Font Awesome · Can you change this, considering that in 99.9% of use cases, the rest of the page should be able to display before Font Awesome is loaded and displayed without degrading user experience… The page I need help with: [ log in to see the link] It seems Font Awesome request is queued in a way that it is render blocking. mixed WordPress 7WordPress 7: users show bugs, compatibility, support pain that may indicate a product gap.
RIACO Icon Block · WordPress 7 Hello, any chance that RIACO could get support for WP 7 soon? mixed Favicon not showing on is_single() post pagesFavicon not showing on is_single() post pages: users show bugs, compatibility, support pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · Hello @harish , thanks for the quick response. complaint Preload Errors in devtools consolePreload Errors in devtools console: users show bugs, support pain that may indicate a product gap.
Font Awesome · Preload Errors in devtools console Hi, I’m getting the following notices in devtools console log: /:1 A preload for ‘ https://use.fontawesome.com/releases/v5.15.3/webfonts/fa-brands-400.woff2’ ; is found, but is not used because the request credentials mode does not match. complaint Mopbile doesnt workMopbile doesnt work: users show support pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · If you have a link I could test, it would be helpful. mixed says I don't have permissionssays I don't have permissions: users show bugs, setup pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · https://wordpress.org/plugins/custom-favicon/ Hello @vanessajw , Are you an administrator of the WP website you are installing this plugin on? mixed Custom Favicon not working on Front-EndCustom Favicon not working on Front-End: users show bugs, compatibility pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · Some themes have this issue because they dont have wp_head in their themes header. complaint Block Fails for Editors in GutenbergFont Awesome icon blocks break for Editor-role users on multisite because saved SVG content is stripped, leaving icons missing on the front end.
Font Awesome · users with the Editor role are unable to use the Font Awesome icon block complaint Most of the free icons won’t show using the pseudo-element methodMost of the free icons won’t show using the pseudo-element method: users show missing feature pain that may indicate a product gap.
Font Awesome · Most of the free icons won’t show using the pseudo-element method Using the CDN or Kit option there’s no difference, most of the 2,020 free icons found on fontawesome page by searching with the “Free” filter won’t show at all, just a crossed out rectangle appears. complaint Not too useful in 2024Not too useful in 2024: users show bugs pain that may indicate a product gap.
Font Awesome · The icon picker is buggy on top. complaint DELETED entire account on meDELETED entire account on me: users show support pain that may indicate a product gap.
Font Awesome · When I asked for support, they weren’t helpful, then stopped responding, communicated like children, then DELETED my entire account causing me hours of update time for several client sites. complaint Not good enough!Not good enough!: users praise quality, which suggests what competitors already do well.
Font Awesome · Please do your best, guys, we believe in you. mixed Apple Touch Icon for WebsiteApple Touch Icon for Website: users show setup pain that may indicate a product gap.
Custom Favicon – Easily Add a Favicon in WordPress · It works perfect! complaint Settings page gives error, unable to update from FA 6.0.0The Font Awesome settings panel failed with a JavaScript error, preventing a client site from switching versions to update the Twitter icon.
Font Awesome · does not let me in settings panel, where I assume I could have switched versions. complaint Breaks websiteBreaks website: complaint conversation with limited structured signal.
Font Awesome · Breaks website Some serious maintenance needs to happen here, this is useless Some serious maintenance needs to happen here, this is useless complaint Terrible it brokes everyting in my siteTerrible it brokes everyting in my site: complaint conversation with limited structured signal.
Font Awesome · Terrible it brokes everyting in my site It brokes everything on my website. Icons don’t work properly. Never set up it. It brokes everything on my website. Icons don’t work properly. Never set up it. complaint Bug: “This block has encountered an error” when clicking Style (TT4, WP 6.8.2)A Font Awesome update made rich text icons crash when opening the Style panel, and the vendor released a quick fix.
Font Awesome · This block has encountered an error and cannot be previewed complaint Issue with WordPress 6.9Font Awesome appears to conflict with WordPress 6.9 and ACF, preventing ACF file fields from opening the media window for the reporter.
Font Awesome · ACF file fields don’t open WP media window with the plugin enabled complaint Refused to connect because it violates the document’s Content Security Policy.Font Awesome icons stopped displaying because stylesheet requests are blocked by content security or CORS policies.
Font Awesome · Font Awesome icons are no longer showing up. complaint Fatal errorFont Awesome failed on a new network subsite because its configuration was invalid and reinstalling did not restore the missing stylesheet or settings.
Font Awesome · I already tried deactivating, uninstalling, and re-activating the Font Awesome plugin but it’s still not working.