Issues
- unsupported third party extensions warning shown for lucee extensions when offlineLDEV-2517Resolved issue: LDEV-2517Michael Offner
- getFileInfo() is really slowLDEV-2505Resolved issue: LDEV-2505Michael Offner
- Support brotli in addition to gzip for output compressionLDEV-2501
- ImageInfo and ImageRead performs way slower than ACFLDEV-2500Michael Offner
- Error caused by comments inside a tag - Incompatibility with ACFLDEV-2497
- update jcifs from 1.3.17 to 1.3.19 or replace with later fork with smb 2.0 supportLDEV-2494Zac Spitzer
6 of 6
unsupported third party extensions warning shown for lucee extensions when offline
Fixed
Description
Environment
None
Attachments
1
relates to
Details
Assignee
Michael OffnerMichael OffnerReporter
Zac SpitzerZac SpitzerPriority
NewNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Details
Details
Assignee
Michael Offner
Michael Offner
Reporter
Zac Spitzer
Zac Spitzer
Priority
NewNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created 11 October 2019 at 12:01
Updated 8 November 2019 at 13:24
Resolved 8 November 2019 at 13:24
Activity
Show:
Michael Offner8 November 2019 at 10:39
Michael Offner8 November 2019 at 10:38
Pothys - MitrahSoft14 October 2019 at 05:30
I've added a fix & confirmed the issue happened on lucee.
Pull Request: https://github.com/lucee/Lucee/pull/771
when you are offline or in flight mode (or if the update provider is down or can't connect)
the third party extension warning is incorrectly shown for the image extension
It seems all provider connection errors are silently ignored, which can be rather confusing
if you add <proxy enabled="true" port="9888" server="localhost"/> to the web config, pointing to an non existent locally proxy, you will also see this error.