Library missing

Trying to install, get this:

Starting Drupal installation. This takes a few seconds ...           [ok]
WD php: Exception: OAuth library:                                    [error]

Please download OAuth.php, extract the archive and copy the contents
to the following location:sites/all/libraries/oauth. Make sure the
file, OAuth.php, is located atsites/all/libraries/oauth/OAuth.php. in
install_verify_requirements() (line 753 of

The following works, running inside sites/all/libraries/oauth:

wget https://github.com/juampy72/OAuth-PHP/blob/master/OAuth.php

Field problem

After fixing above, trying again. Here's what I get; included the command I typed, and all the output:

[@cor:~/cis]$ drush site-install cis --account-name=admin --account-pass=aaa --db-url=mysql://bbb:ccc@localhost/ddd
You are about to DROP all tables in your 'admin_cis' database. Do you want to continue? (y/n): y
Starting Drupal installation. This takes a few seconds ...           [ok]
WD php: Warning: Invalid argument supplied for foreach() in          [warning]
_features_restore() (line 866 of
/{path}/cis/profiles/cis/modules/contrib/features/features.module).
WD php: Warning: Invalid argument supplied for foreach() in          [warning]
_features_restore() (line 866 of
/{path}/cis/profiles/cis/modules/contrib/features/features.module).
WD php: Warning: Invalid argument supplied for foreach() in          [warning]
_features_restore() (line 866 of
/{path}/cis/profiles/cis/modules/contrib/features/features.module).
WD php: Exception: Invalid field name given: field_sections is not a [error]
Field Collection field. in FieldCollectionItemEntity->__construct()
(line 210 of
/{path}/cis/profiles/cis/modules/contrib/field_collection/field_collection.module).
WD php: Warning: Cannot modify header information - headers already  [warning]
sent by (output started at /var/www/drush/includes/output.inc:37) in
drupal_send_headers() (line 1212 of
/{path}/cis/includes/bootstrap.inc).
Exception: Invalid field name given: field_sections is not a Field Collection field. in FieldCollectionItemEntity->__construct() (line 210 of /{path}/cis/profiles/cis/modules/contrib/field_collection/field_collection.module).
Drush command terminated abnormally due to an unrecoverable error.   [error]
[@cor:~/cis]$

field_sections is in cis.info line 251, and a bunch of times on cis_types.info, if that helps.

Comments

btopro’s picture

Status: Active » Needs work

in digging into an easy way of doing this without adding a white-listed library, I realized that LTI tool provider (the thing mad above) and the OAuth module on d.o. are both referencing the same fork of the google provided OAuth base library. I've put in a patch to the LTI developer to allow for inclusion of OAuth module to use for making its requests. If this goes through then it'll be very easy to include both modules in an install routine successfully:

#1930402: OAuth Module support (patch included)

That covers the first issue.

The second is related to features exportability / importability of nested field collections. Unfortunately this bug seems to keep popping up in that project and at the moment I'm not sure of a work-around that is desirable, will need to dig into it deeper as to why this would import / revert (it was in an earlier version and something changed in either entity or fc to make this no longer the case).

mobcdi’s picture

Got the error Invalid field name given: field_sections is not a Field Collection field during install but revisiting the installerpage seemed to allow me get to the admin setup page and complete the setup steps in case its useful to anyone encountering this until a workaround is in place

btopro’s picture

it will let you past but it's not actually doing everything it needs to do in the install as a result. The issue is that the part that's failing is called cis_types which includes content type definitions for everything in the site. Some of them will still install correctly but largely they want. This issue is related to the field collections module which is on my roadmap of things to seriously hunt down. I may also try and isolate the Course content type from everything else for this reason as its the thing that contains the field collections. It's unfortunately a known issue with field collections related to entity api and will require some serious digging to root out.

btopro’s picture

Version: 7.x-1.0-alpha2 » 7.x-1.x-dev
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.