artistro08/tailor-starter

Installation / Seeding Error

baberuth22 opened this issue · 4 comments

When I run the following command:

php artisan theme:seed artistro08-tailorstartertheme --root

I get the error:

Seeding Theme...
Importing Blueprints
Migrating Content Tables

  • Submissions: Content\Forms\Submissions [xc_912c5956878d11ed9699df30dbea9de3c]
  • Forms: Content\Forms [xc_f04b58ea6d8011edaa98d348ccf890efc]
  • Pages: Content\Page [xc_698afed670f147dd9dcfdc2a0f903ff2c]
  • Product Categories: Content\Product\Category [xc_c59d8718011511ed98c7806b464850f0c]
  • Product Properties: Content\Product\Properties [xc_01d7c870014411edb0084dca43b459abc]
  • Orders: Content\Orders [xc_a3436526073e11eda6a5a871a8b74bb8c]
  • Products: Content\Product [xc_2a9a76d0010c11ed90b6fc95f7401555c]
  • Post Categories: Blog\Categories [xc_a15e9d9eac3711ed9eddc1c4cb64ca59c]
  • Post Authors: Blog\Authors [xc_a181b687ac3711ed87f63fd40555bea7c]
  • Posts: Blog\Posts [xc_a113a242ac3711ed82e2cdd679785a5cc]
  • Icons: Content\Icon [xc_2dcfff9463ce4c7ea8a9b032bec5ec8ac]
  • Secondary Menu: Content\SecondaryMenu [xc_1084631fd54d11ec9fa33b373fee9fc6c]
  • Main Menu: Content\MainMenu [xc_271c984c2b0d498ca7826afaf39ee95dc]
  • Social Menu: Content\SocialMenu [xc_614a6aefc642427fa28c343032f19debc]
  • Events: Content\Event [xc_817ac186fc5d11ec86016e37945c2034c]
    Importing Data

In ThemeSeed.php line 149:

[/Users/bryansaltzman/www/valetsites/ballerstreet/themes/artistro08-tailorstartertheme/seeds/data.yaml] Global handle [Content\Set
tings] not found

In GlobalRecord.php line 83:

Global handle [Content\Settings] not found

Can you tell me what troubleshooting things you've already tried? Want to get to the bottom of why it's doing that.

Closing due to no activity

I had the same issue on a fresh October install.
I just ran the command again and it worked. For whatever reason it seems the blueprint isn't quite ready by the time it starts seeding data. Or maybe a temporary file locking issue?
It would be useful to mention this might happen in the install docs if a fix isn't available.

Ahh okay, This may be a bug with October's way of importing blueprints