Failed at first hurdle

  • Resolved thoughton

    (@thoughton)


    2 years, 9 months ago

    Hi,

    Trying to export a multisite subsite to another subsite on the same multisite.

    I click ‘export blog ID 2’ button, select Export to multisite format, enter blog ID 3, and click ‘Export Now’

    I then get a “0% progress” wheel appears, but it never changes. I’ve waited half an hour and it is still at 0%. If I refresh the page it just disappears.

    I enabled debugging and my debug log contains this:

    [24-Feb-2022 11:06:46 UTC] PHP Warning:  is_readable(): open_basedir restriction in effect. File(/theme.json) is not within the allowed path(s): (/var/www/vhosts/devonepoll.com/:/tmp/) in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-includes/class-wp-theme-json-resolver.php on line 353
[24-Feb-2022 11:06:46 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/functions.php) is not within the allowed path(s): (/var/www/vhosts/devonepoll.com/:/tmp/) in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-settings.php on line 545
[24-Feb-2022 11:06:46 UTC] PHP Notice:  Constant CONCATENATE_SCRIPTS already defined in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-config.php on line 131
[24-Feb-2022 11:06:54 UTC] PHP Warning:  is_readable(): open_basedir restriction in effect. File(/theme.json) is not within the allowed path(s): (/var/www/vhosts/devonepoll.com/:/tmp/) in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-includes/class-wp-theme-json-resolver.php on line 353
[24-Feb-2022 11:06:54 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/functions.php) is not within the allowed path(s): (/var/www/vhosts/devonepoll.com/:/tmp/) in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-settings.php on line 545
[24-Feb-2022 11:06:54 UTC] PHP Notice:  Constant CONCATENATE_SCRIPTS already defined in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-config.php on line 131
[24-Feb-2022 11:06:55 UTC] PHP Warning:  Cannot modify header information - headers already sent in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-content/plugins/uncode-privacy/includes/class-uncode-toolkit-privacy-public.php on line 99
[24-Feb-2022 11:06:55 UTC] PHP Notice:  Constant CONCATENATE_SCRIPTS already defined in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-config.php on line 131
[24-Feb-2022 11:07:00 UTC] PHP Notice:  Constant CONCATENATE_SCRIPTS already defined in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-config.php on line 131
[24-Feb-2022 11:07:01 UTC] PHP Deprecated:  contextual_help is <strong>deprecated</strong> since version 3.3.0! Use get_current_screen()->add_help_tab(), get_current_screen()->remove_help_tab() instead. in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-includes/functions.php on line 5586
[24-Feb-2022 11:07:14 UTC] PHP Warning:  is_readable(): open_basedir restriction in effect. File(/theme.json) is not within the allowed path(s): (/var/www/vhosts/devonepoll.com/:/tmp/) in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-includes/class-wp-theme-json-resolver.php on line 353
[24-Feb-2022 11:07:14 UTC] PHP Warning:  file_exists(): open_basedir restriction in effect. File(/functions.php) is not within the allowed path(s): (/var/www/vhosts/devonepoll.com/:/tmp/) in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-settings.php on line 545
[24-Feb-2022 11:07:14 UTC] PHP Notice:  Constant CONCATENATE_SCRIPTS already defined in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-config.php on line 131
[24-Feb-2022 11:07:15 UTC] PHP Warning:  Cannot modify header information - headers already sent in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-content/plugins/uncode-privacy/includes/class-uncode-toolkit-privacy-public.php on line 99
[24-Feb-2022 11:07:16 UTC] PHP Notice:  Constant CONCATENATE_SCRIPTS already defined in /var/www/vhosts/devonepoll.com/httpdocs/_wp/wp-config.php on line 131
    • This topic was modified 2 years, 9 months ago by thoughton.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Codexonics

    (@codexonics)

    Hi thoughton,
    Thanks for using Prime Mover and sorry to hear you have issues. First, looking at the errors – it does not look to be migration related. I think has something to do with user authorization, cache related, or server permissions. But there is no specific details in the error that relates to a Prime Mover process.
    Can you please do the following quick troubleshooting first so we can isolate the issues and get more details:

    • Clear your browser cache.
    • Login to your network admin.
    • Make sure you are using the latest version of Prime Mover plugin (currently version 1.4.9)
    • If you are exporting a subsite – check the subsite front end – does it display correctly? If there are errors or white screen – you need to resolve this before exporting the site.
    • Please check the subsite admin dashboard – can you access it? Make sure it does not have white screen or fatal errors.
    • Confirm if the subsite to be exported is in multisite – go to subsite admin -> Tools -> Sitehealth -> click “Info” tab -> Scroll below and look for “WordPress” section -> Click on it and look for “Is this a multisite?” – it should be “Yes”.
    • Finally follow these steps to reproduce the issue and submit migration/debug logs to our support. Follow these steps under Prime Mover Free version.

      Basically the steps will require you to enable WordPress debug (if not enabled) and then reproduce the error.

    • If the error is still reproducible – please get the migration logs/debug.log generated and check the browser for console errors also (if there is).
    • You can send to us all the logs via our contact page.

    Thanks again! Cheers.

    Thread Starter thoughton

    (@thoughton)

    Thanks for the reply, fixed it now.

    It was the console errors that showed the problem. It was a CORS issue due to a www/no-www siteurl conflict.

    Thanks again!

    • This reply was modified 2 years, 9 months ago by thoughton.
    • This reply was modified 2 years, 9 months ago by thoughton.
Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Failed at first hurdle’ is closed to new replies.