Release announcement- AtoM 2.1

[Sarah Romkey]

Greetings AtoM Users!

We are pleased to announce that the AtoM 2.1 release is now available for download. You will find the newest release on our Download Page. As always, upgrading instructions can be found in our Administrator's Guide:

• Download AtoM 2.1: https://www.accesstomemory.org/download/

• 2.1 Upgrade guide: https://www.accesstomemory.org/docs/2.1/admin-manual/installation/upgrading/#installation-upgrading

We've closed over 120 issue tickets in the 2.1 release, including bug fixes, usability improvements, and new features. This release also includes some major code contributions from developers in our user community - thank you to all for your contributions! You can get an overview of all the associated tickets in our issue tracking system here: https://projects.artefactual.com/versions/8. To see the issues organized by Category, click this link. An outline of some of the major changes will be included below.

Our demo site has been upgraded to 2.1 at http://demo.accesstomemory.org.

Important: Elasticsearch upgrade required for 2.1

With AtoM 2.1, we have upgraded Elasticsearch, AtoM's search and analytical engine, from ES 0.9 to ES 1.3. To install AtoM 2.1, you will first have to upgrade your Elasticsearch installation. You can find more instructions on how to do so in the Elasticsearch documentation: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/setup-upgrade.html

Note that this upgrade will be what is considered by Elasticsearch to be a "Restart upgrade." You can always try searching for tutorials, or even post in the Elasticsearch User Forum or IRC Channel, if you require assistance - see: http://www.elasticsearch.org/community/ for more details.

New: Place and Subjects browse redesign

(Sponsored by Dumbarton Oaks Image Collections and Fieldwork Archives)

• #5434 - "Place" term taxonomy made visible to users for enhanced public browsing

• #5436 - Improve Terms dedicated search box and enable searching for "Use for" labels

In AtoM 2.1, data included on Place and Subject pages such as scope notes, maps, etc, can be made publicly visible, as the elements of the internal Term view page and the public browse page have been integrated. Users are given a treeview of hierarchical terms as well as an alphabetic list and a dedicated search box that can find terms based on All labels, authorized form of name, or "Use for" non-preferred labels.

New: Multilingual usability improvements in AtoM!

(Sponsored by the Canadian Council on Archives)

• #7122 - Display language dropdown menu at top of descriptions to indicate when translated content exists

• #7120 - Alter language facet to display unique documents regardless of culture

A "Unique records" facet will now be the default selection which will display all original (e.g. not translated) descriptions regardless of culture in the Browse pages. Selecting a specific culture will reveal all descriptions in that language - both original and translated. Additionally, when viewing a description, if translations exist, a drop-down menu with the alternate languages listed will appear at the top of the description - click on one, and AtoM will flip the display language of the interface and reveal the translated content.

New: Add alternative and legacy identifiers

(Sponsored by the Australian National University)

• #6107 - Add alternate number field

Now in AtoM, below the identifier field, a link is given to be able to add legacy or alternative identifiers to a description. Users can enter a custom label to clarify the role or status of the identifier (e.g. "Legacy ID") and a value. When saved, the alternative identifiers will appear in the Notes area with the custom label next to them. This will work on EAD import as well - if  @type and @label attributes are included with a <unitid> element, and the @type="alternative" they will import and map to the new custom field.

New: Add additional access points to Archival Institutions

(Community code contribution from the University of Saskatchewan's University Archives & Special Collections)

• #5596 - Repository records - additional access points and facet

Two additional access points have been added to the ISDIAH template  - Geographic subregion and Thematic area. Akin to a subject access point for repositories, the Thematic area taxonomy has been pre-populated with terms in English and French taken from the Canadian Council on Archives' Directory of Archives Theme terms. All terms are editable or can be deleted by users, just as new terms can be added. These new access points will also be available on the Archival institutions browse page as facets available for filtering results.

Lots of other new features!

Highlights include:

• #6049 - Add converse predicates to ISAAR relationships (automatic bidirectional linking)

• Sponsored by the Australian National University

• #6302 - Description identifier added to search index and browse results for authority records

• Added by Kehan Harnan of Gaia Resources - community pull request

• #3899 - RAD and ISAD area headers added to Visible elements module

• Added by the University of Saskatchewan - community pull request

• #5971 - Add ability to hide Archival history from public view (via Visible elements module)

• Sponsored by the Australian National University

• #6308 - Add a setting to sort by identifier then title and expose it on the relevant browse pages

• Added by Kehan Harnan of Gaia Resources - community pull request

• #6991 - Sort button added to digital object browse page

• Sponsored by the University of the Witswatersrand

• #5977 - Add "Date" field (of creation) to "Add new children" widget option in RAD and ISAD edit templates

• Sponsored by the Australian National University

• #6537 - Add basic search to the physical storage browse page

• Added by Seamus O'Connor of Pneumatic Web - community pull request

• # 5435 - Ability to link to related descriptions in AtoM (via an autocomplete beneath the Related materials field) and display link as title of resource

• Sponsored by Dumbarton Oaks

• #7241 - Add columns to the accession browse page for enhanced usability

...and more!

Improvements to the command-line tools and CSV import

Highlights include:

• #6752 Add qubitParentSlug as an option for importing legacy accessions via CSV and linking them to existing descriptions

• Added by Jen Whitney of Carleton University Library - community pull request

• #7247 - Add --index configuration option to the digitalobject:load CLI task

• Added by Edgar Rodriguez of XerCode - community pull request

• #6121 - CSV import - digitalobject:load CLI task can now use identifier.

• #7130 - Add Cast, Credits, and Signatures RAD other notes fields to RAD template and CSV import template

• Added by Seamus O'Conner of Pneumatic Web - community pull request

• #6525 - Add columns for digital object URL and/or filepath to CSV description import templates

• Sponsored by the World Bank Group Archives

• #7108 - improve --output option’s CSV output formatting on import:bulk CLI task

• #6373 - bulk EAD export:  add parameter to limit export to top-level descriptions

• Sponsored by the University of Saskatchewan

...and more!

Bug fixes and usability enhancements

Highlights include:

• #6644 - Return simple markup for lists to the free-text fields in descriptive templates

• #6007 - Add full-text search to the Accessions dedicated search box

• Sponsored by the City of Vancouver Archives

• #7136 - Search auto-suggest no longer replaces query in search bar

• #6739 - All series notes will now export when EAD is exported from the fonds-level

• #6047 - CSV imports include publication status

• #5590 and #6225 - related to mobile interfaces.

• #7016 - DIP upload fixes from most recent version of Archivematica (1.2).

... and many more.

The full list of issue tickets associated with the 2.1 releases can be seen here.

We have created a 2.1 documentation branch - currently they are just a mirror of the 2.0 docs, but over the coming weeks we will begin documenting all these exciting changes and new features. You can see the 2.1 branch of our docs here: https://www.accesstomemory.org/docs/2.1/

We also hope, in the near future, to begin pushing our documentation to Transifex, the service we use for including translations in AtoM, and for translating this website. This will allow our community translation volunteers to begin translating our User and Administrator's Guides if desired! Please expect that the 2.1 documentation branch will be changing significantly in the next months, as we update it to reflect all the changes in AtoM 2.1.

Artefactual also hopes to prepare a 2.1.1 release in a couple months, to include any further interface translations supplied by our volunteer translators via Transifex, as well as any bug fixes we have addressed in the interim. We're also already hard at work on our 2.2 release, which will include a number of exciting features! For more information on 2.1 Translations and how to contribute, see our related User Forum post, here: https://groups.google.com/d/msg/ica-atom-users/F0WygByV-YY/8zKc4tRoUTIJ

Thank you to all our development sponsors, community code contributors, and volunteer translators for making this an amazing release!

Regards,

Dan and Sarah, on behalf of the team at Artefactual

[Anne-Marie]

CONGRATS! Thanks for the acknowledgment. We're delighted to have worked with you guys to further enhance such an amazing tool. Can't wait to get the upgrade in place and start playing around!

<li dir="ltr" style="list-style-type: circle; font-family: Arial; color: rg

...

[sup...@ntair-mail.ca]

Hello and happy Wednesday

Once I down load the rpm tar base and tar xzf atom-2.1.0.tar.gz -C /usr/share/nginx/atom --strip 1 

It's missing the upload folder.  Do I just create it

Thanks 

[Jesús García Crespo]

Hi there,

You don't have to create it, AtoM will do that for when it's necessary as long as the permissions have been set properly.

Regards,

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/6868e796-1976-4e73-8d37-bdd4099cdb7f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

[Ben Stewart]

Hello again

I managed to get this working on CentOS 6.5.  I had a few hickups but for the most part the upgrade from 1.3.1 went much better then the version ATOM 2.0.1 did for me, I suspect the newer version of elasticserach fixed the issues i was having.

I have a couple of questions that remain:
I seemed to have blown away my admin user account or password issue after I recreated the data base as I has an SQL import error after I had setup the application.   Is there a way to reset the admin user from the command prompt?
The other is I can not see the images they are all grey blanked out.  I did try the command (php symfony digitalobject:regen-derivatives) twice before and after I change the owner of the "uploads" folder to www-data with the same results.
Is this tied to the "imagemagick" package?  Is there something else I can look at.

I did try to look at your 2.1 demo site but i get the 403 you been Forbidden error.

Very excited to try this, thank you for your time.

~Ben

System Administrator
Geoffrey R. Weller library & NBCA
UNBC, BC Canada
PH (250) 960-6605
benjamin...@unbc.ca
 

[Jesús García Crespo]

Hi Ben,

On Thu, Oct 9, 2014 at 10:40 AM, Ben Stewart <bcben...@gmail.com> wrote:

I seemed to have blown away my admin user account or password issue after I recreated the data base as I has an SQL import error after I had setup the application.   Is there a way to reset the admin user from the command prompt?

Yes, you have a couple of task that may help: "tools:add-superuser" and "tools:reset-password". Append "-h" at the end to access to the task help.

Also:

- https://www.accesstomemory.org/es/docs/2.1/admin-manual/maintenance/cli-tools/#change-a-password

- https://www.accesstomemory.org/es/docs/2.1/admin-manual/maintenance/cli-tools/#add-a-superuser-admin-account

 

The other is I can not see the images they are all grey blanked out.  I did try the command (php symfony digitalobject:regen-derivatives) twice before and after I change the owner of the "uploads" folder to www-data with the same results.
Is this tied to the "imagemagick" package? Is there something else I can look at.

Hmmm, I wonder if something went wrong during the SQL upgrade. I'd take a look to the digital_object table and see if the path of the images matches with the files under /uploads in your filesystem. I'll ask my colleague MikeG because I think he's dealt with similar situations.

 

I did try to look at your 2.1 demo site but i get the 403 you been Forbidden error.

Fixed now, sorry about that!

[Ben Stewart]

Hello and good afternoon

All those tools and information you supplied worked great, after correcting the uploads path things are moving along good until I reached this point which I do believe I was at once before.

After running the php symfony digitalobject:regen-derivatives command and all worked correctly I when on to re-index php symphony search:populate

I sure I'm almost sure I seen this error with the 2.0.1  I tried to look in the FAQ but can not find anymore than it's still and error.

Maybe i'm looking in the wrong place, almost sounds like an elasticsearch issue more than a PHP issue.  

 

PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 5647239 bytes) in /usr/share/nginx/atom/vendor/Elastica/lib/Elastica/Transport/Http.php on line 108

This is what I found searching the FAQ.

• Why do I get a “Allowed memory size” exhausted error?
  

Thank you

~Ben

[Jesús García Crespo]

Hello Ben,

On Tue, Oct 14, 2014 at 1:21 PM, Ben Stewart <bcben...@gmail.com> wrote:

PHP Fatal error:  Allowed memory size of 134217728 bytes exhausted (tried to allocate 5647239 bytes) in /usr/share/nginx/atom/vendor/Elastica/lib/Elastica/Transport/Http.php on line 108

It seems that you've reached the memory_limit set in your environment. You can either update the configuration in one of the php.ini files or pass "-i memory_limit=" to the command line, e.g.

php -i memory_limit=-1 symfony search:populate

^ That will run the interpreter with no memory limit.

Regards,

[Ben Stewart]

Thank-you

The fix that worked or me was modifying the /etc/php.ini

max_execution_time = 300

memory_limit = 256M

Ben

[sisco...@gmail.com]

Hello,

We are beginning our journey with AtoM 2.1 to catalog our archival collections. However, we have run into a few hiccups that we hope this user group can help us solve as we continue to use the system. Our central issues are as follows: 

1) We are receiving an '500 server' error after attempting to create or save information that we have generated and populated the fields. 

2) Before we receive this '500' error, there is usually a long lag time when we are attempting to upload, create, and save anything. I've attached screenshots to highlight what we are seeing on our end.

We've answered the questions that AtoM asks of all inquirers. Thank you in advance!

• What version of AtoM are you using? 2.1
• What have you tried already to resolve the problem? *Reboots, *Tweaks to the php.ini, my.ini, and elasticsearch.yml files, *Using CLI to import works just fine, *File/folder permissions changes
• What operating system is AtoM installed on (Linux, Windows, Apple, etc.)? Windows
• What version of PHP do you have installed? 5.5.16
• Do you have a stack trace of the error message you received? No.
• Are you hosting your own instance, or are you using an external hosting provider? Hosting our instance

All my best,

Lisa S.

On Monday, September 22, 2014 2:31:11 PM UTC-4, Sarah Romkey wrote:

<li dir="ltr" style="list-style-type: circle; font-family: Arial; color: rg

...

[Sarah Romkey]

Hello Lisa,

Thanks for getting in touch! I'll need to get one of our developers to pop into this thread and take a look- it will take a couple of days, because today is a stat holiday in Canada, and tomorrow we have an all-staff retreat for the day. In the meantime, you could put your AtoM site in debug mode (https://www.accesstomemory.org/en/docs/2.1/admin-manual/maintenance/debug/#debug-mode) to get a more verbose error message, which might help diagnose the problem.

Cheers,

Sarah

Sarah Romkey, MAS,MLIS

Systems Archivist
Artefactual Systems
604-527-2056

@ArchivesSarah

--

You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/a09d628d-b48e-4ae7-abac-1f8c22e9e27f%40googlegroups.com.

[mi...@artefactual.com]

Hi Lisa,

Seeing what's at the end your web server's log, immediately after you get a 500 error, would be helpful for diagnosing.

If you're running Linux, you can display this on the command-line by entering something like this:

  tail <location of server error log file>

Cheers,

Mike Cantelon

Artefactual Systems

...

[Dan Gillean]

Hi Lisa,

Just to add to Mike's comments, if you have followed our installation instructions to the letter, here is an example of the exact path to the web server logs:

• https://www.accesstomemory.org/docs/2.1/admin-manual/maintenance/logging/#web-server-logs

Cheers,

Dan Gillean, MAS, MLIS
AtoM Product Manager / Systems Analyst,
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--

You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/9b7a9269-b389-4458-ac26-d67c753e0d52%40googlegroups.com.

[Lisa Sisco]

Hi Mike, Dan, and Sarah:

We are running it in Windows and our server environment is VMWare. Dan and Mike, thank you for the tips and we will get back to you by the middle of next week once we can look at the web logs after we receive the 500 error. 

And thank you all for your prompt responses! We really appreciate the support.

Respectfully,

Lisa S.

--
You received this message because you are subscribed to a topic in the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/ejPifhY_7YU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.

To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZ%2ByoRVZepAwHj%2BsjrMRovZBQ5obZmoWYHpjjdwjtgAZFw%40mail.gmail.com.

[sisco...@gmail.com]

Hi Dan, Sarah, and Mike:

 

The previous issue seems to have been solved. However, we are still receiving a '500 server error' message when trying to link or upload digital objects. I copied the web logs below with the help of our IT department after we "tripped" the system. Any suggestions as to what we should do to rectify this issue? 

2014-11-20 14:55:48 172.25.24.231 GET /index.php/arctic-3 - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arthur-twomey-records 200 0 0 531

2014-11-20 14:55:51 172.25.24.231 GET /index.php/arctic-3/addDigitalObject - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3 200 0 0 562

2014-11-20 14:56:54 172.25.24.231 POST /index.php/arctic-3/addDigitalObject - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/addDigitalObject 302 0 0 375

2014-11-20 14:56:54 172.25.24.231 GET /index.php/arctic-3 - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/addDigitalObject 200 0 0 499

2014-11-20 14:56:58 172.25.24.231 GET /index.php/arctic-3/multiFileUpload - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3 200 0 0 343

2014-11-20 14:56:58 172.25.24.231 GET /vendor/yui/uploader/uploader-min.js - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 200 0 0 0

2014-11-20 14:56:58 172.25.24.231 GET /js/multiFileUpload.js - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 200 0 0 15

2014-11-20 14:56:58 172.25.24.231 GET /vendor/yui/logger/logger.js - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 200 0 0 218

2014-11-20 14:56:58 172.25.24.231 GET /vendor/yui/uploader/assets/uploader.swf - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 200 0 0 15

2014-11-20 14:57:04 172.25.24.231 POST /index.php/digitalobject/upload symfony=f7t3qbfmosmtufj6rgvm0655g3 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 200 0 0 343

2014-11-20 14:57:04 172.25.24.231 GET /uploads/tmp/THBabf024c5.jpg - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 200 0 0 15

2014-11-20 14:57:08 172.25.24.231 POST /index.php/arctic-3/multiFileUpload - 80 - 172.25.17.130 Mozilla/5.0+(Windows+NT+6.1;+WOW64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/38.0.2125.111+Safari/537.36 http://atom.carnegiemuseums.org/index.php/arctic-3/multiFileUpload 500 0 0 531

 
It is important to note the following: we have increased the size limitations for uploads in php, iis, etc. iis_iusrs user account has full read/write privileges over the websites directory. Would it be possible that the site is looking for a temp directory or a physical location to store the files that may not be set up? Or are the files stored directly in MySQL and could there be a problem there.

All my best and thank you for your insights,

Lisa S.

...

[Jesús García Crespo]

Hi Lisa,

That seems to be the access log of your web server, which normally doesn't contain any details of the errors. Try looking at the error log.

--

You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/7452a6e5-53e0-4983-95e4-2e0153e222e0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[mcot...@gmail.com]

Hello, I cannot seem to install the latest AtoM appliance according to this article.

When I followed the instructions I got:

user@work1:~/atom-vagrant$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:
* The box 'artefactual/atom' could not be found.

In editing the Vagrantfile, I do not know which path to supply for the "config.vm.box_url" variable.

Could someone please point me to a link to the AtoM 2.1 appliance?
(note: the only link I find to an appliance is to the 1.3.1 version)

Thanks

[Jesús García Crespo]

Hi there,

You need to install the latest version of Vagrant available from https://www.vagrantup.com/downloads.html.

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/5e2947ef-5393-457c-8bcf-67de743fb63c%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[mcot...@gmail.com]

Worked perfectly, thanks.

For info: With ubuntu 14.04 the base repository install is Vagrant 1.4.3....clearly a few versions behind.

[Jesús García Crespo]

Oh, thanks for sharing that with us. I've added a note in our docs.

Cheers, 

On Fri, Nov 21, 2014 at 9:11 AM, <mcot...@gmail.com> wrote:

Worked perfectly, thanks.

For info: With ubuntu 14.04 the base repository install is Vagrant 1.4.3....clearly a few versions behind.

--

You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/dc5aa7e0-6cf2-4d02-81fe-ed4293c1ffec%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.