Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QM Drop-in issue with WP All Import plugin #847

Open
shivapoudel opened this issue Jan 25, 2024 · 3 comments
Open

QM Drop-in issue with WP All Import plugin #847

shivapoudel opened this issue Jan 25, 2024 · 3 comments

Comments

@shivapoudel
Copy link

shivapoudel commented Jan 25, 2024

Let's replicate the bug.

  1. Create a sandbox environment for testing over here: https://www.wpallimport.com/debug/
  2. Go to the "All Import > New Import" page.
  3. Upload the "sample.csv" file and select Create new "WooCommerce Products".
  4. Continue to step 2 and again to step 3.
  5. Just drag the "product_name" as a title for testing.
  6. Continue to step 4 and the issue arises within "admin.php?page=pmxi-admin-import&action=options"
  7. Hurray the issue arrived!

Please note: db.php drop-in symlink file of Query monitor should reside in a wp-content directory to receive the bug. Hence similar approach to local development should be made in a local environment. Use this plugin to download wp all importer plugin from debug site for local environment: https://wordpress.org/plugins/wp-anything-downloader/

[25-Jan-2024 05:46:53 UTC] PHP Fatal error: Uncaught Exception: Serialization of 'Closure' is not allowed in D:\htdocs\shop-eachperson\app\public\wp-includes\functions.php:625
Stack trace:
#0 D:\htdocs\shop-eachperson\app\public\wp-includes\functions.php(625): serialize(Object(PMXI_Import_Record))
#1 D:\htdocs\shop-eachperson\app\public\wp-content\plugins\wp-all-import-pro\classes\session.php(83): maybe_serialize(Object(PMXI_Import_Record))
#2 D:\htdocs\shop-eachperson\app\public\wp-content\plugins\wp-all-import-pro\controllers\admin\import.php(1845): PMXI_Session->set('import', Object(PMXI_Import_Record))
#3 D:\htdocs\shop-eachperson\app\public\wp-content\plugins\wp-all-import-pro\wp-all-import-pro.php(773): PMXI_Admin_Import->options()
#4 D:\htdocs\shop-eachperson\app\public\wp-includes\class-wp-hook.php(324): PMXI_Plugin->adminInit('')
#5 D:\htdocs\shop-eachperson\app\public\wp-includes\class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)
#6 D:\htdocs\shop-eachperson\app\public\wp-includes\plugin.php(517): WP_Hook->do_action(Array)
#7 D:\htdocs\shop-eachperson\app\public\wp-admin\admin.php(175): do_action('admin_init')
#8 {main}
thrown in D:\htdocs\shop-eachperson\app\public\wp-includes\functions.php on line 625
@johnbillion
Copy link
Owner

Thanks for the report Shiva!

I can't see anything in the stack trace that's specific to Query Monitor. Can you provide some more info please?

@shivapoudel
Copy link
Author

shivapoudel commented Jan 25, 2024

@johnbillion Please install these WP All Import plugins and Query Monitor with drop-in db.php enabled:

Now follow these steps to replicate the bug within WP All Importer:

  • Go to the "All Import > New Import" page.
  • Upload the "sample_products.csv" file and select Create new "WooCommerce Products".
  • Continue to Step 2 and again click on Continue to Step 3.
  • Just drag the "name" as a title for testing.
  • Continue to Step 4 and the issue arises.

image

When I remove the db.php drop-in everything works perfectly. Thinking so I contacted first to the WP All Import team but they said it's a known issue and I can report it here. Please lemme know if you need help replicating the issue.

@shivapoudel
Copy link
Author

shivapoudel commented Jan 26, 2024

@johnbillion Just a follow-up! Did you replicate the issue as bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants