WPIntell

Source evidence

Custom markup Breaking entire site please fix

Favorites · support · 2025-05-31T03:42:00+00:00

Favorites plugin evidence original source source API
complaintsentiment
mediumseverity
0.93relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

1 / 21 rows with source links

4.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
sarahuk27 unresolved
Hi Support Custom markup is not saving in the database and its showing / > only after saving and its breaking entire webiste HTML. fa fa-heart — trying to add this font awseomr Please fix this issues and update the plugin ASAP https://prnt.sc/WGW4VB-uAt3i I have installed this plugin in fresh wordpress and look like its breaking ? https://prnt.sc/jX6MK9U2q2vc Thanks I have the same issue. It works to enter custom markup, but if you leave these fields empty and save settings for any other change it breaks and the Favorite button disappears and also eats other HTML markup on the pager after where the button was added… The cause is un-escaped inputs in the code. I have submitted a bug report here: https://wordpress.org/support/topic/bug-settings-inputs-not-escaped-causes-malformed-html-on-the-frontend/

Comments

3 shown
sarahuk27 2025-05-31T03:58:00+00:00

I have installed this plugin in fresh wordpress and look like its breaking ? https://prnt.sc/jX6MK9U2q2vc Thanks

chinchillagodzilla 2025-06-03T19:16:00+00:00

I have the same issue. It works to enter custom markup, but if you leave these fields empty and save settings for any other change it breaks and the Favorite button disappears and also eats other HTML markup on the pager after where the button was added…

squarestar 2025-06-06T11:45:00+00:00

The cause is un-escaped inputs in the code. I have submitted a bug report here: https://wordpress.org/support/topic/bug-settings-inputs-not-escaped-causes-malformed-html-on-the-frontend/