Home › Forums › Calendar Products › Event Aggregator › Can't use Facebook Events to upload events
- This topic has 10 replies, 2 voices, and was last updated 8 years, 3 months ago by Geoff.
-
AuthorPosts
-
December 8, 2015 at 8:11 pm #1037952JohnParticipant
When I try to update the daily automatic updates on my Calendar I get this message
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 36206193 bytes) in /home/todev/public_html/wp-includes/wp-db.php on line 1094
Any ideas please?
December 9, 2015 at 2:05 am #1038016JohnParticipantI have upgraded all Events to 4.0 and am still having this problem
December 9, 2015 at 7:51 am #1038295GeoffMemberHi John, and sorry for the issue!
That message means that the server itself has run out of memory and needs more to run tasks. There are some ways to increase memory manually and those are outlined nicely in this post. However, if none of those work, you will want to reach out directly to your host for additional support to increase that limit.
Sorry again for the trouble, but I do hope this gets things started in the right direction!
Geoff
December 10, 2015 at 5:35 pm #1039304JohnParticipantMy host as raised all limits as suggested her response,
I increased memory limit to 196mb in wp-config.php but no luck.
Enabled debug mode and it shows these warnings.
Please try to disable the “music-store” plugin and try again.
If it still fails please send this output to the plugin developer(facebook
import) Tell them that the server wide memory limit is 1024mb.Music store is deactivated and I am STILL getting these warnings eh.
December 10, 2015 at 5:36 pm #1039305JohnParticipantned constant MS_ASK_COOKIE_PERMISSIONS – assumed ‘MS_ASK_COOKIE_PERMISSIONS’
in /home/todev/public_html/wp-content/plugins/music-store/music-store.php on
line 436Notice: Use of undefined constant MS_ASK_COOKIE_PERMISSIONS_TEXT – assumed
‘MS_ASK_COOKIE_PERMISSIONS_TEXT’ in
/home/todev/public_html/wp-content/plugins/music-store/music-store.php on line
437Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: The called constructor method for WP_Widget is deprecated since
version 4.3.0! Use__construct()
instead. in /home/todev/public_html/wp-includes/functions.php on line 3619
Notice: Constant WP_MEMORY_LIMIT already defined in
/home/todev/public_html/wp-config.php on line 82Warning: Cannot modify header information – headers already sent by (output
started at
/home/todev/public_html/wp-content/plugins/music-store/music-store.php:436) in
/home/todev/public_html/wp-content/plugins/nextgen-gallery/products/photocrati_nextgen/modules/frame_communication/package.module.frame_communication.php
on line 65December 10, 2015 at 6:15 pm #1039311JohnParticipantExtra wrinkle, I am getting this warning even when I try to upload a post
Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 38343581 bytes) in /home/todev/public_html/wp-includes/wp-db.php on line 1129
December 11, 2015 at 7:45 am #1039644GeoffMemberHi John,
It’s good that your host was able to increase memory–thanks for doing that!
The fact that we’re seeing so many new notices now in place of the memory limit points to the possibility of a conflict, perhaps with another installed plugin. Will you please run through the steps outlined in this article? It will help us identify what conflict we’re looking at–if any–and how to proceed from there.
Please let me know what you find from that test!
Geoff
December 16, 2015 at 8:18 am #1042333JohnParticipantHi Geoff,
I did all that and it seems that the events ARE uploading, but the error is still occurring and their check boxes on refrsh still appear unchecked…hmmmm.
I am about to go through the process of re installing plugins and will tell you when I hit the problem, from what I can see it has something to do with the choice to auto publish Facebook events.
The following errors have occurred:
Event ID “779069762204878” was already imported from Facebook.
Event ID “988038627928058” was already imported from Facebook.
Event ID “1534822720173141” was already imported from Facebook.
Event ID “185023875182680” was already imported from Facebook.
Event ID “225500947781665” was already imported from Facebook.
Event ID “1006017092796505” was already imported from Facebook.
Event ID “102455140129178” was already imported from Facebook.
Please note that as a result, no events were successfully imported.- This reply was modified 8 years, 3 months ago by John.
December 16, 2015 at 10:53 am #1042397GeoffMemberHi John,
Thanks and please do keep me posted.
It is possible that Facebook Events is storing those events in the database to prevent them from being re-imported a second time. Once you import an event via Facebook Events the system stores a “note” so that deleted events are not re-imported (as this would be the desired behavior for most cases and for automatic imports as well).
To delete saved deleted events notes add this snippet to your theme functions.php file and re-load the import page (it will run once per page-load) until the message is shown, after that remove snippet:
/* Deletes 50 posts per page load*/ $posts = get_posts( array( 'numberposts' => 50, 'post_type' =>'deleted_event') ); if (!empty($posts)) { foreach ($posts as $post) { wp_delete_post( $post->ID, true); } } else { echo 'Done deleting!'; }
Cheers!
GeoffDecember 16, 2015 at 8:41 pm #1042621JohnParticipantThe conflict appears to have been with the User Pro plugin. After turning it off and on again our Facebook Importer seems to be working fine. Might have been an allowable file size limit in User Pro
December 17, 2015 at 8:36 am #1042980GeoffMemberPhew! That’s great to hear and nice work finding the conflict.
Let us know if any other questions or issues pop up–we’d be happy to help. 🙂
Geoff
-
AuthorPosts
- The topic ‘Can't use Facebook Events to upload events’ is closed to new replies.