Memory issue on "Submit an event"

[Benny]

Hi there,

I get a Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 615 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 1045

… when I click on Submit an event (/events/community/add) even though it looks like there’s plenty of memory on the server. I have other websites that generate quite a bit of traffic and never have any problems.

Any suggestions?

Thanks,

[Victor]

Hi Benny!

Thanks for reaching out to us! Let me help you with that issue.

Are you getting this error anywhere else in your site or just in that page?

Could you please enable WP_DEBUG and WP_DEBUG_LOG ? This will create a debug.log file inside the /wp-content directory. After that, try navigating a few times into the add page where you are having the issue, so that in case there is another error we are not seeing, it will be saved into the debug.log file. Please share that log file with us so we can spot the problem from there.

I can see from your system settings that you have WP_MEMORY_LIMIT set to 768M. Could you please try raising the memory limit for your WordPress installation and see if you still get the error? You can learn how to do that here > https://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP

Let me know how it goes.

Thanks,
Victor

[Benny]

Hi Victor,

It only happens on that very specific page.
Here’s the log:

[18-Aug-2017 01:16:30 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 01:21:43 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 01:22:40 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 01:22:50 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 02:49:48 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 02:49:49 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 03:28:14 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 03:28:38 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[18-Aug-2017 18:11:08 UTC] PHP Fatal error: Call to a member function get() on null in /home/dreamin7/public_html/wod/wp-content/themes/yootheme/footer.php on line 10
[21-Aug-2017 16:41:50 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 876 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 1045
[21-Aug-2017 16:46:33 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 72 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 626
[21-Aug-2017 17:14:11 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 72 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 1045
[22-Aug-2017 00:26:53 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 615 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 1045
[22-Aug-2017 16:57:25 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 130968 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 3248
[22-Aug-2017 16:57:46 UTC] WordPress database error Unknown column ‘wpxv_postmeta.meta_value’ in ‘field list’ for query SELECT SQL_CALC_FOUND_ROWS DISTINCT wpxv_posts.*, IF (wpxv_posts.post_type = ‘tribe_events’, wpxv_postmeta.meta_value, wpxv_posts.post_date) AS post_date FROM wpxv_posts WHERE 1=1 AND 0 ORDER BY wpxv_posts.post_date DESC LIMIT 0, 5 made by require(‘wp-blog-header.php’), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts
[23-Aug-2017 00:28:36 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 130968 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 3248
[23-Aug-2017 03:01:52 UTC] WordPress database error Unknown column ‘wpxv_postmeta.meta_value’ in ‘field list’ for query SELECT SQL_CALC_FOUND_ROWS DISTINCT wpxv_posts.*, IF (wpxv_posts.post_type = ‘tribe_events’, wpxv_postmeta.meta_value, wpxv_posts.post_date) AS post_date FROM wpxv_posts WHERE 1=1 AND 0 ORDER BY wpxv_posts.post_date DESC LIMIT 0, 5 made by require(‘wp-blog-header.php’), wp, WP->main, WP->query_posts, WP_Query->query, WP_Query->get_posts
[23-Aug-2017 04:14:19 UTC] PHP Fatal error: Allowed memory size of 805306368 bytes exhausted (tried to allocate 130968 bytes) in /home/dreamin7/public_html/wod/wp-includes/class-wp-query.php on line 3248

[Victor]

Hi Benny!

Thanks for coming back with the error logs.

I can’t relate any of the error logs being something directly coming from our plugins.

Are you making any template customization for any of the community add form templates?

Just to make sure there is no plugin or theme conflict, could you please go through the steps in our testing for conflicts guide and see if you still get the error? Please start by switching to a default theme like twenty seventeen.

If that doesn’t clear the error, then proceed by deactivating the plugins one at a time to see if any changes.

If you see no difference when testing for conflicts, we’ll have to make some deeper troubleshooting.

Let us know how that goes.

Thanks,
Victor

[Benny]

Thanks Victor, you were right… Interestingly enough, switching to another theme and back was enough to fix the issue… And yeah, doesn’t make much sense does it?

Anyways, this is fixed now, onward… 🙂

[Victor]

Hi Benny!

Glad to know you could solve the issue! Thanks for following up to let us know about it.

I’ll go ahead and close this, but feel free to open a new topic if anything comes up and we’d be happy to help!

Cheers,
Victor

[Author]

Posts