• Resolved futureyoon

    (@futureyoon)


    v3.9.1crash with fluentcrm

    i rolled back, didnt manage to capture the error..
    i am running on bitnami

    • This topic was modified 2 years, 7 months ago by futureyoon.
Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Hi @futureyoon , thanks for reporting the issue. Is there any chance you could check the error log and either post related errors here or send us a message on our website? We’ll investigate now as well but most of our team isn’t online for a few hours, so the more information we can collect the better.

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    We were able to confirm an issue with Fluent CRM and PHP 8.0+ with the latest release. We’re preparing an update now that we’ll push shortly.

    Thanks again for alerting us and our apologies for the inconvenience. When the update is available (within the hour) maybe you can test again and confirm it’s resolved.

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    The update has now been released. Please let us know if you still see any issues.

    Thread Starter futureyoon

    (@futureyoon)

    I am still getting a fatal error

    [14-Apr-2022 19:58:05 UTC] PHP Fatal error:  Uncaught Error: Call to undefined method Uncanny_Automator\Fluent_Crm_Helpers::get_custom_field() in /bitnami/wordpress/wp-content/plugins/uncanny-automator/src/integrations/fluent-crm/actions/fcrm-add-contact.php:235
    Stack trace:
    #0 /bitnami/wordpress/wp-content/plugins/uncanny-automator/src/integrations/fluent-crm/actions/fcrm-add-contact.php(42): Uncanny_Automator\FCRM_ADD_CONTACT->get_all_fields()
    #1 /bitnami/wordpress/wp-content/plugins/uncanny-automator/src/integrations/fluent-crm/actions/fcrm-add-contact.php(20): Uncanny_Automator\FCRM_ADD_CONTACT->setup_action()
    #2 /bitnami/wordpress/wp-content/plugins/uncanny-automator/src/core/classes/class-set-up-automator.php(463): Uncanny_Automator\FCRM_ADD_CONTACT->__construct()
    #3 /bitnami/wordpress/wp-content/plugins/uncanny-automator/src/core/classes/class-set-up-automator.php(264): Uncanny_Automator\Set_Up_Automator->initialize_triggers_actions_closures()
    #4 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(307): Uncanny_Automator\Set_Up_Automator->Uncanny_Automator\{closure}()
    #5 /opt/bitnami/wordpress/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
    #6 /opt/bitnami/wordpress/wp-includes/plugin.php(474): WP_Hook->do_action()
    #7 /opt/bitnami/wordpress/wp-settings.php(450): do_action()
    #8 /bitnami/wordpress/wp-config.php(232): require_once('...')
    #9 /opt/bitnami/wordpress/wp-load.php(50): require_once('...')
    #10 /opt/bitnami/wordpress/wp-blog-header.php(13): require_once('...')
    #11 /opt/bitnami/wordpress/index.php(17): require('...')
    #12 {main}
      thrown in /bitnami/wordpress/wp-content/plugins/uncanny-automator/src/integrations/fluent-crm/actions/fcrm-add-contact.php on line 235
    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Hi @futureyoon , this one is a different issue than what we found and fixed last night. It suggests your environment is not seeing a file that definitely exists in the plugin; we haven’t seen other reports either and it seems to be site-specific.

    Our team’s suggestion is that you do the following as a next step:
    1. Downgrade Automator again.
    2. Disable FluentCRM (if you’re using it, can you confirm?).
    3. In the admin bar, use Automator > Flush cache to clear any caching.
    4. Reinstall the latest version of Uncanny Automator (are you doing this from the site UI, FTP or another way?).
    5. Try reenabling FluentCRM if it was previously enabled.

    If none of the above helps and you are using FluentCRM, maybe you can confirm the version that’s active and whether you’re using the Pro plugin for FluentCRM.

    Following that, if we can’t determine the issue, it may help to get more information about the site via the system report (and at that point it’s probably better to move this to our Help Desk).

    Thread Starter futureyoon

    (@futureyoon)

    I think i figured out. it was due to the runner authority between bitnami and daemon.
    you may close the ticket. thx for the quick response!

    Plugin Contributor Uncanny Automator

    (@uncannyautomator)

    Ah, interesting! Thanks for the update and feedback. We’ll go ahead and close the ticket.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘v3.9.1crash with fluentcrm’ is closed to new replies.