Allow account creation during checkout for fixed-seat configs

[gausam]

Allow configurations where the number of seats is fixed and cannot be edited by the user during checkout.

All Submissions:

• [x] Have you followed the Contributing guideline?
• [x] Does your code follow the WordPress' coding standards?
• [x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

How to test the changes in this Pull Request:

1. Use a fixed-seat config such as

global $pmprosm_sponsored_account_levels;
$pmprosm_sponsored_account_levels = array(
    2 => array(
        'main_level_id' => 2,
        'sponsored_level_id' => array(1),
        'min_seats' => 5,
        'max_seats' => 5,
        'seats' => 5,
        'seat_cost' => 0,
        'sponsored_accounts_at_checkout'  => true,
    )
);

2. Visit the checkout page for the level
3. You should be able to create 5 test accounts and the box to edit the number of accounts will not be displayed

Other information:

• [x] Have you added an explanation of what your changes do and why you'd like us to include them?
• [x] Have you successfully run tests with your changes locally?

Changelog entry

Allow account creation during checkout for fixed-seat configs

[andrewlimaza]

Thanks for this, please can you test renewals for 'parent' accounts. The fields should be hidden by default and then shown if the user unchecks the 'keep child account active' or it should show the number of fields for the remaining amount of uses for that level. So if they've used 2/3, show one field. If they uncheck a child account, it should show 2 fields (1/3 'uses')

Here's my setup used for this test: global $pmprosm_sponsored_account_levels; $pmprosm_sponsored_account_levels = array( //seats based on field at checkout 1 => array( 'main_level_id' => 1, 'sponsored_level_id' => 2, 'seats' => 2, 'seat_cost' => 10, 'sponsored_accounts_at_checkout' => true, ) );

Screenshot:

[andrewlimaza]

Here's the error message when trying to checkout -

[gausam]

Thanks, Andrew 👍 I've added adjustments to handle the renewal scenario and I successfully tested with scenarios:

• Keep sponsored accounts as-is during checkout
• Replace first sub-account only
• Replace second sub-account only
• Replace both sub-accounts (fails but due to an unrelated bug on dev)