Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • @ekamran The plugin only does that once upon activation since version 4. We didn’t want to attempt to create it on every request because it’s not critical for the plugin to work properly. We will create loaders for everyone in one of the future versions, but you shouldn’t notice any difference.

    Version 4 came out in January this year, were you perhaps using the ManageWP Worker before that?

    Hey Jasper,
    “ManageWP – Worker Loader” is an automatically generated “must use” WordPress plugin that enables ManageWP Worker to load early, for performance and reliability reasons. The loader is automatically removed upon main plugin deactivation.

    It shouldn’t require any action from you, and the main plugin will work perfectly fine without it. Where exactly did you get that prompt?

    Thread Starter Milos Colakovic

    (@briareos)

    Thanks for the response, James.

    Does that mean there is no centralized way to access the official localized files only but to extract the official .zip files? The sr_RS (Serbian) localized files for instance are accessible via SVN, which is great, but ar (Arabic) aren’t, so I assume those are managed separately. Does that mean that the translation teams themselves build the .zip files?

    Hi Sylvain,

    There was indeed a bug on our side, and we just pushed a fix. Thank you for notifying us ??
    The conflict shouldn’t happen anymore, but we would like to check if everything is working as it should, so we didn’t increment the version number yet. Could you advise your clients to re-download the latest ManageWP Worker plugin version if the conflict happens to them?

    Hi,

    For us to include pluggable.php two conditions must be met:
    1. The HTTP request must be sent explicitly from https://managewp.com. That means it should never be included in regular requests, while ManageWP Worker is active in the background.
    2. The request must be related to backup/restore functinality. Other actions are executed on init hook with the priority of 9999.

    In those cases, the request is handled by the plugin, and it is terminated after sending the response to ManageWP.

    However, if you have noticed a case in which the ManageWP Worker plugin includes pluggable.php in a case not described above, that is definitely not intended. Do you by any chance have error logs related to redefinition of the wp_mail function?

    Best regards,
    Milos Colakovic

    Hy Sylvain,

    I’m Milos, a ManageWP developer.
    This functionality is there only for select few cases – specifically when using ManageWP backup and restore functionality, which is functional even if the WordPress installation gets broken due to a theme or plugin update, and you want to restore your website to a previous state. It is never used in normal requests.

    Please tell me if you have any further inquiries.

    Best regards,
    Milos Colakovic

Viewing 6 replies - 1 through 6 (of 6 total)