Structure of /updates folder

Permalink
Hi.

I've created a package which checks for the use of various js and css files. I'm matching the file path against:

DIR_REL . '/concrete/[css|js]/...'

That's worked fine up until now that somebody has deployed on a multisite solution. It appears the files are stored in:

/updates/100510/concrete/[css|js]/...

Could somebody explain this /updates/100510/ directory? When is it used? Is it always in the same format/name? What are the various constants (DIR_APP_UPDATES, DIRNAME_UPDATES, etc)?

Is there a constant that I can use, like:

SOME_CONSTANT . '/[css|js]'

which will either end up as:

/concrete/ (a normal install at the root)
/folder/concrete/ (when c5 doesn't sit at the root)
/updates/xxxxxx/concrete/ (multisite)
etc

It appears that I'll have to check for a few different scenarios manually...

Thanks,
James

jshannon
 
ryan replied on at Permalink Reply
ryan
The /updates/100510 folder is used on our servers. the 100510 is the date of the update in this case, but typically it would be the version of concrete5 like:

/updates/concrete5.4.1/

In any case it could really be any folder name that contains a full concrete5 download like:
/updates/concrete5.4.1/concrete

You would be best to use the same value as concrete5 uses:
DIR_BASE_CORE