[wp-meta] [Making WordPress.org] #8039: Plugin Directory, API: Return one new plugin field: 'php_plugin_name'

[Making WordPress.org]

#8039: Plugin Directory, API: Return one new plugin field: 'php_plugin_name'
------------------------------+--------------------
 Reporter:  alberttarress     |      Owner:  (none)
     Type:  enhancement       |     Status:  new
 Priority:  low               |  Milestone:
Component:  Plugin Directory  |   Keywords:
------------------------------+--------------------
 We have noticed that a huge amount of plugins are defining their name on
 the main .php file in a 'simplified' way, while when defining the
 readme.txt name, they add a more 'SEO-friendly' large name.

 We can see an example with the following plugin: Everest Forms.
 If we look at the name they define on their main file 'everest-forms
 /everest-forms.php', it is just "Everest Forms" (displayed on the normal
 WP plugins list page).

 But when looking at the readme.txt file, we notice its name is "Contact
 Form by Everest Forms – Simple Contact Form to Advanced Contact Form,
 Quiz, Survey, & Custom Contact Form Builder for WordPress"

 The same is done by more and more plugins every day.

 We think this change on the plugin name might be confusing for some users,
 since if the user clicks on 'view details', the plugin name displayed is
 the one from the readme.

 Not only that, but a whole lot of external services that fetch the Plugin
 Directory API are retrieving this 'long' name, instead of the name that
 every user sees on the plugin's list page.

 Probably the plugin name from the main php file is not currently being
 stored on the plugin directory. It might be useful seen the differences
 between both names.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8039>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org