Thanks! I did use that patch and everything works great but does it only work with a table display? I can't nest items (make one item a parent of the other) with a table display. It only orders at the top level. Is that a Drupal restriction?
Love the module btw, thanks for your work!
Is there any movement on this? It would be great to have!
When? We don’t want to generate additional frustrations by announcing a date and then not be able to meet this deadline.
I think you already did that when you said it would be completed before the end of the year back in December.
@DerekAhmedzai I'm am up for a fork, as long as it makes it easy to migrate from the Opigno distribution.
You'll want to look at hook_tokens and hook_token_info.
Those will let you define the tokens and define the token replacements.
pixiekat → created an issue.
Came here to say this and had the same thing on 6.1.
Webform UI is enabled but there's no button; only a source tab and an elements tab.
Adding "element/add/fieldset" to the end of the URL works though.
You also need this one for line 613 getApprovedModuleByStep()
I've had this happen too on my site with a large user base. The list to populate users on the add members to learning path form takes a while to load.
Upgraded a bunch of sites and it went smoothly. One thing I might suggest is to release a 2.x minor release requiring apitools ahead of the official 3.x release, since in some cases I had issues with trying to upgrade but getting caught in a loop where it would fail because it couldn't find the apitools service that zoomapi requires.
Oh, got it. It was a Guzzle configuration. For put() requests in Guzzle 6, you need to send ['json' => $data] as your $option. For form data, you would send ['form_params' => $data].
Might be helpful to include in the documentation (not meaning that as a demand or to be rude or anything; I just think other people might be interested so they don't have to hunt). :)
I did discover one issue, actually. I was trying to put to the Update meeting status endpoint using the put() method and I received an 400 response: Request Body should be a valid JSON
I'm passing the meeting ID as the path and ['action' => 'end'] as the $option. I can't figure out why it's happening when it was working previously.
Doing some testing and that is the case, thanks! :)
Thanks for all the work. For the record are post and deletes the same as post in such that it requires the json key in the options array?
pixiekat → created an issue.
Most likely related to https://www.drupal.org/project/drupal/issues/2982052 🐛 Allow an install hook in profiles installing from configuration Needs work , which is an outstanding issue in core.
Depending on what's changed or if it's a minor release, you should be able to alias it in your own composer.json using "drupal/state_machine": "1.6 as 1.5" until the Opigno's composer is update.
According to the release notes, there's no real breaking changes. It was just an incredibly minor release.
https://www.drupal.org/project/state_machine/releases/8.x-1.6 →
Thank you!
I had just been editing the view itself to filter out certain items but this is a welcome change.