I was really referring to the fact that I’m usually against storing your own custom things under /i/ as that is where the standard APEX installed files live.

For any of our custom resources we tend to setup something like /ci/ this way our custom themes can refer to /ci/css/sidebar.css etc and we don’t need to worry that we’ll ever accidently wipe out our own things if we upgrade APEX, it also helps to make a better separation between the ‘core’ things in APEX and our own custom resources etc.

Hope this clarifies,

John

Your assumption that I am storing images/css/javascript etc. under /i/ is correct. But of course, all of these files are created and stored on the local file system and “put” to /i/ via the WebDAV connection, hence the “locked” resource issue that is the subject of this post. Working this way means theme files can easily be restored en masse following an APEX upgrade and negates the risk of them being wiped out for good.

Stephen

I’m assuming you’re also uploading and storing your own images/css/jaavscript etc under the /i/ location.

I would really recommend against that, as you’re exposing yourself to wiping out those resources when you come to upgrade APEX (as you’ve discovered), instead I’d recommend creating your own location for any custom resources and using that.

Just my thoughts,

John.