Skip Navigation

[Resolved] Adding View to Page Causes Fatal Error in WordPress

This support ticket is created 4 years, 1 month 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 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by aaronM-9 4 years, 1 month ago.

Assisted by: Shane.

Author
Posts
#1560297

I just tried creating a page called "Browse Products" that simply embeds a View called "View-Products-Brand". However, when publishing the page it throws a fatal error. Here is the shortcode (the entire body content of the page):

[wpv-view name="view-products-brand"]

When I remove the shortcode from the page the error does not occur. Below please find the e-mail automatically generated by WordPress. Thanks for any help.

-------------------------------------

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.

**link omitted**

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 5.3.2
Current theme: Astra (version 2.3.4)
Current plugin: Toolset Types (version 3.3.10)
PHP version 7.0.33

Error Details
=============
An error of type E_ERROR was caused in line 91 of the file /home/croydoncoop/public_html/wp-content/plugins/types/vendor/toolset/types/embedded/classes/loader.php. Error message: Allowed memory size of 268435456 bytes exhausted (tried to allocate 20480 bytes)

#1560567

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Aaron,

Thank you getting in touch.

Based on the error here it seems that your wordpress instance is running out of memory.

What I would recommend that you do is to increase your wordpress memory limit and try again.

To do this please follow the instructions in the link below.
hidden link

Thanks,
Shane

#1561613

The View had a filter that used a shortcode attribute but I was not passing the shortcode attribute, so it was returning thousands of posts and no pagination (prompting the memory issue).

Once I added the attribute to the Views shortcode, the issue went away.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.