Thanks for the reply. The file exists in /usr/local/interworx/var/errors, but not exists in apache environment, maybe caused by some missing apache configuration?
I did not changed any apache related configuration on the server.
After some research, i found the root of the problem.
In the apache config the disabled site’s document root is /home/interworx/var/errors/disabled but in that directory, there is no iwx-error.css and apache can’t handle the …/iwx-error.css link to the main directory.
Maybe a quick fix is a symbolic link.
Good point, and I just tested in our server and it does not appear to use the iw error.css file either.
I’m thinking ahead a little here, so sorry if I’m wrong, but if symlinked, and the future updates from IW are installed, but let’s say they move the CSS file, would that not cause a reverse failure if using symlinked.
Perhaps a better idea would be to move the CSS folder into the disabled folder, and tweak the php on the disabled file, which should work I think, and I’ll email Mr T about this, so it can be corrected on future updates.
I hope this makes sense and I’m sorry if I’m wrong, I was just thinking ahead and how it might be affected, as symlinked files or folders could easily be forgotten they exist.