i know you said
Btw: I'm typing this problem description without having current access to the environment. So please ignore any syntax errors.
but i have to ask the question.
do you use #APP_IMAGES# as prefix?
Workspace Files use #WORKSPACE_IMAGES#myFilename.png as Prefix.
I am using #APP_IMAGES# and I uploaded them as static application file. The link was in fact copied from the static file page.
But all applications in all new workspaces seem to have this problem.
In case it matters: Database Schema Name and Workspace Names are identical. I tested to change the path prefix (manage services/set workspace preferences), but still the image didn't show (although the path returned by #APP_IMAGES# changed).
Normaly I would expect some issue with ords config, but since the images do function in another workspace I am somewhat confused about this.
if I had a mistake like that, I'd do the following.
1. Download a File from the staticfilies. open it on my computer
Delete the file from the Applicatoin static files.
2. upload the file loaded in point 1.
3. testing of the file uploaded in point 2 in the application
If this works, I would think that a referencing did not work correctly.
hopefully this will help.
Tried all this several times. I loaded the same file in one of the working workspaces and it was shown properly. Also it does not make a difference whether it is an application static file or a workspace static file.
I think there must be some special referencing on workspace level going on. I have the impression, that workspaces that were migrated from 5.0 do work and newly created workspaces in Apex 5.1 do not work. What I do not know, is how can I track where the different parts of the ords url are resolved.
Like check in ords_metadata and also in apex_050100 or maybe apex_listener.