Manual Scheduling an Export

  • Resolved Brian_Milnes

    (@brian_milnes)


    3 years, 11 months ago

    Hi, I am missing something obvious, I’m afraid.

    I am wanting to allow users to download an up-to-date Export from a CPT.

    I have tried the link from the XLSX button, but that doesn’t re-run the export.

    I have tried to find the documentation that explains this, but cannot find it, and don’t understand the options in “manual scheduling”.

    What is the distinction between “Trigger” “Processing” and “File” URLs?

    Do I have to run them in sequence, to get an updated file?

    Thanks and sorry for being a dullard.

    Brian

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter Brian_Milnes

    (@brian_milnes)

    3 years, 11 months ago

    And trying my own suggestion “Processing” relies on “Triggering”, and doing them in order appears to create a new export run.

    But then, downloading the file appears to still get the original file (same name), not a new one…

    Plugin Author WP All Import

    (@wpallimport)

    3 years, 11 months ago

    Hi @brian_milnes

    I have tried to find the documentation that explains this, but cannot find it, and don’t understand the options in “manual scheduling”.

    The information on setting up cron jobs for imports also applies to exports: http://www.wpallimport.com/documentation/recurring/cron/.

    And trying my own suggestion “Processing” relies on “Triggering”, and doing them in order appears to create a new export run.

    That’s correct. The “trigger” script only flags the export as “started”, the “processing” script runs the export.

    But then, downloading the file appears to still get the original file (same name), not a new one…

    You have to run the “processing” script over and over until it completes the export, at which point the new file will be available to download.

    Thread Starter Brian_Milnes

    (@brian_milnes)

    3 years, 11 months ago

    How can this be made automatic? (Without user intervention?)

    Or is the reliant on scheduling, say a daily CRON job?

    Thread Starter Brian_Milnes

    (@brian_milnes)

    3 years, 11 months ago

    On my staging server, re-running the Processing script worked OK until the final iteration, when I get the following error:
    {“status”:403,”message”:”Export #26 is not triggered. Request skipped.”}

    And the xlsx file is not updated

    Thread Starter Brian_Milnes

    (@brian_milnes)

    3 years, 11 months ago

    And now I have increased the “number of records” setting in the export, to 550 (larger than the 490 records to export).
    After doing that, “triggered” and then “processed” results in
    {“status”:200,”message”:”Export #26 complete”}
    message, but
    xlsx file still only contains original 470 records (10 short)

    Thread Starter Brian_Milnes

    (@brian_milnes)

    3 years, 11 months ago

    *20 short (!)

    Plugin Author WP All Import

    (@wpallimport)

    3 years, 11 months ago

    Hi @brian_milnes

    How can this be made automatic? (Without user intervention?) Or is the reliant on scheduling, say a daily CRON job?

    The cron jobs on your server would automatically run it.

    I get the following error: {“status”:403,”message”:”Export #26 is not triggered. Request skipped.”}

    This isn’t an error, it means the export is complete and hasn’t been triggered (started) yet.

    xlsx file still only contains original 470 records (10 short)

    It sounds like your server is caching the file. Please try installing the latest BETA version of WP All Export (free version available here: https://downloads.wordpress.org/plugin/wp-all-export.zip). Once that’s installed, add the following code to your child themes functions.php file:

    add_filter( 'wp_all_export_no_cache', 'my_no_cache', 10, 1 );
function my_no_cache( $cache ) {
	return TRUE;
}

    This should force WP All Export to bypass the cache on your server.

    Plugin Author WP All Import

    (@wpallimport)

    3 years, 11 months ago

    Hi @brian_milnes

    I’m going to mark this as resolved since we have not heard back. Let me know if you still have questions about this. Anyone else, please start a new ticket.

    Thread Starter Brian_Milnes

    (@brian_milnes)

    3 years, 11 months ago

    Yes thanks, we’ve written small bit of code to await the return code and then write out the spreadsheet.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Manual Scheduling an Export’ is closed to new replies.