futureyoon

Hi,

Thank you for the quick update.
I am running on AWS EC2 so technically I am the one should be stopping it which I tried.

I tried to remove the extension = redis.so from php.ini
and then rebooted the server.

then phpredis in Redis settings change its client to Predis, which I need it to remain as phpredis client for AWS.

and you mention that there is no harm to have it running locally but wouldn’t it consume the resource if it keeps on running?

Anyway, would you be able to tell how to stop local redis while its client remains as phpredis?

Thank you

• This reply was modified 4 years, 1 month ago by futureyoon.
• This reply was modified 4 years, 1 month ago by futureyoon.

Never mind, I think i found the culprit.. it’s not H5P neither learndash…

it’s buddyboss.
I have added a buddyboss shortcode inside the lesson. that breaks things..

Do you have any idea how to fix this?

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

OK.

Just for my understadning for this update,
“Support for environments where DOCUMENT_ROOT is different from WordPress installation directory”

Any partcular scenarios that you were aware of and tried to fix with this release?
It’s because as we have done a couple of test together earlier, it requires a brand new env setup. so if this update is not meant for AWS cloudfront or CDN related, it wouldnt be so worth to go thru the test again..

Do you mind sharing some cases that you were targeting to resolve. Thx

• This reply was modified 4 years, 2 months ago by futureyoon.

Thank you so much. Yes the color code would make user life easier 🙂

Oh I think i found it.

I have to see it from ‘Published’
but it still seems to be a bug as in why ‘Published’ tab display all templates created and published but yet ‘All’ tab doesnt list those templates that I can see from ‘Published’?

it doesn’t seems right.

Thx for the info.

Just curious for the s3 bucket.

Should I expect .webp file stored in S3 bucket when I enable this plugin?

Would be able to confirm this?

Thank you

OK. Thank you for taking a look at this and addressing the issue. 🙂 I saw a new release from amelia. this fix is implemented in a new release?