Expresso
ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5
Back to this add-on's main page
View Other Add-ons From PutYourLightsOn
Image problem with EE 3.3.2 and Expresso 4.2.5
Support (Resolved)
Cyril-Figgis
|
Posted: 05 October 2017 09:05 PM |
|
|
|
We are using EE 3.3.2 and Expresso 4.2.5.
When I choose Browse Files while trying to select an image, the ExpressionEngine file chooser open behind the Image Properties dialog box and it is impossible to select an image.
This happens in Chrome, Safari and Firefox.
|
|
|
PutYourLightsOn
|
Posted: 06 October 2017 05:11 AM |
# 1
|
|
Developer
|
This issue has been addressed in Expresso. Please update to the latest version of EE to resolve your issue.
|
|
|
Red Sea Studio
|
Posted: 06 October 2017 10:05 AM |
# 2
|
|
|
I’m getting the same issue with the packages I just downloaded just now - latest versions of both EE (3.5.11) and Expresso (4.2.5).
Downgrading to Expresso 4.2.4 does seem to fix this though.
|
|
|
PutYourLightsOn
|
Posted: 07 October 2017 04:43 AM |
# 3
|
|
Developer
|
Hmm, it is working fine in my local environment: EE 3.5.11, Expresso 4.2.5, Chrome 61
|
|
|
xynergy_inc
|
Posted: 16 October 2017 06:49 PM |
# 4
|
|
|
I’m also getting this in EE3.5.11 and Expresso 4.2.5, even in Chrome (v61.0.3163.100). Devot:ee won’t allow me to upload an image, but see https://ibb.co/kuUkbR for screenshot.
Could it be a side-effect of this item in the changelog: “Fixed filepicker modal issue in full screen mode”?
|
|
|
mac999
|
Posted: 17 October 2017 07:12 AM |
# 5
|
|
|
any update on this?
under pressure with a deadline and cant upload images
error
Uncaught TypeError: Cannot read property ‘getContentElement’ of null
at Object.callback (expresso.js?v=4.2.5:157)
|
|
|
PutYourLightsOn
|
Posted: 17 October 2017 07:36 AM |
# 6
|
|
Developer
|
We’re looking into this and will post an update here soon
|
|
|
mac999
|
Posted: 17 October 2017 07:45 AM |
# 7
|
|
|
thanks
|
|
|
PutYourLightsOn
|
Posted: 17 October 2017 08:28 AM |
# 8
|
|
Developer
|
Ok, we’ve tracked down the issue and have just released version 4.2.6 which fixes this. Please clear your cache when testing and let us know if the issue persists.
|
|
|
mac999
|
Posted: 17 October 2017 11:46 AM |
# 9
|
|
|
great
That worked. Thanks for your quick response
|
|
|
xynergy_inc
|
Posted: 17 October 2017 11:52 AM |
# 10
|
|
|
We’re also seeing this resolved - thanks guys!
|
|
|
PutYourLightsOn
|
Posted: 17 October 2017 11:54 AM |
# 11
|
|
Developer
|
Glad to hear it and thanks for your patience!!
|
|
|