Hi Thomas, You should be able to simply run archesproject/build/install_arches_db.sh (or install_arches_db.bat on windows) and then archesproject/build/install_packages.sh (or install_packages.bat). You will need to have elasticsearch running when you run install_pacakges. However, this is only a good solution for a dev version though as this will truncate your existing arches database and you will lose any business data. In production, presently the best approach I'm aware of is to extract your business data, completely redeploy Arches including the database, and then reload your business data.
Cheers, - Rob On Tuesday, April 15, 2014 5:40:32 AM UTC-7, [email protected] wrote: > > Hi Bob, > you were perfectly right, that was a false alarm. -> local browser cache > "issue" when testing the official v2.0. And previously we were on the most > recent dev version (when the error occurred). > Btw. how do you keep a once-built dev version up to date without too much > effort? > > Sorry and thanks a lot. > Thomas > > > Am 14.04.2014 19:22, schrieb Rob Gaston: > > Hi Thomas, > > Strange, I just grabbed version 2.0.0 from the same url that you linked > to and I'm not seeing that issue -- is it possible that this is an issue > with your local browser cache or that you are seeing a different issue > (perhaps with the same error but from a different source)? > > It would be helpful to see exactly where the error is occurring (and any > additional information, especially a stack trace) and also (if possible) > see the copy > of /archesproject/arches/Media/js/debug/widgets/Arches.widgets.MapPanel.js > that you've got locally. > > Please keep me updated! > > Thanks, > - Rob > > > On Sunday, April 13, 2014 10:48:46 PM UTC-7, [email protected] wrote: >> >> Good Morning Rob, >> hmm thats odd, when we reinstalled from scratch on friday i downloaded >> the official v2 from https://bitbucket.org/arches/arches/get/2.0.0.zip. >> I just re-checked that we are on the official v2 on the dev server and >> still i can see the error. But anyway, great it is fixed in the latest dev >> version - we will use that from now on. Thanks for your support! >> Thomas >> >> >> Am 12.04.2014 19:07, schrieb Rob Gaston: >> >> Hi Tobias, >> >> Thanks for finding this issue. Looks like this is a bug in the latest >> development Arches code, but was not present in the officially tagged v2 of >> Arches. As such I assume you are running the very latest, correct? This >> is fine, it just means that the version you are working with has not been >> scrutinized as heavily and may have some issues. I've fixed this in the >> code repository. If you update to the latest code you should no longer see >> this issue. >> >> Thanks again for bringing this to our attention! >> - Rob Gaston >> >> >> On Saturday, April 12, 2014 12:04:57 AM UTC-7, Tobias Kohr wrote: >>> >>> So this is the error that occurs in JavaScript (line 67 in >>> Arches.forms.Locations.js), when clicking on the "Locations" button: >>> >>> TypeError: this.mapPanel is undefined >>> >>> this.map = this.mapPanel.map; >>> >>> Is this a problem of our installation or a general bug? >>> >>> Cheers, >>> Tobias >>> >>> >>> 2014-04-11 19:21 GMT+02:00 Tobias Kohr <[email protected]>: >>> >>>> Dear Arches fellows, >>>> >>>> in our Arches v2 installation the functionality of adding locations >>>> to ARCHAEOLOGICAL HERITAGE (SITE) didn't work anymore. So we did a clean >>>> re-install of Arches v2 today, with the result that we still cannot add >>>> locations either. >>>> >>>> Is this a problem of our instance or did we discover a bug in >>>> v2 here? Can you add a location to a site in your Arches instances? >>>> >>>> Firebug shows an error that mapPanel is undefined in some script. I >>>> will give a better description and further debug on monday with access to >>>> our dev server. >>>> >>>> Thanks for any feedback! >>>> -Tobias >>>> -- >>>> -- To post, send email to [email protected]. To unsubscribe, >>>> send email to [email protected]. For more information, >>>> visit https://groups.google.com/d/forum/archesproject?hl=en >>>> --- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Arches Project" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/archesproject/dalgNIwLI9s/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> -- To post, send email to [email protected]. To unsubscribe, >> send email to [email protected]. For more information, >> visit https://groups.google.com/d/forum/archesproject?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Arches Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> >> >> -- > -- To post, send email to [email protected] <javascript:>. To > unsubscribe, send email to [email protected] <javascript:>. > For more information, visit > https://groups.google.com/d/forum/archesproject?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Arches Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
