Making WordPress.org

Changeset 8900


Ignore:
Timestamp:
05/31/2019 12:09:32 AM (6 years ago)
Author:
SergeyBiryukov
Message:

Plugin Directory: Update plugin approval email content to clarify for new developers that they're responsible for updating their code in SVN and what their username is.

Props Ipstenu.
Fixes #4482.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • sites/trunk/wordpress.org/public_html/wp-content/plugins/plugin-directory/admin/class-status-transitions.php

    r7694 r8900  
    237237        $subject = sprintf( __( '[WordPress Plugin Directory] %s has been approved!', 'wporg-plugins' ), $post->post_title );
    238238
    239         /* translators: 1: plugin name, 2: plugin slug */
     239        /* translators: 1: plugin name, 2: plugin author's username, 3: plugin slug */
    240240        $content = sprintf(
    241241            __(
    242242                'Congratulations, your plugin hosting request for %1$s has been approved.
    243243
    244 Within one hour you will have access to your SVN repository with the WordPress.org username and password you used to log in and submit your request. Your username is case sensitive.
    245 
    246 https://plugins.svn.wordpress.org/%2$s
    247 
    248 Here are some handy links to help you get started.
     244Within one (1) hour your account will be granted commit access to your Subversion (SVN) repository. Your username is %2$s and your password is the one you already use to log in to WordPress.org. Keep in mind, your username is case sensitive and you cannot use your email address to log in to SVN.
     245
     246https://plugins.svn.wordpress.org/%3$s
     247
     248Once your account has been added, you will need to upload your code using a SVN client of your choice. We are unable to upload or maintain your code for you.
     249
     250Using Subversion with the WordPress Plugin Directory:
     251https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/
     252
     253FAQ about the WordPress Plugin Directory:
     254https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/
     255
     256WordPress Plugin Directory readme.txt standard:
     257https://wordpress.org/plugins/developers/#readme
     258
     259A readme.txt validator:
     260https://wordpress.org/plugins/developers/readme-validator/
     261
     262Plugin Assets (header images, etc):
     263https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/
    249264
    250265WordPress Plugin Directory Guidelines:
    251266https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/
    252 
    253 Using Subversion with the WordPress Plugin Directory:
    254 https://developer.wordpress.org/plugins/wordpress-org/how-to-use-subversion/
    255 
    256 FAQ about the WordPress Plugin Directory:
    257 https://developer.wordpress.org/plugins/wordpress-org/plugin-developer-faq/
    258 
    259 WordPress Plugin Directory readme.txt standard:
    260 https://wordpress.org/plugins/developers/#readme
    261 
    262 A readme.txt validator:
    263 https://wordpress.org/plugins/developers/readme-validator/
    264 
    265 Plugin Assets (header images, etc):
    266 https://developer.wordpress.org/plugins/wordpress-org/plugin-assets/
    267267
    268268If you have issues or questions, please reply to this email and let us know.
     
    275275            ),
    276276            $post->post_title,
     277            $plugin_author->user_login,
    277278            $post->post_name
    278279        );
Note: See TracChangeset for help on using the changeset viewer.