Skip Navigation

[Resolved] CRED Error when Completing Woocommerce Order

This support ticket is created 5 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Karachi (GMT+05:00)

This topic contains 9 replies, has 3 voices.

Last updated by nedG 5 years, 6 months ago.

Assisted by: Waqar.

Author
Posts
#1208615

I am creating a Membership site for a local civic league.

I have set up a Membership Renewal Form using CRED. Existing Members must be logged in to use this form.

Per your Membership Tutorial, I have configured the settings of the renewal form to add a particular product to the Woocommerce Shopping Cart... and then the user can proceed to checkout.

Everything seems to work smoothly on the front-end.

However the backend Admin area is a different story. Since I am only in a testing environment and not using any automated Payment methods (I am simply using Cash on Delivery)... the Order gets passed to Woocommerce as a "Processing" status. When I go into the Admin section and attempt to change the order status to "Completed", I receive a "white screen" with the following errors...

Notice: Undefined index: user_pass in /var/www/vhosts/croatanbeach.org/httpdocs/wp-includes/user.php on line 1543

Notice: Undefined index: user_login in /var/www/vhosts/croatanbeach.org/httpdocs/wp-includes/user.php on line 1546

Notice: Object of class WP_Error could not be converted to int in /var/www/vhosts/croatanbeach.org/httpdocs/wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/models/UserForms.php on line 475

Catchable fatal error: Object of class WP_Error could not be converted to string in /var/www/vhosts/croatanbeach.org/httpdocs/wp-content/plugins/cred-frontend-editor/application/controllers/notification_manager/queue.php on line 59

None of the account "changes" that I made during the Renewal Form Process ever get saved to the DB. It all just simply fails.

I know that you don't provide support for Woocommerce issues, but this seems like CRED related errors. I essentially have all of my plugins deactivated (except for just a few). I am starting to suspect a deeper issue.

#1209346

Hi Ned,

Thank you for contacting us and I'll be happy to assist.

To troubleshoot this issue, I'll recommend the following steps:

1. Please make sure that WordPress and all Toolset plugins are updated to their latest versions.

2. Next, you can temporarily disable all plugins other than the Toolset and the WooCommerce and then check the form again.

3. To rule out any custom or theme code conflict, it would also be a good idea to test this with a default theme like "Twenty Nineteen".

4. Based on the error you've shared, you can also temporarily remove any existing notification attached to the membership renewal form and see if the error is fixed.

If all these steps fail, I'll need temporary admin login details to access your website's admin area, for deeper troubleshooting.

I've set your next reply as private so that only you and our support team can access it.

Important note: Please make a complete backup copy of the website, before sharing the access details.

I hope this helps and let me know how it goes.

regards,
Waqar

#1210003

Hi Ned,

Thanks for writing back and for sharing these details.

I was able to access your website, after editing the 'hosts' file, but the username/password doesn't seem to work.

Can you please check and share them again?
(your next reply will be private as well)

regards,
Waqar

#1210022

Please try it again

#1210561

Hi Ned,

Unfortunately, the username and password that you provided are still not working.

Is it possible that your website is behind some sort of firewall or GEO IP restriction?

Can you share a clone or snapshot of your website, instead of direct access?
(it can be from this website or from another test website where the issue is reproducible)

We usually recommend the free Plugin “Duplicator” (http://wordpress.org/plugins/duplicator/) for this porpoise.

If you already know how Duplicator works, you can skip the instruction video and just send me the installer file and the zipped package you downloaded.

Duplicator Instructions:
hidden link

( note: I'll need both files and you'll probably want to use DropBox, Google Drive, or similar services, as the snapshot file will be quite big )

IMPORTANT: Remember to create or keep an admin account for me before creating the snapshot, or I won’t be able to log in. You may delete the new admin account once the snapshot has been built.

I will set your next answer as private so you can provide me the information securely.

regards,
Waqar

#1210641

I apologize. I must have typed something in wrong. I have rest the credentials to the ones mentioned previously and then checked it myself. Now they are working.

Pelase try once again.

Sorry.

#1211331

Hi Ned,

Thank you for waiting, during I performed some tests on my website.

Based on the settings from your website's user edit form, I was able to reproduce this issue on my test website.

When a user edit form includes an email notification that is attached to “When payment is complete” event, PHP error and notices are shown, on order completion.

Appreciate your report and I've shared these findings to the concerned team for further investigation. I'll keep you updated with the progress, through this ticket as well.

Meanwhile, as a workaround, you can disable the email notification attached to your renewal form and use WooCommerce's own email notification which is sent when an order is completed.

regards,
Waqar

#1219514

Hi,

This is to notify you that this issue has been fixed in Forms 2.3.2.
Notify us if the issue still exists.

Thanks.

#1241315

{ ticket status updated }

#1243318

My issue is resolved now. Thank you!