fatal error emai-piping

  • Resolved Sergio Alfaro

    (@rafasshop)


    10 months, 3 weeks ago

    Hi!

    I tried to place a ticket in your website, but it’s stuck after click in the button to send it. I tried different days from differents browsers.

    I sent you an email to your support email, and I don’t received any reply and the ticket is no appears in your control panel.

    So I am asking here:

    I have two websites using your plugin, and executing the wordpres cron by ssh I found this error:

    thrown in /home/domain/htdocs/domain.com/wp-content/plugins/wpsc-email-piping/asset/lib/php-imap/src/PhpImap/Mailbox.php on line 93
    Fatal error: Uncaught Error: Undefined constant "OP_READONLY" in /home/domain/htdocs/domain.com/wp-content/plugins/wpsc-email-piping/asset/lib/php-imap/src/PhpImap/Mailbox.php:93
    Stack trace: 0 /home/domain/htdocs/domain.com/wp-content/plugins/wpsc-email-piping/includes/class-wpsc-ep-imap-importer.php(48): [constant expression]() 1 /home/domain/htdocs/domain.com/wp-content/plugins/wpsc-email-piping/includes/class-wpsc-ep-cron.php(92): WPSC_EP_IMAP_Importer::import() 2 /home/domain/htdocs/domain.com/wp-includes/class-wp-hook.php(324): WPSC_EP_Cron::import_emails() 3 /home/domain/htdocs/domain.com/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 4 /home/domain/htdocs/domain.com/wp-includes/plugin.php(565): WP_Hook->do_action() 5 phar:///usr/bin/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(343): do_action_ref_array() 6 phar:///usr/bin/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(265): Cron_Event_Command::run_event() 7 [internal function]: Cron_Event_Command->run() 8 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func() 9 [internal function]: WP_CLI\Dispatcher\CommandFactory::{closure:WP_CLI\Dispatcher\CommandFactory::create_subcommand():97}() 10 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(491): call_user_func() 11 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(417): WP_CLI\Dispatcher\Subcommand->invoke() 12 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(440): WP_CLI\Runner->run_command() 13 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1237): WP_CLI\Runner->run_command_and_exit() 14 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start() 15 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(78): WP_CLI\Bootstrap\LaunchRunner->process() 16 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap() 17 phar:///usr/bin/wp/php/boot-phar.php(11): include('…') 18 /usr/bin/wp(4): include('…') 19 {main}

    Please, can you take a look if this is a bug and solve it?

    I am experiencing crons issues and I think that maybe it’s related with this.

    Thank you.

    Best Regards.

    • This topic was modified 10 months, 3 weeks ago by Sergio Alfaro.
Viewing 3 replies - 1 through 3 (of 3 total)
  • miliighe

    (@miliighe)

    10 months, 3 weeks ago

    Hello Sergio,

    Thanks for your patience with the issue. Rest assured, we will help you out with the issue.

    Please try again to raise a support ticket on our support portal.

    Or send email at [email protected]

    Please mention this support thread in the mail or ticket so we can get reference.

    Thank you.

    Thread Starter Sergio Alfaro

    (@rafasshop)

    10 months, 3 weeks ago

    Hello Millind.

    Both things are exactly what I did if you read my message.

    I tried several times to place a ticket in your support portal, from different computers and browsers, incognito mode included.

    I already sent an email to that address 7 days ago and I am still waiting for a reply too

    Please, can you take a look on it?

    Thank you.

    • This reply was modified 10 months, 3 weeks ago by Sergio Alfaro.
    Plugin Author PSM Plugins

    (@psmplugins)

    10 months, 3 weeks ago

    Hello @rafasshop,

    Thank you for reaching out. We apologize for the delay in our response; we discovered that your recent email was incorrectly routed to our spam folder.

    To ensure we can assist you promptly, our team member, @miliighe, has manually created a support ticket on your behalf. You should receive a separate email with the ticket details shortly. We have also added your email address to our trusted contacts to prevent this from happening again.

    We investigated why you might have been unable to create a ticket on our website. The most likely reason for both the website access issue and the email being marked as spam is that your IP address may have been flagged by our security systems. In such cases, our server’s firewall automatically blocks activity to protect our platform.

    If you face this issue again, you could try accessing our website from a different network (e.g., a mobile network instead of Wi-Fi).

    Please rest assured that we are committed to resolving your issue. Our team will follow up with you through the new support ticket.

    Best regards,

    The SupportCandy Team

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

The topic ‘fatal error emai-piping’ is closed to new replies.