@foxy-vikvik your patch does not fix the issue is what you're saying?
overriding the timezone on the date field in the calendar view to UTC does not fix the issue for me.
nicoleannevella → created an issue.
Patch fixing the css
Patch fixing the css
nicoleannevella → created an issue.
How do I add a conflict key?
I am experiencing this exact same issue.
nicoleannevella → created an issue.
Bumping this.
Can we get a release soon?
Solved:
I just create a views attachment where the Row Apath is set to the key I needed and attach that to the main view page.
The issue this creates is it throws a fatal error if that key is not there.
I wrote a patch to fix that, uploading in a new issue.
nicoleannevella → created an issue.
figured it out!
Note I am wondering how to use a "drupal token" in the JSON FIle path in Query Settings
It states "Can use Drupal token as well. "
nicoleannevella → created an issue.
suggestion in comment #3 fixed my issue.
nicoleannevella → created an issue. See original summary → .
@salvis, I agree with @xeM8VfDh this is disappointing.
the module works with the patches on D10. But beta2 breaks the patches, and thus does not work on D10.
D9 end of life is fast approaching.
This patch fails to apply on 9.5.9
Please do not post screenshots of it passing the Upgrade Module status. It does not help.
It's a very simply patch. I'm not sure why it's not applying.
composer failed to apply this patch for me. this is the last module blocking my upgrade.
patch in comment #4 seems to be working. but does not pass the Upgrade Status module test as the version requirement in the .info.yml file needs to be updated to include ^10