Making WordPress.org

Changeset 13730


Ignore:
Timestamp:
05/17/2024 06:37:24 AM (5 weeks ago)
Author:
dd32
Message:

Plugin Directory: Submission: Add a FAQ item of 'How can I expedite my plugin review?'.

Props lukecarbis.
Fixes #7065.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • sites/trunk/wordpress.org/public_html/wp-content/themes/pub/wporg-plugins-2024/patterns/page-add.php

    r13578 r13730  
    5555            </p>
    5656
     57            <h3><?php _e( 'How can I expedite my plugin review?', 'wporg-plugins' ); ?></h3>
     58            <p>
     59                <?php
     60                printf(
     61                    __( 'Your plugin review cannot be prioritised over others, to help us approve your plugin sooner, please ensure that you have read the <a href="%s">Security chapter</a> of the Plugin Handbook.', 'wporg-plugins' ),
     62                    'https://developer.wordpress.org/apis/security/'
     63                );
     64                ?>
     65            </p>
     66            <p><?php _e( 'Our three most common reasons for not approving a plugin are:', 'wporg-plugins' ); ?></p>
     67            <ul>
     68                <li><?php printf( __( 'The plugin contains unescaped output: <a href="%s">Learn about Escaping Data</a>', 'wporg-plugins' ), 'https://developer.wordpress.org/apis/security/escaping/' ); ?></li>
     69                <li><?php printf( __( 'The plugin accepts unsanitized data: <a href="%s">Learn about Sanitising Data</a>', 'wporg-plugins' ), 'https://developer.wordpress.org/apis/security/sanitizing/' ); ?></li>
     70                <li><?php printf( __( 'The plugin processes form data without a nonce: <a href="%s">Learn about Nonces</a>', 'wporg-plugins' ), 'https://developer.wordpress.org/apis/security/nonces/' ); ?></li>
     71            </ul>
     72            <p><?php _e( 'If the code in your plugin falls into one of the above categories, <strong>your plugin will not be approved</strong>. The plugin review team will refer you back to these Handbook pages, adding further delay to the review process.', 'wporg-plugins' ); ?></p>
     73
    5774            <h3><?php esc_html_e( 'What will my plugin URL be?', 'wporg-plugins' ); ?></h3>
    5875            <p><?php echo wp_kses_post( __( 'Your plugin&#8217;s URL will be populated based on the value of <code>Plugin Name</code> in your main plugin file (the one with the plugin headers). If you set yours as <code>Plugin Name: Boaty McBoatface</code> then your URL will be <code>https://wordpress.org/plugins/boaty-mcboatface</code> and your slug will be <code>boaty-mcboatface</code> for example. If there is an existing plugin with your name, then you will be <code>boaty-mcboatface-2</code> and so on. It behaves exactly like WordPress post names.', 'wporg-plugins' ) ); ?></p>
Note: See TracChangeset for help on using the changeset viewer.