These are chat archives for collectiveaccess/support

3rd
May 2016
Kehan Harman
@kehh
May 03 2016 01:33
@eriwm The directories that should exist in that directory are listed in app/conf/media_volumes.conf, and these should all get created by the installer. If you moved your media directory then possibly these did not move with it?
@stefankeidel I was afraid you'd say that ;)
ericwm
@eriwm
May 03 2016 10:52
Hello, This is just an observation. I have just deleted my providence-develop directory and unzipped a new version. Edited a new setup.php and logged in from my browser. Got the usual error messages re permissions etc.. Looked in the media directory and the only files there were - readme and htaccess files. I created /collectiveaccess and then workspace, images and tilepics, set permissions and everything worked ok. Am i doing something wrong that prevents these folders being written to the media directory?
CollectiveAccess
@collectiveaccess
May 03 2016 10:52
The installer should create them on installation.
Oops, I'm repeating everyone else :-)
The odd thing is that the installer should refuse to install if it can't write to the media directory. Is the media directory mounted in some semi-odd way?
ericwm
@eriwm
May 03 2016 10:54
Such as?
CollectiveAccess
@collectiveaccess
May 03 2016 10:54
NFS?
Is it just a plain old directory? If so, what are the permissions?
ericwm
@eriwm
May 03 2016 10:55
not that I am aware of I am using Ubuntu server
CollectiveAccess
@collectiveaccess
May 03 2016 10:55
Which version?
ericwm
@eriwm
May 03 2016 10:56
permissions are 777 vers 14.04.1
CollectiveAccess
@collectiveaccess
May 03 2016 10:57
ok, then that's just odd. When you install those media subdirectories (images, workspace, tilepics, etc.) are consistently never created?
ericwm
@eriwm
May 03 2016 10:58
no - maybe I should try setting the permission on the media directory immediately after I unzip 1.7
CollectiveAccess
@collectiveaccess
May 03 2016 11:02
As long as you do it before you install it should work
you're running develop code? Or the 1.6.1 release?
ericwm
@eriwm
May 03 2016 11:32
Ok I will give it a try. I did another unzip and set the media directory permission to root before logging in from browser. Same result no subdirectories in media.
yes using develop code
Stefan
@stefankeidel
May 03 2016 11:46
You are running the installer after you unzip, right? Or are you just plugging in an existing database? The installer can't create anything if you don't run it, obviously
ericwm
@eriwm
May 03 2016 11:52
That's probably where I have gone wrong - will dump everything again and start from scratch.
CollectiveAccess
@collectiveaccess
May 03 2016 12:40
ah...
good call Stefan. Didn't think of that one :-)
ericwm
@eriwm
May 03 2016 14:39
Hi all, Don't want to waste too much more of your time but can I use a saved profile from my 1.6.1 install in a 1.7 new install if so where do I put the file ? .I have tried putting it profiles/xml as collectiveaccess.xml but cannot access it from the install menu.
Stefan
@stefankeidel
May 03 2016 14:54
That's the right location ... the name of the profile in the dropdown might be different though. It's taken from the <profileName/> element in the XML file
To be clear, you're talking about <ca_root>/install/profiles/xml/, yes?
Oh, and to answer the question: Yes, you should be able to use a profile export. Might have to tweak a few lines because we got rid of a couple of bundle but it should mostly work
ericwm
@eriwm
May 03 2016 15:32
Thank you I will try it.
ericwm
@eriwm
May 03 2016 15:39
Tried it and got this error - There were errors parsing the profile(s): Profile validation failed. Your profile doesn't conform to the required XML schema.
Stefan
@stefankeidel
May 03 2016 17:46
Well there probably is a very small (and fixable) schema error in the exported profile. Try running it through a XML validator like xmllint yourself to find out where it is
Usually it's idnos/codes that are being cut off by the profile exporter causing violations of some of the uniqueness contraints we impose on profiles (e.g. a placement code has to be unique within a screen)
ericwm
@eriwm
May 03 2016 21:25
xmllint did the trick after running this on my xml file and then copying into the xml folder my file appeared in the drop down list and installation completed with only one error namely invalid type for ui code bundle_mapping_editor_ui
Stefan
@stefankeidel
May 03 2016 21:53
That's an editor for the very old and never finished importer. You can just delete that entire <userInterface> block