Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Undefined index: assetPath upon upgrade #15

Closed
1 task done
ganar opened this issue Feb 6, 2018 · 2 comments
Closed
1 task done

[BUG] Undefined index: assetPath upon upgrade #15

ganar opened this issue Feb 6, 2018 · 2 comments

Comments

@ganar
Copy link

ganar commented Feb 6, 2018

Submit a bug report or feature request

  • This is a bug report

Bug report

Subject of the issue

Describe your issue here.

"Undefined index: assetPath" after upgrading to the last version. switching back to 0.3.1 solves the issue

screen shot 2018-02-06 at 12 34 59 pm

Your environment

  • Running on Docker with no isssues
  • OSX High Sierra
  • Chrome and Firefox

Steps to reproduce

Updated from 0.3.1 to the most recent version

Expected behaviour

the Template should not have problems with assetPath

@robbinjohansson
Copy link
Owner

robbinjohansson commented Feb 6, 2018

Hi,

It looks to me that the assetPath variable is missing in haywire.yaml, would you mind paste the code of that file for me to have a look?

This line was added in 0.3.2 and is needed for the asset cache busting functionality to work.

There have been some issues (#14) after asset cache busting was implemented in 0.3.2 so I might have to rollback the update. But please let me see the contents of haywire.yaml of your site/project first please, maybe assetPath is just missing/incorrect.

Thanks for using the theme, sorry for the inconvenience of the update.

@robbinjohansson
Copy link
Owner

robbinjohansson commented Feb 9, 2018

Fixed in 0.3.4.

Go ahead and update:

$ bin/gpm update haywire

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants