Fieldtype

Developer
Supported

Expresso

ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5

Back to this add-on's main page
View Other Add-ons From PutYourLightsOn

     

You must be logged in to post.

PHP errors in 2EE 2.8.1

Support (Resolved)

e2design
e2design

Just changed Wygwam to Expresso on a 2.7.3 install.
Tested and worked

Thereafter upgraded from EE 2.7.3 -> 2.8.1

And now getting PHP errors while trying to open the Fieldtype or Channel Fields (see attached).
The entries with an Expresso field still seems to work though.

PutYourLightsOn
# 1
Developer
PutYourLightsOn

what version of Expresso?

e2design
# 2
e2design

Expresso 3.3.1

e2design
# 3
e2design

Any news on this topic?

PutYourLightsOn
# 4
Developer
PutYourLightsOn

sorry about the delay, i haven’t been able to replicate this locally. i’ll troubleshoot again later and post an update for you.

PutYourLightsOn
# 5
Developer
PutYourLightsOn

i’m not convinced that this is an error with Expresso. the error is happening in Api_channel_fields.php which is a core file. might be worth asking EllisLab about this.

e2design
# 6
e2design

I solved the issue by stepping back to my EE 2.7.3. version - then first upgraded to EE 2.8.1 - and from that version installed Expresso and removed Wygwam. It all works now

PutYourLightsOn
# 7
Developer
PutYourLightsOn

wow, nicely done. unfortunately EE 2.8 broke a LOT of add-ons but glad to hear you got everything working!!

tre
# 8
tre

Hi.

I’ve got this issue with 2 of my versions using EEv2.8.1 - but only when I use Expresso in a Grid. The error it’s throwing is:
A PHP Error was encountered
Severity: Notice
Message: Undefined index: toolbar
Filename: expresso/ft.expresso.php
Line Number: 304

Any insight into this?
Thank you.

PS. just updated to Expresso 3.4.5

tre
# 9
tre

Hey -

I’m sorry. The issue has resolved itself. There may have been a cache issue after updating to 3.4.5

Thanks!

FYI - it turns out that if I switched the Toolbar configuration, to Light from Basic, it the error went away. When I switched it back to Basic from Light, the error never returned. Quirky, but it did the job!

PutYourLightsOn
# 10
Developer
PutYourLightsOn

ok no problem, glad to hear it’s working for you