In our Stripe logs, we see errors when editors try to purchase access to content while previewing a page. In this case, we should probably just strip the preview parameter from the URL.

Eventually, spam user creation will become an issue. This would be our first step to combat it.

Down the line, integrating with a social login plugin instead of having an email/password signup form could be both a feature and decrease spam further.

In Stripe, products can be set up where customers choose the price that they pay. This would be a great feature for RWS to take advantage of, but we currently receive the following issue when trying to register for that kind of price:
Error creating checkout session. You can only specify 1 line item when specifying a price with "custom_unit_amount" configured. Specify a single line item with a quantity of 1.

The reason for this is that when we create a checkout session for a one-time payment price (which "customer chooses price" is considered), we also create a $0 subscription in the same Checkout session. This is because a user's access is determined by whether they have an active subscription for a product.

Until it is possible to have both a free subscription and a "customer chooses price" product in a single checkout session, supporting that pricing model would require a substantial shift in how RWS works.

On a completely new site with WP 6.6.1 and RWS 1.0.9, when visiting the post and page editor (for both new and existing posts), I'm getting the following error: "The editor has encountered an unexpected error." with the following JS error reported in the console:

TypeError: undefined is not an object (evaluating 'e.metaValue.includes')

which appears to be coming from this part of the editor sidebar component:

which is probably due to the generated restricted_product_ids post meta not being an array for the current post.

Some sites already have a Stripe account where they have been selling subscriptions and may want to link their existing Customers to WordPress users. Right now, this would involve updating metadata in the database directly.

It would be nice to:

1. On the Add User page, allow setting a Customer ID
2. Allow editing the Stripe Customer ID on the Edit User page

RWS works great for sites that just want to monetize their content, but what happens when such a site grows and needs other membership features? Ideally, those sites would have a way to "upgrade" to PMPro to have access to all of its add ons and integrations.

In order for this migration to work, the following steps would need to be taken:

• Create a PMPro membership level for each Stripe product
• For each user, check if they have subscriptions in Stripe. If so, give them the corresponding PMPro membership with an expiration date for the next payment date if the sub is not free. In the RWS Stripe account, pause collection so that they are not charged again
• For each piece of content that is restricted by RWS, restrict it to the corresponding PMPro levels

From there, sites can simply deactivate RWS and complete setup for PMPro WITH A NEW STRIPE ACCOUNT. All RWS data (including Stripe subscriptions) will remain intact in case something goes wrong with the migration.

Drawbacks:

• Users with paid RWS subscriptions would need to check out again in PMPro at the end of their current payment period
• If users have multiple RWS subscriptions, MMPU would be needed on PMPro site