As part of our installation, we have a need to select Chinese as a default language for certain fields.  On my local install I have this working though it was not clear exactly which step caused that to finally work. As I started to install the several config files in production to replicate this, I have found an odd side effect.  The language list is not loading.  A Chrome Inspect does not show the list as usual.  Instead I get the placeholder. On the local install, an Inspect Element in Chrome has this line. <option value="urn:cspace:core.collectionspace.org:vocabularies:name(languages):item:name(zho)'Chinese'" selected="selected">Chinese</option> However, on production it has only this: <option value="" selected="selected">Please select a value</option> So, I conclude from this that production is missing some state or step that allows it to load these dynamic term lists. I can confirm that the http://{host}:8180/collectionspace/tenant/core/authorities/initialise step has been done on production.  Under Administration >> Term List Management >> Languages (3rd instance), I see the list of languages, including Chinese. As I stated in another thread, we have 2 users that were created, have disappeared from the web UI, and I cannot add them back in. If we have to clear the databases and recreate them to get progress again, I can do that but I need a process to follow. Thanks for any help you can provide to get us back on track for this deployment. James D. Keeline

As noted in a previous response, wiping and re-creating databases and starting with a fresh slate, on your production instance, might be prudent at this point. That response mentions the command that can be used for doing so ... one that your sysadmin apparently has already run at least once, and might now run again: "Running 'ant undeploy deploy create_db -Drecreate_db=true import' once again, from within the topmost directory of the source code tree for the CollectionSpace Services layer ..." On Thu, Jun 16, 2016 at 9:14 AM, James Keeline <james@keeline.com> wrote: > As part of our installation, we have a need to select Chinese as a default > language for certain fields. On my local install I have this working > though it was not clear exactly which step caused that to finally work. > > As I started to install the several config files in production to > replicate this, I have found an odd side effect. *The language list is > not loading.* A Chrome Inspect does not show the list as usual. Instead > I get the placeholder. > > On the local install, an Inspect Element in Chrome has this line. > > <option value="urn:cspace:core.collectionspace.org:vocabularies:name(languages):item:name(zho)'Chinese'" > selected="selected">Chinese</option> > > However, on production it has only this: > > <option value="" selected="selected">Please select a value</option> > > So, I conclude from this that production is missing some state or step > that allows it to load these dynamic term lists. > > I can confirm that the *http://{host}:8180* > */collectionspace/tenant/core/authorities/initialise* step has been done > on production. Under Administration >> Term List Management >> Languages > (3rd instance), I see the list of languages, including Chinese. > > > As I stated in another thread, we have 2 users that were created, have > disappeared from the web UI, and I cannot add them back in. > > If we have to clear the databases and recreate them to get progress again, > I can do that but I need a process to follow. > > Thanks for any help you can provide to get us back on track for this > deployment. > > James D. Keeline > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > >