@erdm

erdm → created an issue.

MR!36 tested with Drupal 10.3

Error:

Error: Call to a member function getResources() on null in Drupal\shopify\Form\ShopifyWebhooksAdminForm->buildForm() (line 38 of /var/www/html/d103test/web/modules/contrib/shopify/src/Form/ShopifyWebhooksAdminForm.php).

#0 [internal function]: Drupal\shopify\Form\ShopifyWebhooksAdminForm->buildForm()
#1 /var/www/html/d103test/web/core/lib/Drupal/Core/Form/FormBuilder.php(536): call_user_func_array()
#2 /var/www/html/d103test/web/core/lib/Drupal/Core/Form/FormBuilder.php(284): Drupal\Core\Form\FormBuilder->retrieveForm()
#3 /var/www/html/d103test/web/core/lib/Drupal/Core/Controller/FormController.php(73): Drupal\Core\Form\FormBuilder->buildForm()
#4 [internal function]: Drupal\Core\Controller\FormController->getContentResult()
#5 /var/www/html/d103test/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(123): call_user_func_array()
#6 /var/www/html/d103test/web/core/lib/Drupal/Core/Render/Renderer.php(638): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#7 /var/www/html/d103test/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(121): Drupal\Core\Render\Renderer->executeInRenderContext()
#8 /var/www/html/d103test/web/core/lib/Drupal/Core/EventSubscriber/EarlyRenderingControllerWrapperSubscriber.php(97): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext()
#9 /var/www/html/d103test/vendor/symfony/http-kernel/HttpKernel.php(181): Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}()
#10 /var/www/html/d103test/vendor/symfony/http-kernel/HttpKernel.php(76): Symfony\Component\HttpKernel\HttpKernel->handleRaw()
#11 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/Session.php(53): Symfony\Component\HttpKernel\HttpKernel->handle()
#12 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/KernelPreHandle.php(48): Drupal\Core\StackMiddleware\Session->handle()
#13 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/ContentLength.php(28): Drupal\Core\StackMiddleware\KernelPreHandle->handle()
#14 /var/www/html/d103test/web/core/modules/big_pipe/src/StackMiddleware/ContentLength.php(32): Drupal\Core\StackMiddleware\ContentLength->handle()
#15 /var/www/html/d103test/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(106): Drupal\big_pipe\StackMiddleware\ContentLength->handle()
#16 /var/www/html/d103test/web/core/modules/page_cache/src/StackMiddleware/PageCache.php(85): Drupal\page_cache\StackMiddleware\PageCache->pass()
#17 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/ReverseProxyMiddleware.php(48): Drupal\page_cache\StackMiddleware\PageCache->handle()
#18 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/NegotiationMiddleware.php(51): Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle()
#19 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/AjaxPageState.php(36): Drupal\Core\StackMiddleware\NegotiationMiddleware->handle()
#20 /var/www/html/d103test/web/core/lib/Drupal/Core/StackMiddleware/StackedHttpKernel.php(51): Drupal\Core\StackMiddleware\AjaxPageState->handle()
#21 /var/www/html/d103test/web/core/lib/Drupal/Core/DrupalKernel.php(741): Drupal\Core\StackMiddleware\StackedHttpKernel->handle()
#22 /var/www/html/d103test/web/index.php(19): Drupal\Core\DrupalKernel->handle()
#23 {main}

An installation method with Composer as an alternative to the method described in #15

Step 1:

composer require mglaman/composer-drupal-lenient

Step 2:

composer config --merge --json extra.drupal-lenient.allowed-list '["drupal/shopify"]'

Step 3: past patch( currently MR36) in composer.json

"drupal/shopify":{
                "New version of the module-issues-3414025":"https://git.drupalcode.org/project/shopify/-/merge_requests/36.patch"
            }

Step 4:

composer require 'drupal/shopify:2.0.x-dev@dev'

#MR111 worked for me. +1 for RTBC

I also experienced the same problem. The patch here might be useful.

https://www.drupal.org/project/private_message/issues/3365542 💬 Loading previous messages and listing last messages doesn't work RTBC

Yes, you're right, it's another bug, but I just wanted to point out that I saw the same error even though I couldn't use the "entity clone module". This issue may not be related to the "entity clone" module.

Hi k.prozorov,
Thanks for patch but it didn't work.
Unfortunately both 2 problems still exist.

If you really need this, you can follow this path below.
I haven't tested it with the whole site, so test it locally before using it on your production site.

*temporary solution

composer require mglaman/composer-drupal-lenient
composer config --merge --json extra.drupal-lenient.allowed-list '["simshaun/recurr"]'

composer require 'simshaun/recurr:^5'
composer require 'drupal/smart_date:4.1.x-dev@dev'
---------------------------------------------------

erdm → created an issue.

erdm → created an issue.

Patch 25 tested on env. Drupal 10.1.2 - PHP 8.1

Checking patch composer.json...
Checking patch js/fivestars.js...
Checking patch js/like.js...
Checking patch js/useful.js...
Checking patch src/Plugin/VotingApiWidgetBase.php...
error: while searching for:
      $query->condition('timestamp', time() - $timestamp_offset, '>=');
    }

    $votes = $query->execute();
    if ($votes && count($votes) > 0) {
      $vote = $storage->load(array_shift($votes));
    }

error: patch failed: src/Plugin/VotingApiWidgetBase.php:218
error: src/Plugin/VotingApiWidgetBase.php: patch does not apply
Checking patch votingapi_widgets.info.yml...
Checking patch votingapi_widgets.libraries.yml...

Testing For 46

Module can not be installed via drush or UI

PHP Fatal error:  Declaration of Drupal\conditional_fields\Routing\RouteSubscriber::getSubscribedEvents() must be compatible with Drupal\Core\Routing\RouteSubscriberBase::getSubscribedEvents(): array in /var/www/html/test46/web/modules/contrib/conditional_fields/src/Routing/RouteSubscriber.php on line 77
 [warning] Drush command terminated abnormally.

No, it was just an idea of how Unified Date would generate more benefits for ecosystem.

Bravo, You completed well with other options.
Actually, this idea came from here.
There is still no stream(activity feed) module or stable notification system in the Drupal ecosystem. Collecting all activities & crud operations in a single stream and sorting with Unified Date. Just it.
If it gives support for other entity types, Unified Date plays an important role in this kind of scenario.

Sorry, my mistake...
I'm testing patches one by one in different versions. You could call it a kind of hobby.
I mixed up the issues. I don't know how it happened but I posted it here.
I tested this patch ( issue-3333559: D10 compatibility) 📌 [9.2] Remove jQuery dependency from the once feature RTBC for D10 which didn't work.

Sorry again,
Shifali Baghel & gillesbailleux .Thanks for effort....

erdm → created an issue.

Hi Shifali Baghel ,
Thanks for patch.
I tested with Drupal 10.1

erdm → created an issue.

#8 Could not apply patch!

There should be a customized warning message to show before or after this ban as to why it happened.

Hi Jurgen,
I know it's not an ECA related problem.
Since I use ECA for notifications in the above scenario, I wanted to get advice by thinking if I can solve it with ECA again.

I will listen to your advice. By the way, I would be very happy if you could evaluate this scenario at tube.tchncs/ecaguide

Thanks

erdm → created an issue.

Error with Merge request !4279

ParseError: syntax error, unexpected single-quoted string "nid", expecting identifier or variable or "{" or "$" in Drupal\Core\Extension\ModuleHandler->loadInclude() (line 224 of /home/erdm/web/newD10test/public_html/D10test3/web/core/modules/forum/forum.install) #0 /home/erdm/web/newD10test/public_html/D10test3/web/core/includes/install.inc(86): Drupal\Core\Extension\ModuleHandler->loadInclude()

Hii sidharth_soman;
Thanks, It's working without any error. I didn't get an error like you mentioned above.
Drupal test version Drupal 10.1.1. Tested with bario theme 5.5 and local bootstrap library 5.3
I'm testing them all on linux. Could be from windows environment-libraries, not sure.

erdm → created an issue.

Thanks Jurgen, It works.

erdm → created an issue.

erdm → created an issue.

I see the same issue even though I'm not using the entity clone module.
I don't think it's related to the entity clone module.
It happens when I try to delete messages.(/admin/config/message/message_delete_multiple)

erdm → created an issue.

Actually, I opened this message separately under the forum module. Because in the new drupal plans, forum module will be separated from the core and I thought it would be more accurate to follow it there. But it is taken here to be followed under D9.5 dev version. There should be something they know. Not a big deal.
I didn't use the one in the Core module, I installed it with composer and patched it in the separate forum module.

Maybe it is necessary to create a separate node type for forums. Considering for the future, maybe the support will be completely removed.
When I create it as a node type, the error goes away, but I'm not sure if it will get as much performance as the forum module.

Checking patch forum.install...
error: while searching for:

  return $schema;
}

error: patch failed: forum.install:175
error: forum.install: patch does not apply
Checking patch forum.install...
Hunk #1 succeeded at 161 (offset 2 lines).
error: while searching for:
 function forum_update_9100() {
  $connection = \Drupal::database();
  if ($connection->schema()->tableExists('forum_index') && $connection->databaseType() != 'sqlite') {
    $connection->schema()->addPrimaryKey('forum_index', ['nid']);
    return 'Added primary key to the forum_index table.';
  }
 }
error: patch failed: forum.install:182
error: forum.install: patch does not apply
Checking patch forum.install...
error: while searching for:
 */
 function forum_update_9100() {
  $connection = \Drupal::database();
  if ($connection->schema()->tableExists('forum_index') && $connection->databaseType() != 'sqlite') {
    $connection->schema()->addPrimaryKey('forum_index', ['nid', 'tid']);
    return 'Added primary key to the forum_index table.';
  }

error: patch failed: forum.install:182
error: forum.install: patch does not apply

erdm → created an issue.

erdm → created an issue.

erdm → created an issue.

@tim-diels

Before patch,

Target filter is not being filtered. It shows the whole list with other values belonging to unselected controller fields.

After Patch

Only those that are filtered by selection(Barcelona) are displayed.

I hope the explanation and screenshots were sufficient.

Hi Niles,
Patch works.
Nice work. Thanks

Ok. I'm gonna test it now.

It would be greateful if you add multi-controller feature.

Thanks

Sorry , I've sent the wrong image.

There is no problem with the view preview. Even multi-controller is working.

Here's previews with "Display all results for the specified field"

Barcelona id is 34 (Players: Messi,Neymar,Figo)
Liverpool id is 37 (Players: Muhammed Salah)

Single Controller

Multi-Controller

Note:FYI. There's other problem when you're editing the node. Target filter is not being filtered. It shows the whole list with other values belonging to unselected controller fields. Of course it would be better to open another issue.

Hi niles38,
I think I solved some parts but not all.

What I have changed is (form_filter_fields.module)
I added "((string)" to the line blocks below...

148: $straight_html = trim(strip_tags((string)$rendered->jsonSerialize(), "<li>"));
156:  $rough_html = trim(strip_tags((string)$rough_html));
162 :    strip_tags((string)$rough_html_pieces[1])

Now it's working.Log warning messages and The referenced entity (taxonomy_term: ABC) does not exist warning message is gone.

But:

Warning is gone but it's still not working with multi-value controller(field_team). It's working with controller field with limited 1 value.
For example I can't achieve if I want to get Barcelona and Liverpool players together.When I change controller field to unlimited values(managed field), target field can not be filtered. All players are on the list.

Single controller is working after code revised.

Screenshots

View

Term name

Contextual Filter

erdm → created an issue.

Hi Duvan,
I tested the module but it does nothing even I've tested it with your sample. Also I don't use Field Group Ajaxified Multipage.
What's your seetings for contextual filter. Maybe it's not working because of a contextual filter here. Or any idea why it's not working?

The same problem occurs even with version 3. You see the same problem not only with "add members" but also when adding media entities.
All entities are listed twice.

erdm → created an issue.

@sudesh
PbT Test version: 3.1.21
Drupal version : 10.0.7

Test PbT module info.yml

name: 'Permissions by Term'
description: 'Restricts access to nodes and taxonomy terms via user to term relations.'
dependencies:
  - 'drupal:system'
  - 'drupal:field'
  - 'drupal:taxonomy'
  - 'drupal:path_alias'
type: module
core_version_requirement: '^9'
# version: '3.1.9'
package: 'Permissions by Term'
configure: permissions_by_term.settings

# Information added by Drupal.org packaging script on 2022-11-09
version: '3.1.21'
project: 'permissions_by_term'
datestamp: 1668009537

Test for 3289053-30.patch

patch
Checking patch composer.json...
Checking patch modules/permissions_by_entity/tests/src/Kernel/EntityAccessCheckTest.php...
Checking patch modules/permissions_by_entity/tests/src/Kernel/EntityPublicationTest.php...
Checking patch permissions_by_term.info.yml...
error: while searching for:
  - 'drupal:taxonomy'
  - 'drupal:path_alias'
type: module
core_version_requirement: '^9'
version: '3.1.9'
package: 'Permissions by Term'
configure: permissions_by_term.settings

error: patch failed: permissions_by_term.info.yml:6
error: permissions_by_term.info.yml: patch does not apply
Checking patch permissions_by_term.module...
Checking patch src/Event/PermissionsByTermDeniedEvent.php...
Checking patch src/Listener/KernelEventListener.php...
Checking patch src/Service/AccessCheck.php...
Checking patch src/Service/TermHandler.php...
Checking patch tests/src/Kernel/AccessStorageTest.php...
Checking patch tests/src/Kernel/MultilingualTest.php...
Checking patch tests/src/Kernel/NodeEntityBundleInfoTest.php...
Checking patch tests/src/Kernel/PBTKernelTestBase.php...
Checking patch tests/src/Kernel/TermHandlerTest.php...

erdm → created an issue.

Nice work.Thanks @sagesolutions .
It would be grateful if this blocking system integrated with Version 3.

erdm → created an issue.

erdm → created an issue.