Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: Runtime Exception

Status	Resolved
Add-on / Version	Carson 1.1.0
Severity
EE Version	7.3.14

D Majer

Feb 16, 2024

Hello,

We’ve installed the Carson trial to review whether this will be helpful for our clients’ sites. Unfortunately we are seeing the attached exception in the Omni field when editing an entry.

Do you know what is causing this please?

Thanks,
Damien

BoldMinded (Brian)

Thanks for letting me know about this, Damien. I just uploaded a new version that should fix it.

D Majer

Thanks - that’s resolved that issue. However, now when trying to use Carson actions in the edit form, we’re seeing mixed content warnings in the browser console because the ACT URL its trying to call is HTTP instead of HTTPS. All other ACT URLs in the admin are HTTPS as you would expect.

BoldMinded (Brian)

Check your site_index config value. Carson does not explicitly type out http or https it uses EE’s config settings, so somewhere you most likely have http in a setting value.

D Majer

site_url is set to be the same as base_url which is set as an env variable. The base_url definitely include https.

BoldMinded (Brian)

I’m not sure what else to look into. Carson is using EE’s functions to build the URL and is not assuming http or https. These are the settings I have in my config file:

$config[‘site_url’] = ‘https://ee-dev7.vm/’; $config[‘base_url’] = $config[‘site_url’]; $config[‘site_index’] = ”;

Did you check the site url inside the CP settings page to make sure it’s using the value from your config?

D Majer

Comment has been marked private.

D Majer

If we dd($url) in the core fetch_site_index function, the URL also includes https.

BoldMinded (Brian)

I’m not sure what else to suggest. I use this same code in several other add-ons. On occasion someone reports a similar issue and it always comes down to the site’s config somewhere along the way. Do you have any htaccess rewrites happening? Any extra config files being loaded that you forgot about? Could another add-on be modifying the config values? Have you tried a new/clean EE install with just Carson installed to see if the issue persists?

D Majer

What’s even more weird is that the URL is right if I console.log(actionUrl) in fieldtype.js in Carson

#10

D Majer

Ok, we’ve resolved that. Now Carson ACT ajax request 500 with the following response:

{”messageType”:”error”,”message”:”No such property: 'logger 'on ExpressionEngine\Legacy\Facade”,”trace”:[“#0 ee\/ExpressionEngine\/Legacy\/Facade.php(35): ExpressionEngine\Legacy\Facade->get('logger ')”,”#1 user\/addons\/carson\/Actions\/FetchData.php(60): ExpressionEngine\Legacy\Facade->__get('logger ')”,”#2 ee\/ExpressionEngine\/Service\/Addon\/Module.php(64): BoldMinded\Carson\Actions\FetchData->process()”,”#3 ee\/ExpressionEngine\/Service\/Addon\/Module.php(39): ExpressionEngine\Service\Addon\Module->route('\\BoldMinded\\Car…')”,”#4 ee\/ExpressionEngine\/Service\/Addon\/Module.php(115): ExpressionEngine\Service\Addon\Module->routeAction('FetchData ', Array)”,”#5 ee\/legacy\/libraries\/Actions.php(181): ExpressionEngine\Service\Addon\Module->__call('FetchData ', Array)”,”#6 ee\/legacy\/libraries\/Core.php(682): EE_Actions->__construct(true, Object(Closure))”,”#7 ee\/legacy\/controllers\/ee.php(51): EE_Core->generate_action(true)”,”#8 [internal function]: EE->index()”,”#9 ee\/ExpressionEngine\/Core\/Core.php(268): call_user_func_array(Array, Array)”,”#10 ee\/ExpressionEngine\/Core\/Core.php(124): ExpressionEngine\Core\Core->runController(Array)”,”#11 ee\/ExpressionEngine\/Boot\/boot.php(184): ExpressionEngine\Core\Core->run(Object(ExpressionEngine\Core\Request))”,”#12 index.php(164): require_once('…')”,”#13 {main}”]}

#11

BoldMinded (Brian)

How is the logger not available? Weird. At the top of the FetchData.php class on line 14 or so, add this:

ee()->load->library('logger')

If that fixes the issue for you I’ll add it to the next release.

#12

D Majer

Comment has been marked private.

#13

BoldMinded (Brian)

If that is the message you’re getting back from OpenAI, then that’s something to sort out with your account.

#14

D Majer

We have it up and running now. A couple of questions:

Does Carson support grid fields, particularly within fluid? It appears to just place a Carson wand icon to the top right of the grid field instead of against each text input within a grid.
Does Carson support Wygwam?
The Carson SEO field looks to work well with SEO Lite, however, we’re not seeing any results with the Carson Assistant field. There is an error that displays in the browser console: Uncaught TypeError: Cannot read properties of null (reading ‘parentNode’)

#15

BoldMinded (Brian)

Yes, it should. I tested both separately, but didn’t test Grid inside of Fluid.
Yes, it’s just a CKEditor field.
I’m going to need more information. What is your assistant field settings? Screenshot or video of what is going on would help.

#16

D Majer

Comment has been marked private.

#17

BoldMinded (Brian)

Comment has been marked private.

#18

D Majer

Comment has been marked private.

#19

BoldMinded (Brian)

You’re using the Wygwam field from EE Harbor? Why not switch to the native RTE? It’s still CKEditor under the hood. I have to think about this a bit more, my first thought is since Carson only supports EE 7.3 and above, there isn’t much need for Wygwam. It’s basically deprecated and being phased out b/c the RTE is basically Wygwam, but native, so I don’t see a reason to support Wygwam separately.

#20

BoldMinded (Brian)

You should be able to change the field type from Wygwam to RTE without losing content.