Can't use Facebook Events to upload events

Home Forums Calendar Products Event Aggregator Can't use Facebook Events to upload events

Viewing 11 posts - 1 through 11 (of 11 total)
  • Author
    Posts
  • #1037952
    John
    Participant

    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?

    #1038016
    John
    Participant

    I have upgraded all Events to 4.0 and am still having this problem

    #1038295
    Geoff
    Member

    Hi 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

    #1039304
    John
    Participant

    My 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.

    #1039305
    John
    Participant

    ned 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 436

    Notice: 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
    437

    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: 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 82

    Warning: 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 65

    #1039311
    John
    Participant

    Extra 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

    #1039644
    Geoff
    Member

    Hi 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

    #1042333
    John
    Participant

    Hi 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.
    #1042397
    Geoff
    Member

    Hi 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!
    Geoff

    #1042621
    John
    Participant

    The 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

    #1042980
    Geoff
    Member

    Phew! 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

Viewing 11 posts - 1 through 11 (of 11 total)
  • The topic ‘Can't use Facebook Events to upload events’ is closed to new replies.