[wp-trac] Re: [WordPress Trac] #5651: Optimize get_plugin_data

WordPress Trac wp-trac at lists.automattic.com
Sat Jan 12 23:17:56 GMT 2008

#5651: Optimize get_plugin_data
 Reporter:  filosofo                          |        Owner:  anonymous
     Type:  defect                            |       Status:  new      
 Priority:  normal                            |    Milestone:  2.5      
Component:  General                           |      Version:  2.5      
 Severity:  normal                            |   Resolution:           
 Keywords:  has-patch get_plugin_data memory  |  
Comment (by darkdragon):

 It was a copy and paste error. It '''was''' in my version index after all.
 I'm not sure how many mistakes there are, as it only happens a few times
 while doing the phpdoc documentation. However that is why there is a
 ticket open to fix phpdoc documentation mistakes.

 Replying to Filosofo, I have to agree with DD32 on this one. It would
 introduce a regression if we forced the suggestion on Plugin Developers.
 The goal is to only pull in enough that we get all of the data, not
 completely break half the plugins out there.

 Something that '''should''' be, does not mean it is required. If it was
 required, then the wording would be '''must'''. '''Should''' just means
 you can do it, if you want, but it doesn't matter either way. Or that is
 what I read from the RFC (little bit complicated wording if you ask me).

 Patch completes all of DD32 suggestions. Any more?

Ticket URL: <http://trac.wordpress.org/ticket/5651#comment:13>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list