Reüel

Thank you, glad we could help!

Upon further investigation, the console error seems to be caused by the custom post type not supporting custom-fields. After adding support in register_post_type(), the Wikipedia preview works as expected.

SiteGround confirmed in support chat they’re on it:

I can see that this has been raised already in terms of what is going on. So our wordpress developers are on it and are working on a solution.

It seems this is caused by the changes in Speed Optimizer version 7.4.5 in the function add_async_attribute( $tag, $handle, $src ) for the “Defer Render-blocking JS” setting.

• 7.4.4 → https://plugins.trac.www.ads-software.com/browser/sg-cachepress/tags/7.4.4/core/Front_End_Optimization/Front_End_Optimization.php#L240
• 7.4.5 → https://plugins.trac.www.ads-software.com/browser/sg-cachepress/tags/7.4.5/core/Front_End_Optimization/Front_End_Optimization.php#L240

In our case, these are the values that this method receives (please note I’ve added some spaces in the source URL to prevent this forum to replace characters):

$src = 'https://www.example.com/test.js?siteground-async=1 & # 0 3 8;ver=1.0.0';

$tag = "<script type='text/javascript' src='https://www.example.com/test.js?siteground-async=1&ver=1.0.0' id='test-js'></script>";

The call to remove_query_arg( 'siteground-async', $src ) then results in https://www.example.com/test.js#038;ver=1.0.0 and the resulting $tag of the add_async_attribute() function then contains an invalid URL (resulting in an endless stream of HTTP 404 errors):

https://www.example.com/test.js&ver=1.0.0

Hope this will be fixed soon!

• This reply was modified 1 year, 3 months ago by Reüel.
• This reply was modified 1 year, 3 months ago by Reüel. Reason: Special characters got replaced

We are unable to reproduce any issues when using multiple pages in the form. The issue you’re seeing is probably due to misconfiguration.

Payments are started based on the form entry. Please make sure the entry contains at least one product and conditions in the payment feed do not prevent the payment from being started for your entry.

Can you elaborate a bit on what you’re trying to accomplish exactly? It’s not clear to me. Are you trying to offer SEPA Direct Debit or to hide this method on the form?

SEPA Direct Debit is usually used for the recurring payments, for which the first payment has been completed with iDEAL, Bancontact or SOFORT. However, it is possible to let Pronamic Pay create a “mandate” at Mollie — required for SEPA Direct Debit — for a first payment through SEPA Direct Debit by setting the “Account Holder Name” and “Account IBAN” fields, but it is more prone to user input errors compared to using a first payment through iDEAL/Bancontact/SOFORT. In test mode, Mollie will not automatically update a SEPA Direct Debit payment to the ‘completed ‘Paid’ status. Instead, you need to manually update the payment status and then request the the payment status within WordPress again. To update the payment status at Mollie, you can use the URL listed at WordPress admin → Pay → Payments → [ Choose payment ] → Meta box ‘Mollie’ → Click tr_XXXXXX link → Change Payment State.

You can add a Payment Methods field (from the ‘Payment Fields’ group) to your Gravity Forms form, in which you can select from which payment methods a customer can choose.

Gravity Forms does not offer front-end subscription management in an account on the site, as is the case with our integrations with WooCommerce Subscriptions, MemberPress and Restrict Content Pro. If you need this with Gravity Forms, you’d need to develop this yourself.

However, you can include subscription information like next renewal date and an URL to cancel the subscription by using merge tags in notifications, like {pronamic_subscription_renewal_date} and {pronamic_subscription_cancel_url}.

For detailed instructions, please refer to our documentation at https://www.pronamicpay.com/en/manuals/recurring-payments-with-gravity-forms/#gravity-forms-meldingen-instellen

If you want to send renewal notices through the Gravity Forms notifications, you should leave the plugin activated indeed.

I understand you want to offer the ‘Direct Debit’ (incasso) payment method on your form? In the Pronamic Pay payment feed settings of the Gravity Forms, you need to assign text fields to the ‘Account Holder Name’ and ‘Account IBAN’ fields on the tab ‘Fields’.

Please note that if you want to offer one-off payments with SEPA Direct Debit, this needs to be enabled for your account by Mollie.

In the settings of a Gravity Forms notification, there’s an option called ‘Event,’ and within that, there’s a choice named ‘Subscription Renewal Notice.’ Notifications using this event are sent one week before the renewal payment is scheduled to be created (the ‘Next payment date’ as mentioned in subscriptions; WordPress admin → Pay → Subscriptions).

This issue has been resolved in the just released Pronamic Pay version 9.6.0.

This error can happen with the database structure of older WordPress installations. We’ve recently identified a fix and an upcoming plugin update should resolve the issue. Please stay tuned.

For full details about this issue, see https://github.com/pronamic/wp-pronamic-pay-mollie/issues/32

@tiztou Mollie and MemberPress are indeed supported, but I understand you’ve already received reply from us on the same question via email. The yellow pending icons in front of payments are normal while the payment is being processed by Mollie. As soon as the payment has been completed, Mollie will let your site know and payments will be updated accordingly by Pronamic Pay.

PS: per the forum user guide, it’s recommended to start a new topic on the support forums instead of replying to someone else’s (see https://www.ads-software.com/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too).

Hmm, this is not a common issue and I’m not sure what could cause this or to which “value” the message refers. This is the full error message?

From what I found online, this could be related to a signature used in communication with the bank. Are the private key and certificate generated from within WordPress through the configuration or did you use the mentioned OpenSSL commands? Is OpenSSL up-to-date on the server (see WordPress admin → Tools → Site Health → Debug → Pronamic Pay → OpenSSL version).