Reüel

Unfortunately, Gravity Forms does not provide such functionality (like membership plugins do, which is supported by our plugin). We may add our own functionality for updating existing subscriptions started through Gravity Forms. If you want to have this functionality added with priority and are willing to contribute to the development costs, please contact us at [email protected] to discuss this further.

As a side note, we do not use the Subscriptions API from Mollie for subscriptions. The mentioned documentation from https://docs.mollie.com/reference/update-subscription is therefore irrelevant.

Action Scheduler is a third-party library for background task scheduling and processing. The logs help with debugging if issues arise, but the 31-day retention period is simply the default. The rate at which the logs grow depends on the number of payments and subscriptions and can vary by website. You can adjust this period as needed—it has no specific impact on our plugin’s functionality.

I understand new subscribers are getting an error during checkout. Could you please share the error message, so we can assist you further?

You can update to the latest plugin version, which will remove the iDEAL issuer selection for Mollie from the MemberPress checkout. No changes to any other settings needed.

Support for Contact Form 7 and PayPal are only available in the paid version. Just like a number of functionalities for WooCommerce, such as restricting payment methods to specific countries and customising the checkout button.

With your purchase of the Premium version, you support further maintenance and development of the plugin — so you can continue to safely accept payments in the future — and also get access to free email support and add-ons for showing fundraising progress and integrations with the WP All Export (https://www.wpallimport.com/export-wordpress/) and Notification (https://bracketspace.com/notification/) plugins.

The amount is stored per subscription. Therefore, if you want to change the amount only for new subscriptions, you can simply update the amount in the Gravity Forms form. This will leave current subscriptions unaffected.

Preslav, did you even look at the error message?

Fatal error: Uncaught TypeError: implode(): Argument #2 ($array) must be of type ?array, string given in /wp-content/plugins/sg-cachepress/core/Cli/Cli_Settings.php:91

This is line 91 in the Cli_Settings.php file:

\WP_CLI::error( 'We\'ve imported everything except the following settings: ' . implode( $result, ', ' ) );

The issue is with the implode(), because according to https://www.php.net/implode the function signature is (separator first):

implode(string $separator, array $array): string

Alternative signatures are also listed, e.g. the “Legacy signature (deprecated as of PHP 7.4.0, removed as of PHP 8.0.0)“:

implode(array $array, string $separator): string

I don’t need any further assistance from the Support Team, I just pointed you to a fatal error which can occur with your plugin so you can resolve this further with your developers. It doesn’t really matter in this case if you can reproduce the issue, because just by looking at the error message and corresponding code it is clear what the issue is and that a developer needs to resolve this.

FYI, apparently I looped over the results of wp site list --field=url in a multisite environment and this included the URL of a deleted site which is not pointing to a server anymore. Therefore, the “ssl_enabled": 1 from the settings could not be imported and resulted in an error. Currently this results in the fatal error message as mentioned, but with the updated parameters to implode() this error message is shown:

Error: We've imported everything except the following settings: ssl_enabled

Thanks for checking, Preslav. You mentioned that both export and import are successful, but in that case the error will not occur. I can’t test right now, but for example a case like enabling Memcached through settings import while Memcached is not enabled in Site Tools will probably trigger the error.

The red icon in the subscriptions overview reflects the subscription has been cancelled as expected in Pronamic Pay too. No payments will be started for subscription with this status.

From your screenshot, I now understand which date you’re referring to (I was thinking about the date being listed in the subscription details, after clicking the “#1711” link — which will also list the “Notes” section). I’ve forwarded this to our developers, so the next payment date will only be listed for active subscriptions in the future. I expect this to land in the next plugin update and therefore already mark this support topic as ‘resolved’.

Unfortunately, the current reporting functionality is limited to this year’s data. Enhanced reporting capabilities are on our radar, but changes in this area are not expected in the short term.

By default, the action scheduler deletes all completed and cancelled after 31 days. If you want to lower this period, you can use the filter action_scheduler_retention_period to set a retention period (in seconds).

For further details, please refer to the Action Scheduler source code at https://github.com/woocommerce/action-scheduler/blob/90b98e6fe97d455679b1d288f050cad8f6f79771/classes/ActionScheduler_QueueCleaner.php#L50-L61

When a MemberPress subscription is cancelled, the corresponding Pronamic Pay subscription should also automatically have been updated to the ‘Cancelled’ status. The next payment date will not be shown then anymore in the Pronamic Pay subscription details.

If the status of the subscriptions is not ‘Cancelled’, you might want to check the ‘Notes’ section in the subscription details to find out what caused the status change to the current status.

Hmm, I see GitHub makes the changes look like a lot more complex than they are ??

We’ll post here when an update is available.

Hello Jan-Willem, thank you for your message. We’ll be looking into the issue and let you know here once an update has been released which resolves the notices.

For development, you might want to follow along or contribute in https://github.com/pronamic/wp-pay-core/issues/201.

Perfect, thanks @cartpauj!