• Resolved krzxsiek

    (@krzxsiek)


    The plugin causes a conflict and an error “Unable to initialize WP_Filesystem” when we have define('FS_METHOD', 'ftpext');
    set in the wp-config.php file.
    I consider this a bug that needs to be fixed immediately because some people, like me, value security and the “ftpext” mode instead of “direct”.
    Please fix it. Best regards

    WordPress 6.7.2
    PHP 8.3.9 (Tested from 8.1 upwards)

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    Hello @krzxsiek,

    Did you also open a ticket in our ticket system (ticket #4371)? I tried to reach out to you there and even sent a reminder, but my replies don’t seem to come through. Apologies for that! We can continue working on the issue here using this topic.

    Regarding your question, using WP_Filesystem for file management in a WordPress plugin is considered best practice, so the error message you’re seeing is not exactly a bug. The message acts as a safeguard to prevent fatal errors when WP_Filesystem is not initialized.

    Using WP_Filesystem is required — and the safest way — to enable the plugin to write feeds and backup files. I don’t think there is a way around that, but I will investigate if there’s an alternative solution.

    You mentioned that the plugin causes a conflict. Could you please share more details on what exactly the conflict is? This will help me get a better picture of the issue.

    Looking forward to your reply, and in the meantime I will investigate any solutions.

    Best regards,
    Michel

    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    Hello @krzxsiek,

    I’ve investigated the issue further. You can disregard my request for more information about the conflict.

    For now, you can revert back to a previous version of our plugin while I work on finding a solution. You can download version 3.11.0 by visiting our website at wpmarketingrobot.com, opening the Your account page, and navigating to the Downloads tab. There, you’ll find the 3.11.0 version available for download.

    To install the 3.11.0 version on your server, please follow these steps:

    1. Download the 3.11.0 version from the Downloads tab on your account page.
    2. Deactivate (but do not delete) the current WooCommerce Product Feed Manager plugin on your Plugins page.
    3. Go to your server file manager and navigate to the wp-content/plugins folder.
    4. Delete the wp-product-feed-manager folder.
    5. Upload the contents of the downloaded .zip file to the wp-content/plugins folder.
    6. Reactivate the WooCommerce Product Feed Manager plugin on your Plugins page.

    Let me know if this helps or if you need any further assistance. I will report back when I have a definite solution for the issue.

    Best regards,
    Michel

    Thread Starter krzxsiek

    (@krzxsiek)

    Thank you for your answer. I will upload the previous version of the plugin in a moment.
    And returning to the conflict, I also have a problem with the Contact Form 7 plugin which prevents sending emails from the form. The problem also disappears when I change “ftpext” to “direct” so I suspect that they are related.

    I apologize if what I write is incomprehensible, but I write through a translator.

    Thread Starter krzxsiek

    (@krzxsiek)

    Only you seem to be writing about some premium version of this plugin and I don’t have the premium version ??
    I have version 2.13.0 installed on my site and it’s this that creates the conflict.

    • This reply was modified 3 weeks, 2 days ago by krzxsiek.
    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    OK, I hadn’t noticed that, sorry for the misunderstanding. But I know the issue is also active on the Premium version of our plugin, so we need to fix it anyway.

    But in your case, if you’re using a free version, you can download version 2.11.2 from this link: https://www.ads-software.com/plugins/wp-product-feed-manager/advanced/. At the bottom of the page you can download version 2.11.2. The rest of the procedure is the same as mentioned above.

    Thread Starter krzxsiek

    (@krzxsiek)

    Thanks for your help, but after talking to my coworkers it turned out that we don’t need this plugin and I can just disable it.

    So sorry for the confusion, but I hope this post will help someone else ??

    Plugin Contributor Michel Jongbloed

    (@michel-jongbloed)

    OK, no problem @krzxsiek, thanks for letting me know. I will still investigate the issue and try to fix it, but I will close your topic then. And I will also close your ticket #4371 in our ticket system.

    Have a great day.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.