You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the job macro depends on the existence of the cray lookup, which is currently a stub file in lookups/cray.csv. however when the app is installed somewhere and the cray.csv is updated appropriately, will it be overwritten next time the app is upgraded?
similarly, there is a local/sysnames.savedsearch file, which shouldn't cause problems, but nothing should be distributed in local/. it could just be put in a different directory.
the real fix is probably to have a config page which a site can use to tailor its config files according to its needs. e.g. does it have a cray, then click here to indicate you have updated the cray.csv lookup file (which the app with then confirm, and revise the job(3) lookup to use it, otherwise the job macro probably should not have it in there)
The text was updated successfully, but these errors were encountered:
the job macro depends on the existence of the cray lookup, which is currently a stub file in lookups/cray.csv. however when the app is installed somewhere and the cray.csv is updated appropriately, will it be overwritten next time the app is upgraded?
similarly, there is a local/sysnames.savedsearch file, which shouldn't cause problems, but nothing should be distributed in local/. it could just be put in a different directory.
the real fix is probably to have a config page which a site can use to tailor its config files according to its needs. e.g. does it have a cray, then click here to indicate you have updated the cray.csv lookup file (which the app with then confirm, and revise the job(3) lookup to use it, otherwise the job macro probably should not have it in there)
The text was updated successfully, but these errors were encountered: