• Resolved Motoristi

    (@motoristi)


    Hi again,

    While testing in my sandbox I managed to get the S3 Importer stuck. It displays the message “S3 importer is currently running. Importing 1 of 40.” with a progress bar and has done so for a day regardless of attempts to disable, uninstall, reinstall or even roll-back versions.

    The second issue is that nothing gets uploaded to S3 anymore. Every image shows the following on top of the image in the list and in the editor: “Warning: Illegal offset type in isset or empty in C:\xampp\htdocs\fi\wp-content\plugins\ilab-media-tools\classes\tools\s3\ilab-media-s3-tool.php on line 1020”

    Also in editor the S3 Info widget area shows this:
    “Not uploaded to S3.
    Bucket:
    Warning: Illegal string offset ‘s3’ in C:\xampp\htdocs\fi\wp-content\plugins\ilab-media-tools\classes\tools\s3\ilab-media-s3-tool.php on line 332

    Warning: Illegal string offset ‘bucket’ in C:\xampp\htdocs\fi\wp-content\plugins\ilab-media-tools\classes\tools\s3\ilab-media-s3-tool.php on line 332
    Path:
    Warning: Illegal string offset ‘s3’ in C:\xampp\htdocs\fi\wp-content\plugins\ilab-media-tools\classes\tools\s3\ilab-media-s3-tool.php on line 335

    Warning: Illegal string offset ‘key’ in C:\xampp\htdocs\fi\wp-content\plugins\ilab-media-tools\classes\tools\s3\ilab-media-s3-tool.php on line 335”

    The situation persists with both the latest version of 1.4.8 and the first one I have tested 1.4.6. This renders all my subsequent testing impossible until resolved.

    Please advise on how I can reset the plugin.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author interfacelab

    (@interfacelab)

    What version of PHP are you using?

    Thread Starter Motoristi

    (@motoristi)

    My sandbox is using PHP 7.1.8 because my web hosting will upgrade to PHP 7 in a few months.

    Additional information:

    Uploading a new image gets instantly sent to S3. The warning ontop of the image is on that one too but the S3 Info widget is clear and shows the S3 path.

    Then …

    I reset the importer by removing the options for it from the wp_options table.
    I disabled the S3 tool (as instructed in the importer page).
    Then started the importer to send the local only files to S3 and it sticks to 1 again with nothing new showing up in the bucket.

    Just to add to this conversation

    I’m also getting the same problem as Motoristi
    Identical situation (plugin uploading 1 file )

    using PHP 7.0.22 if it helps

    Plugin Author interfacelab

    (@interfacelab)

    @motoristi

    I just uploaded 1.4.9 – it might help you out. Let me know how it goes.

    Thanks,

    Jon.

    Thread Starter Motoristi

    (@motoristi)

    Hi Jon,

    Thank you for responding so quickly with new versions.

    Sorry for my delay. Took a while before I had the opportunity to test further. Version 1.4.9 removed all warnings in my PHP7 sandbox WP but did not help the importer.

    This evening I installed your new version 1.5.0 to both my Windows XAMPP sandbox and to a test WP on my current web host (running PHP5 ontop of *nix).

    The importer worked like a charm on the *nix PHP5 test WP … but even the new “Import stuck? Force it to cancel.” does not resolve the importer issue in the WinXAMPP sandbox. The text on the importer changes to “Cancelling … This may take a minute …” but you could wait an hour for all the good it does.

    So currently I can’t test with a *nix PHP7 environment that will be on my web hosting service in a few months. However if the importer issue is Windows related then I would assume it works as brilliantly as the rest of the plugin after the web host upgrade.

    Is there any way you could test on a Windows+XAMPP laptop or sorts? I don’t know but I would imagine many others run their test enviroments on a PC even if they have a “real” web host for the actual site(s).

    Thread Starter Motoristi

    (@motoristi)

    Hi Jon,

    Test version installed and test result email sent…

    Plugin Author interfacelab

    (@interfacelab)

    I’ve uploaded a version that allows you to use wp-cli to do the import. You should use that if you are having problems with the importer.

    These are some issues that have been identified with using the importer:

    – Using basic auth on your site
    – Hosting provider can’t resolve your host name
    – Your host has somehow disabled non-blocking curl requests
    – You don’t have the curl extension installed

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Warnings and importer stuck while testing’ is closed to new replies.