-
Notifications
You must be signed in to change notification settings - Fork 71
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
taxonomy_term.resource_types.default already exists #924
Comments
Please take a look. Islandora Feature is not installing via ansible. |
@Natkeeran I think I'll try to sort out a local install before attempting something with ansible. |
@Natkeeran That works for me locally, but can't really test with vagrant until it's merged and in packagist. |
@dannylamb Should we merge it and test. I can test this after 12 pm. |
@Natkeeran Go for it and I'll run a |
@dannylamb Actually, I had tried that yesterday. That did not work for me! But will try again. |
@Natkeeran I'm not sure if it will resolve things 100%, there's likely a few more steps we'll have to make. I ran into the issue yesterday when attempting to rebase my work for #888, and this got me a step further. |
The fact that we're working around that crazy content translation/entity update bug isn't helping make diagnosis any easier, too. |
@Natkeeran Now that I think about it, maybe I can do what we did with #920 and push a branch to foundation's repo. Then we can point claw-playbook at it and test. |
@Natkeeran I pushed up https://github.com/Islandora-CLAW/islandora_demo/tree/issue-924 and am using it to test with claw-playbook. |
@Natkeeran Tested with a fresh |
I am assuming the following issue is related to the original translation related issue.
|
@Natkeeran Yeah, should be. After the giant wall of red is there a blue |
Thanks @dannylamb |
Seeing the following ansible error. This maybe a regression issue related to this merge: https://github.com/Islandora-CLAW/islandora_demo/pull/2.
The text was updated successfully, but these errors were encountered: