Skip Navigation

[Resolved] Internal Server Error on Checkout

This support ticket is created 3 years 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 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 8 replies, has 2 voices.

Last updated by Mateus Getulio 3 years ago.

Assisted by: Mateus Getulio.

Author
Posts
#2554233

I am trying to: When I place an order I get to the final checkout but get an internal server error.

Link to a page where the issue can be seen: hidden link

I expected to see:

Instead, I got:

#2554555

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hey there,

Thanks for your contact, and welcome to the Toolset support forum!

Could you please share more details about how this is related to Toolset? If you deactivate it, is the issue solved?

Keep us posted about it. Thanks!

Regards,
Mateus.

#2556371

Hi Mateus

I will send you the logs that show that Types is creating the issue. If you access the Woocommerce logs then you will see that the errors is created / caused by the types plugin.

I have to trust the Woocommerce error logs.

Will send you the logs in the am. It is late here in South Africa. Portion of the checkout purchase process is affected by Types.

Kind regards
Sean

#2558909

Any Help with this ?

#2558931

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello,

I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://toolset.com/privacy-policy-and-gdpr-compliance/#data-shared-with-our-support
**IMPORTANT**

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link

Please, let me know if you need any additional details. Have a nice day.

#2559635

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi there,

Thank you for providing the website credentials, but it seems that the wp-admin dsahboard is crashed? hidden link

Also, we're unable to reproduce the issue on the checkout page. We added a product, went to cart -> checkout and it worked fine: hidden link

At last, about this:

I will send you the logs that show that Types is creating the issue. If you access the Woocommerce logs then you will see that the errors is created / caused by the types plugin.

Were you able to get the logs? If yes, please share them with us.

Looking forward to your reply. Thanks!

#2560243

The crash was caused by Toolset... Please find attached LOG :

Howdy!

Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

In this case, WordPress caught an error with one of your plugins, Toolset Types.

First, visit your website (hidden link) and check for any visible issues. Next, visit the page where the error was caught (hidden link) and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

hidden link

To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.1.1
Active theme: OceanWP (version 3.4.1)
Current plugin: Toolset Types (version 3.4.17) PHP version 8.1.15

Error Details
=============
An error of type E_ERROR was caused in line 125 of the file /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/field/mapper/abstract.php. Error message: Uncaught TypeError: Cannot access offset of type string on string in /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/field/mapper/abstract.php:125
Stack trace:
#0 /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/field/type/select/mapper/legacy.php(45): Types_Field_Mapper_Abstract->apply_options_filter(Array, Array)
#1 /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/field/service.php(54): Types_Field_Type_Select_Mapper_Legacy->find_by_id('tournament', 6125)
#2 /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/field/group/mapper/legacy.php(55): Types_Field_Service->get_field(Object(Types_Field_Gateway_Wordpress_Post), 'tournament', 6125)
#3 /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/post/builder.php(36): Types_Field_Group_Mapper_Legacy->find_by_post(Object(WP_Post), 9999)
#4 /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/models/post/deletion.php(38): Types_Post_Builder->load_assigned_field_groups(9999)
#5 /usr/www/users/sauwhqrwrm/wp-content/plugins/types/application/controllers/m2m.php(137): Types_Post_Deletion->before_delete_post('6125')
#6 /usr/www/users/sauwhqrwrm/wp-includes/class-wp-hook.php(310): Types_M2M::{closure}('6125')
#7 /usr/www/users/sauwhqrwrm/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#8 /usr/www/users/sauwhqrwrm/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#9 /usr/www/users/sauwhqrwrm/wp-includes/post.php(3407): do_action('before_delete_p...', '6125', Object(WP_Post))
#10 /usr/www/users/sauwhqrwrm/wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/classes/CRED_Helper.php(2591): wp_delete_post('6125', true)
#11 /usr/www/users/sauwhqrwrm/wp-content/plugins/cred-frontend-editor/library/toolset/cred/embedded/classes/CRED.php(120): CRED_Helper::clearCREDAutoDrafts()
#12 /usr/www/users/sauwhqrwrm/wp-includes/class-wp-hook.php(308): CRED_CRED::_admin_init_('')
#13 /usr/www/users/sauwhqrwrm/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#14 /usr/www/users/sauwhqrwrm/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#15 /usr/www/users/sauwhqrwrm/wp-admin/admin.php(175): do_action('admin_init')
#16 /usr/www/users/sauwhqrwrm/wp-admin/index.php(10): require_once('/usr/www/users/...')
#17 {main}
thrown

#2560937

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi there,

Thank you for sharing the logs.

We're still debugging this issue, and as soon as possible we'll provide you with updates. Please stay tuned.

Thanks,
Mateus.

#2561071

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hi there,

Upon further inspection, we have concluded that the issue does not seem related to Toolset. For instance, if you deactivate all the seven Toolset plugins, the issue still exists - so it is very unlikely to be related to our plugins.

Moreover, here are the logs that were generated when reproducing the issue: https://pastebin.com/ZQ86bFsU

As we can see, the error is coming from the 'subscription-for-woocommerce' plugin. Therefore, what we can recommend is that you get in touch with their support team and address the issue with them.

Thanks for your understanding!