the UI is not accessible as never use it i.e. there is no mapping for /lucee provided. does using the UI fix this problem can it not be done via the console?
the way we deploy lucee is as follows (in order to have a cutom path and ensure the webinf is not under the www path):
- install tomcat
- change default web-inf (this is done by adding a pre execute script to systemd tomcat8 service)
sed -i 's|appBase="webapps"|appBase="/mnt/data/qebapps"|' /etc/tomcat8/server.xml
if [ -f /mnt/data/webapps/ROOT/WEB-INF/lucee/lucee-web.xml.cfm ]; then
sed -i 's,<mapping archive="{lucee-web}/context/lucee-context.lar" physical="{lucee-web}/context/" primary="physical" readonly="yes" toplevel="yes" trusted="true" virtual="/lucee/"/>,<mapping physical="{web-root-directory}/../../www/" primary="physical" readonly="yes" toplevel="yes" trusted="true" virtual="/"/>,' /mnt/data/webapps/ROOT/WEB-INF/lucee/lucee-web.xml.cfm;
fi
since the webinf is lower then the www and the mapping is modified lucee admin pages are not present but this is how we prefer it.
To test different versions we delete the ROOT directory and ROOT.war and replace it with the version we want. this way the Lucee version and extensions should be compatible since they are shipped together
My argument is that the image functions are fundamental to most websites,
how can a final release have such a major issue?
why is the same issue not present in the snapshots that follow the final release?
has no one else experienced this bug?