Closed (fixed)
Project:
RELAXed Web Services
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Feb 2017 at 09:09 UTC
Updated:
17 Apr 2017 at 19:43 UTC
Jump to comment: Most recent
Comments
Comment #2
samerali commentedAnyone has solution for this issue? it's certainly blocking the whole module from working at D8.3
Comment #3
samerali commentedComment #4
jeqq commentedHere is the fix: https://github.com/relaxedws/drupal-relaxed/pull/82. It will be merged and pushed on d.o when Drupal 8.3.0 will be released.
Comment #5
samerali commentedThanks alot @jeqq.. I'm going to try it it
Comment #6
samerali commentedLooks like the pull request does work for me and the error is now gone.. for anyone want to use patch Relaxed 8.1 dev. You could use this for now: https://gist.github.com/sameronline/407c2fc115e9bbc0d53898d3a788398c
Comment #7
samerali commented@jeqq Do you mind looking at: https://www.drupal.org/node/2850649#comment-11987860
I'm using the above patch + drupal/replication latest dev version which throws this error on drush cr:
that's probably drupal/replication and not drupal/relaxed?
Comment #8
samerali commentedI was able to resolve this error by uninstalling the relaxed module and installing it again.
The 8.3 patch contained some changes that to the configs on installation and it does not seem to pick up these new changes unless module is disabled and enabled again... see https://github.com/relaxedws/drupal-relaxed/pull/82/files#diff-f4b48fdd8...
Comment #9
samerali commented@jeqq don't we need some kind of hook_update @ relaxed.install to avoid this from happening?
Comment #10
jeqq commented@samerali Thank you for testing and debugging this. I've added an update function that should load the new config.
Comment #11
samerali commented@jeqq Thankyou, I have been following your commits on github! thanks for including the test suites as well appreciated.
Comment #13
jeqq commentedComment #15
papagrandeI updated the issue summary to help search engines.
(This update worked for me. Thanks.)