Getting this error through Drush when running a command (and some Undefined index...through status-logs).

So I uninstalled my sub-theme,
uninstalled omega,
deleted theme folder/files,
cleared cache, ran
drush sql-query "DELETE FROM whh_key_value WHERE collection='system.schema' AND name='omega';"and
drush sql-query "DELETE FROM whh_key_value WHERE collection='system.schema' AND name='MY_THEME';"
cleared cache

Error message gone.

Reinstall omega (now alpha6) through drush.
- Errors back for omega, omega_simple_starterkit and omega_starterkit.

The following module is missing from the file system: omega bootstrap.inc:233

Also in 'Reports - logs' I now have:

Undefined index: #options in omega_preprocess_field() (line 360 of /var/www/whise/themes/omega/omega/omega.theme)

and

= Noticed some of the alpha5 patches are not in omega-functions--admin.php anymore, specifically the ones that fixed some of my previous errors around having the site in a sub-folder. For example:
realpath(".") . base_path() . drupal_get_path('theme', $theme) to
realpath(".") . '/' . drupal_get_path('theme', $theme)
from #2451267-3: Can't modify layout [#2451267-3.diff]

I guess my question is re the bootstrap and Undefined index errors, but was an thinking that it may all relate as Drupal is not able to locate key theme files.

Comments

pietpomp created an issue. See original summary.

himerus’s picture

himerus CreditAttribution: himerus as a volunteer commented
Version: 8.x-5.0-alpha6 » 8.x-5.x-dev

I can't be sure why it's saying it can't find Omega??

The undefined index in preprocess_field was solved in latest dev, one commit after alpha6 release. :(

It looks like the issues with base_path you linked were in the D7 version, and the change/fix hasn't been applied to D8. I will test an install on a subdirectory and see what it looks like.

There are definitely going to be hiccups over the next month or so as a few more alphas are released and it nears beta at which point nothing should "break" a subtheme.

pietpomp’s picture

pietpomp CreditAttribution: pietpomp commented

Cool, just to clarify it's a subfolder as in http://192.168.0.18/test/ at /var/www/test on localmachine.

Further info:
Also, tried a new install&database, D8.1.7 and fresh Omega aplha6 code. All fresh no other modules/patches.

Activating Omega gave the missing bootstrap 233 error

User warning: The following theme is missing from the file system: in drupal_get_filename() (line 233 of /var/www/test/core/includes/bootstrap.inc).

and when I cloned a sub-theme from starter kit through UI, I got these two through Reports:

Notice: Undefined variable: ttype in include_once() (line 152 of /var/www/test/themes/omega/omega/theme-settings/layout-config.php).

Warning: file_get_contents(/var/www/test/test/themes/omega/omega/style/scss/vars.scss): failed to open stream: No such file or directory in SassFile::get_file_contents() (line 66 of /var/www/test/themes/omega/omega/src/phpsass/SassFile.php).

Subtheme is there, but saving changes to active/default sub-theme gives white screen. Have to 'back' to get back into site and changes are not applied.

Built in themes work as expected.

himerus’s picture

himerus CreditAttribution: himerus as a volunteer commented

I've done 5 new installs this morning. All Drupal 8.1.7 and latest dev of Omega.

  • Installed Drupal and Omega via custom composer.json -> worked as expected using localhost domain
  • Installed Drupal and Omega via tar.gz downloads -> worked as expected using localhost domain
  • Installed Drupal and then installed Omega via admin/modules/install -> worked as expected using localhost domain
  • Installed Drupal and Omega via custom composer.json -> worked as expected on subdirectory install and url
  • Installed Drupal and Omega via targ.gz downloads -> worked as expected on subdirectory install and url

So the first three tests were on my http://d8.localhost alias I use.
The last two were using the local path http://192.168.1.xxx/drupal/docroot/

I'm completely unable to reproduce these errors.

I don't know why you're getting a broken or incomplete package.

pietpomp’s picture

pietpomp CreditAttribution: pietpomp commented

Thank you for the effort.
I was using the alpha6 pack and alpha5 before that, but can see you switch this issue's flag to dev version.
Will try dev and see what's the go.