Source evidence

Bug with XML-RPC settings

No Nonsense · support · 2024-11-23T11:01:00+00:00

No Nonsense plugin evidence original source source API

mixedsentiment

mediumseverity

0.78relevance

3replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 20 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

15 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

Ov3rfly resolved

If option “Disable XML-RPC” and “Also kill any incoming XML-RPC request” is active and you only switch off the “Disable XML-RPC” option, the sub-option is no more visible in backend but access to xmlrpc.php in frontend is still blocked with 403. Expected behaviour: Disabling top-option should also disable sub-option. No Nonsense 3.5.0, WordPress 6.6.2 Thanks… I’ll look into the feasibility of making the sub-settings dependent on the status of the “parent” setting. This issue is fixed now in version 3.5.0.2. Thanks, works as expected now. Sidenote, cosmetic, unrelated: The settings element nav.r34nono-secondary-menu overflows with some screen widths and german language admin interface.

Commercial Context

Opportunity

support triage and conversation operations

Remove Comments support operations workflow for reducing support load and keeping customer conversations moving

Buyer: support-heavy site owners, agencies, and community operators

Wedge: triage repeated remove comments threads, failed replies, knowledge gaps, and escalation workload

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Bug with XML-RPC settings: users show bugs, compatibility, missing feature pain that may indicate a product gap.

Evidence quote: Bug with XML-RPC settings If option “Disable XML-RPC” and “Also kill any incoming XML-RPC request” is active and you only switch off the “Disable XML-RPC” option, the sub-option is no more visible in backend but access to xmlrpc.php in frontend is still blocked with 403.

Affected feature: bugs

bugs compatibility missing feature reliable

Plugin

API

No Nonsense

1.0K active installs · 42.4K downloads · rating 90.0

remove comments remove emoji remove howdy remove wordpress logo remove xml-rpc

Comments

3 shown

Room 34 Creative Services, LLC 2024-11-25T16:10:00+00:00

Thanks… I’ll look into the feasibility of making the sub-settings dependent on the status of the “parent” setting.

Room 34 Creative Services, LLC 2024-12-02T16:36:00+00:00

This issue is fixed now in version 3.5.0.2.

Ov3rfly 2024-12-05T09:13:00+00:00

Thanks, works as expected now. Sidenote, cosmetic, unrelated: The settings element nav.r34nono-secondary-menu overflows with some screen widths and german language admin interface.