Source evidence

Plugin Breaking Hueman Theme Functionality

Team Showcase · support · 2020-09-21T14:40:00+00:00

Team Showcase plugin evidence original source source API

complaintsentiment

mediumseverity

0.86relevance

2replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

2 / 24 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

22 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

sachinagarwal94 unresolved

Hi Team, I have been using this since the start and I am very happy to use it, Recently I discovered that My theme’s functionality broke after I disabled your plugin. The plugin somehow disabled the Check All Functionality . Link to discussion I am referring to. Also, I am not able to open any post on mobile , But after disable your plugin everything is working fine. I have linked relevant posts for your reference and understanding. Regards. Sachin Agarwal The page I need help with: [ log in to see the link] Thanks for your post, could you please check browser console area if there any JS error is showing? its probably js error issue on the plugin list page. please send me a screenshot of browser console area if you see any js errors. Regards This happens to me too. The “checkall” checkboxes don’t work anywhere in the WP admin. For example go to Plugins and click the checkall checkbox, nothing happens. Nor on the updates screen, or Media, or Posts/Pages, etc. I’ve tried on two sites and a test site on localhost, the Team Showcase plugin causes it somehow when it’s active. The only message seen in console log is “Unchecked runtime.lastError: The message port closed before a response was received.” I can’t say if that is part of the cause, but it’s there on all the sites I test. However, on one site when I disable the plugin (and checkboxes work again), this error still showed up in console, so it could be unrelated. I hope that helps.

Commercial Context

Opportunity

member and course operations

Team Members paid-access operations for protecting paid access, course delivery, and subscriber operations

Buyer: course creators, membership businesses, and agencies

Wedge: monitor team members access rules, course delivery, subscriber billing, and support-heavy failures

Investigate Pain card complete market

Analysis

heuristic-v1

Summary: Plugin Breaking Hueman Theme Functionality: users show bugs, compatibility, support pain that may indicate a product gap.

Evidence quote: Plugin Breaking Hueman Theme Functionality Hi Team, I have been using this since the start and I am very happy to use it, Recently I discovered that My theme’s functionality broke after I disabled your plugin.

Affected feature: bugs

bugs compatibility support value

Plugin

API

Team Showcase

1.0K active installs · 197.6K downloads · rating 80.0

meet the team page members profiles team team members team showcase

Comments

2 shown

PickPlugins 2020-09-22T16:07:00+00:00

Thanks for your post, could you please check browser console area if there any JS error is showing? its probably js error issue on the plugin list page. please send me a screenshot of browser console area if you see any js errors. Regards

Guyinpv 2020-12-29T08:16:00+00:00

This happens to me too. The “checkall” checkboxes don’t work anywhere in the WP admin. For example go to Plugins and click the checkall checkbox, nothing happens. Nor on the updates screen, or Media, or Posts/Pages, etc. I’ve tried on two sites and a test site on localhost, the Team Showcase plugin causes it somehow when it’s active. The only message seen in console log is “Unchecked runtime.lastError: The message port closed before a response was received.” I can’t say if that is part of the cause, but it’s there on all the sites I test. However, on one site when I disable the plugin (and checkboxes work again), this error still showed up in console, so it could be unrelated. I hope that helps.