Hi All,
I notice that the Scholar-3.5.0 distribution is organized quite a bit differently than Scholar-3.4.1.
Are the implications of this change discussed someplace?
I only found one mention of it, on the Harvard site:
http://openscholar.harvard.edu/software/openscholar-drupal-7/7x-35
Here, at the end of the change list, under Dev & Infrastructure, they mention:
"Note: this release introduces the make file. Upgrading from 7.x-3.4 to 7.x-3.5 requires extra system operations."
What are these extra system operations specifically?
The reason I ask is that I succeeded installing Scholar-3.4.1 but failed with Scholar-3.5.0.
Scholar-3.4.1 I installed by
1. dropping the decompressed folder (renamed as 'openscholar') into the profiles directory of the basic Drupal I already installed in the web folder.
2. making the sites/all/modules and sites/default directories read/writeable
3. creating a sites/default/settings.php by copy/pasting sites/default/default.settings.php
4. navigating to the new site's url and following the Drupal installation instructions, choosing OpenScholar, etc. No troubles.
If I follow the same recipe with Scholar-3.5.0, step 4 fails after choosing English as the language.
There is an error "Sorry, the profile you have chosen cannot be loaded."
I suspect it has something to do with the new file structure and the 'extra system operations.'
Thanks for any insight.
Comments
I am also experiencing issues
I am also experiencing issues with upgrading from 3.4 to 3.5
I use git to track the changes and i have done some local custom code changes in OS 3.4. I tried to create patches with git format-patch option, but because OS 3.5 has changed the file structure(instead /profiles/openscholar is now /profiles/openscholar/openscholar), it is harder to merge.
Is it even possible to do the upgrade with git from 3.4 to 3.5? Could any of the OS Core developers please give some advice or guidelines how this could be accomplished?
We are in the process of
We are in the process of writing some upgrade instructions now. Upgrading is possible and should not pose an issue. There is a build script that needs to be run since we are using a make file instead of managing duplicate copies of Drupal modules. The structure of your docroot will remain the same. We will be releasing a tarball that is in the same structure as previously, but if you would like to build the application your self it is pretty painless.
You no longer need to download Drupal core separately. Checkout 3.5 and run ./scripts/build this will make a docroot at' GIT_ROOT/www" with the same structure as before. You will need a current version of drush installed.
Hope this helps, let me know if you have any issues.
Thanks,
Richard Brandon
Make file?
Is ./scripts/build a traditional drush make file? When I try running "drush make scripts/build" I get a warning about the 'core' attribute being required. I'm trying to learn drush for this (I've needed to for a while, so this is as good a reason as any), and am not sure I'm understanding how to call the scripts correctly.
TLDR; It is a bash script not
TLDR; It is a bash script not a drush make command.
./scripts/build is a bash script that runs a traditional drush build
It handles keeping your settings in place and copying the 4-5 diverged modules that we are still working on into the contrib directory.
It also keeps drupal core separate from the profile and adds a symlink. You can take a look at the script of you want to see how to build it manually.
Or even better you can contribute back some parameters for that script that allow for the docroot to be named something other than www etc...
Thanks,
Richard
Windows 7 with Nginx
How do I run this script in Windows? I have drush.
My docroot is blah/openscholar/public_html; how do I target the build to be done there?
Thanks!
sedroca, I've asked our
sedroca,
I've asked our windows dev to document how he handles the script.
In the meantime you can get a prebuilt copy from our official release page, http://openscholar.harvard.edu/download
Jon
Thanks
Thanks for adding the prebuilt copy - while I'm still working out some infrastructure issues on my end, I'm going to use that.
From the root of where you've
From the root of where you've put OpenScholar, run ./scripts/build. I don't have Nginx installed, so I don't know how far the build process will get for you. For me it gets almost to the end then fails in the last few steps. Here's what I do:
I don't know if you can create a hard link from Nginx on Windows. If you can't, open up a Windows command line in Administrator mode, and use the following command from root:
mklink /D /J openscholar www\profiles\openscholar
What do you run
What do you run ./scripts/build inside of?
A Drush window?
Windows command prompt?
I had some success with the pre-built version but would like to learn this method.
I believe git comes with a
I believe git comes with a bash terminal and that's what you should use. Cygwin would also be a good option. No idea what a windows command prompt would do - I haven't regularly used windows in over a decade.