🇬🇧United Kingdom @joekers

breidert → credited joekers → .

I've changed the priority to major as this issue allows users to prolong their license without renewing. Depending on the implementation, it would allow users to bypass paying for the renewal and/or retain user roles that they should no longer have.

+1 from me too!

Had an issue with the latest changes not being merged in but all good now.

I wanted to get this in the dev branch ready for #3161731: Add basic test coverage for the widgets and plugins → so I've made the changes related to the feedback I gave.

There were a couple of items flagged by phpcs but we can fix those later.

Thanks @rahulrasgon and @jasjeet for creating and working on this issue.

I've merged the MR into dev. Thanks!

Thanks for raising and fixing the issue - merged into dev.

joekers → made their first commit to this issue’s fork.

PR merged into the dev release - thanks for your work on this!

Great stuff! Hopefully we can make a new release soon to include it.

@handkerchief could you try using the dev release and see if that fixes the issue?

The issue should've been fixed in 🐛 Configuration schema for "Enable extra settings" (title,pagination,...) incorrect Fixed

Thanks for raising this issue @handkerchief. I've been able to recreate the issue and unfortunately, it's also the same for the "Offset results" and "Limit results" options.

I have a feeling it's something related to the schema updates that have been added and the field types for these options but I'm still digging into it to confirm.

Thanks for raising the issue and for the fix - I've committed it to the dev branch.

Also thanks to those for testing it.

Committed and created new release.

Committed and created a new release.

Committed and created a new beta release.

Patch applied to the 8.x-2.x dev branch.

Thanks @ckng for the reroll - this was based on the 2890844-65.drupal.patch and now applies cleanly to 10.2.x

Committed and created a new release. Thanks.

Thanks @martin_klima for the info and patch - I'm in the same situation as you with tracking changes.

The patch is working well for me but the performance is a bit concerning, though it's more important that I have the messages kept as I run a set of migrations daily and need to know when there are issues.

Thanks Volodymyr.I - I've committed the patch to the dev branch and will tag a new release.

Thanks for reporting this issue milton_segretti - I've merged the patch in.

Thanks for fixing the typos - marking RTBC

I monitored Room 1 | 3.8 The Lounge

I monitored Room 1 | 3.8 The Lounge

I monitored Room 5 | 3.2 A & B

I monitored Room 6 | 3.1 C & 3.2 C

I monitored Room 6 | 3.1 C & 3.2 C

I monitored Room 1 | 3.8 The Lounge

Monitored Room 5 | 3.2 A & B

Monitored Room 5 | 3.2 A & B

I attended this

The entity_value plugin here was the key for me - thanks @very_random_man!

The query is also affected by this issue - when the saved search is created, the query doesn't always have the conditions applied when using a view that has AJAX enabled.

As per the comment on [3315790-4] the active query doesn't have the filter applied from the AJAX call.

I've reviewed the PR and added some comments.

I've tested the patch and it works well - the onPaid event is no longer called twice.

After the changes have been made on the MR I can mark this as RTBTC.

I'm not really sure what the issue with composer is but I think it's unrelated so marking as "needs review".

joekers → created an issue.

This was a site-specific issue where access to the node was controlled in an access hook. Paragraphs checks for 'view' access on the entity and then its parent, at this point it was forbidden, and then showed empty in the REST feed.

joekers → created an issue.

@cburschka I think what you're saying is right - the sub-module should cover entity reference revisions, however in my case, on the export nothing is printing for this type of entity. I'm not sure if it's best to create a new issue for it?

joekers → created an issue.

Just wanted to comment in case it helps anyone else out - when using this module with the Session Limit → module, the '/session-limit' path can be added so that they work together.

The pass_reset_UID never seems to be in the session so this isn't working for me. Am I missing something, or maybe there was a change to core that removes it from the $_SESSION?

Patch from #65 is working for me too - on 9.4.4. Cheers!