paygate / payweb_gravity_forms Goto Github PK

We use output buffering extensively in our theme and after implementing PayGate on a client site found that this was no longer working as it should. Eventually we identified that the problem is two calls to ob_start() in the plugin without corresponding calls to close the buffer (e.g. ob_end_clean().

The offending calls are on lines 62 and 103 of paygate.php - removing them both along with the unnecessary call to ob_clean() on line 104 resolves the issue.

We've made this change locally, but would appreciate it being included in the next update so we don't have to keep manually applying the fix.

Hi
I have been getting the error below

(index):543 Uncaught TypeError: Cannot read properties of undefined (reading 'indexOf')
at HTMLIFrameElement. ((index):543)
at HTMLIFrameElement.dispatch (fc0c975cfeda2be36628c923ee7f11c1.js:3)
at HTMLIFrameElement.v.handle (fc0c975cfeda2be36628c923ee7f11c1.js:3)
(anonymous) @ (index):543
dispatch @ fc0c975cfeda2be36628c923ee7f11c1.js:3
v.handle @ fc0c975cfeda2be36628c923ee7f11c1.js:3

Thanks for this plugin. It's working great! There's one thing I've run into that I'm not quite sure how to handle, so I figured I'd ask first to see if there's something I'm missing.

When exporting entries, and using a conditional, "Payment Status" is missing both the "Approved" and "Declined" options.

Example:

Is there anyway to get those options in the export select field, or do I have something mis-configured?

Thanks!

When the form is embedded without AJAX, it just continues to the thank you page, and when AJAX is on, I get this CORS error:

You can see the form at: https://theboxfashion.co.za/join/checkout-option-01/?flow=1

Current Behaviour:

Currently, the plugin defaults to using the form entry ID as the payment reference.

Proposed Feature:

Introducing a "Reference" section in the plugin settings would provide valuable customization options:

1. Use default reference (entry ID): Maintain the existing behaviour for streamlined use.
2. Select a field to use as reference: Allow users to pick a relevant existing field (e.g., invoice number, customer ID) to align with their payment reconciliation processes.
3. Hash the entry ID and use that as a payment reference: Offer a more secure approach by applying a hashing function (e.g., MD5, SHA-1) to the entry ID, creating an obfuscated reference.

Benefits:

• Adaptability: Accommodates varying payment processor requirements and diverse user workflows.
• Improved Reconciliation: Enables users to leverage more meaningful references for easier reconciliation on their payment processor's end.
• Potential Security Enhancement: The hashing option could provide an added layer of security if desired.

Hi there

The PayGate Gravity Forms plugin v2.2.11 for Gravity Forms v2.4.18 seems to create an error on WordPress version 5.7.2, any ideas on how to fix this? I updated my gravity form to the latest version Version 2.5.0.2 but this didn't solve the problem. Kindly advise on the solution.
Please see attached, the error only shows up when The PayGate Gravity Forms plugin v2.2.11 for Gravity Forms v2.4.18 is activated.

the error details caused by the PayGate Gravity Forms plugin v2.2.11 on WordPress site health.

Include option to process actions after payment, like writing an entry to a Google Sheet.

Example implementation:

• Gravity Forms Google Sheets

Documentation:

• How to Add Delayed Payment Support to a Feed Add-On