[wp-forums] Stumbled across an old, closed thread with bad advice

[Mika A Epstein]

Even with wildly wrong stuff, unless the topic's open and on the current point release (3.3.x) we don't go back and edit. Old is old, and it's there for historical since the thought process has some merit to it :)

Heck when someone says edit core, I always reply with big, bold, italic, "Nooooooo!!!" instead of editing.

On Jun 7, 2012, at 7:00 AM, Chris Cox <chris at renaissance-design.net> wrote:

> The whole purpose of the endeavour is to remove functionality. I can't think of a single reason for removing the editor functionality where leaving it accessible but with an unobtrusive message below the editing pane wouldn't cause more problems than it solves. It's a different situation to the perms being incorrectly set, and requires a different approach - if functionality can't be used it should be hidden from the user unless it's intended that they should go about enabling it.
> 
> Installing a role management plugin instead of just setting a constant provided by core would be using a sledgehammer to crack a nut, but I purposely didn't pick on that particular piece of advice because I was well aware that it came from you. As Mika's pointed out, it was the best advice at the time but as of the creation of DISALLOW_FILE_EDIT it's obsolete, and thus shouldn't be the closest thing to an official answer anyone can find (given that you're a mod your words carry weight, and people tend to look on the forums for anything they can't find in the Codex).
> 
> As to no core edit being described: that doesn't appear to have stopped the last poster before the thread was closed from resolving to damn well do it anyway.
> 
> I was hoping it could be solved quite simply with a mod edit. Evidently not.
> 
> *Chris Cox*
> 
> Web Designer/Developer
> 
> Renaissance Design <http://www.renaissance-design.net/>
> 
> Mobile: +44 (0) 7779 336185
> 
> 
> On 07/06/2012 12:33, esmi at quirm dot net wrote:
>> on 07/06/2012 11:47 Chris Cox said the following:
>>> Two answers given, one of which was hacking core, the other breaking WP
>>> functionality by setting file permissions. The post comes second in the
>>> SERPS when I Googled the issue, so it's fairly high-profile.
>> 
>> Setting theme file permissions to read-only is not breaking WP functionality  - especially given that many vanilla installs do not have write permission on the themes folder by default. A third solution was also proposed in that thread - using role management.
>> 
>> Also given that no core edit was described, I don't see how this is an issue.
>> 
>> Mel
> _______________________________________________
> wp-forums mailing list
> wp-forums at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-forums