WPIntell

Source evidence

remove option to protect "wp-content"

Hide WP · support · 2016-07-08T18:56:00+00:00

complaintsentiment
mediumseverity
0.75relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 32 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

26 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
tazotodua unresolved
hi. i think that protecting option for “wp-content” makes people into more brainstorming, thinking if that will be good or what to do after enabling them and etc.. however, that option is not needed at all, because in reality, hiding “wp-content” slug from links or etc, wont ever protect wordpress from being recognized.. anyone can easily type: example.com/wp-blog-header.php (or etc) and see if they generate white page,then that site is wordpress (any other CMS will just redirect to not found html page or etc). please, take this into consideration seriously. I have spent many time thinkng if it was worth to protect “wp-content”, till i’ve got to this conclusion…. just insert a note on option page, that the option is useless (just to let users know and stops searching if “wp-content” protection is worth to try). also, there are different measure to detect wordpress, for example while generating css classes in html… WP-ADMIN & login URL protection is much enough! https://wordpress.org/plugins/hide-wp/

Comments

0 shown

No comments were stored for this source.