Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor sermitr

    (@sermitr)

    Hello.

    Our data indicates that your site has WP-Cron deactivated by defining the constant DISABLE_WP_CRON. The constant is usually defined in the file wp-config.php. It can also be disabled by hosting provider, so you might reach out to them about it.

    If WP-Cron is disabled, there should be an external scheduler (e.g. Cron) running for WordPress to function properly, otherwise scheduled events will not be executed. The issue is not Jetpack-specific and is likely to affect other plugins or even WordPress itself.

    More on WP-Cron here: https://developer.wordpress.org/plugins/cron/

    Please let us know if you get any further questions.

    Plugin Contributor sermitr

    (@sermitr)

    Hello @crisdb

    1. Activate Jetpack and configure it with default modules (Security, Performance, Anti-spam).
    2. Use the Masterstudy registration form (built into the theme).
    3. Try to register a new user from the frontend form.

    Unfortunately I wasn’t able to reproduce the problem by following these instructions.

    Testing it on your site, I see that there’s an error returned (but not displayed) by the registration form:
    {"errors":[{"id":"required","field":null,"text":"Il campo \u00e8 obbligatorio"}],"status":"error"}

    The error is a translation of the Field is required error, which is triggered in the file masterstudy-lms-learning-management-system/_core/lms/classes/user.php. It is not triggered by Jetpack itself.

    However, there does seem to be a plugin conflict. If possible, please provide more detailed instructions to reproduce it, and we’ll try to debug the problem.

    It might also help to ask the MasterStudy developers for additional details on the “The third party plugin is blocking cookies.” issue they mentioned.

    If there was a widespread cookie issue caused by Jetpack, we would see it with other plugins or even WordPress itself. It appears to be a conflict with this specific plugin, and we would appreciate any pointers that would help us get it resolved.

    Plugin Contributor sermitr

    (@sermitr)

    Hello @edent.

    Thanks for bringing it up. We’ll give it a closer look and see if this is something we could optimize.

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