🇮🇳India @junaidpv

Same as #6 (MR !23) but in classical patch form for easy applying in composer based build setup we use here.

Re-rolled for the 2.0.0-beta2 and latest 2.x branch.

It now just works for body fields??

The original patch I posted in #23 were supposed to work with any long text field with summary. But I see it now evolved lot more but restricted to just body fields as there are some hard coding for body fields. Definitely it needs to be a generic one.

Faced this bug. I confirm patch #5 helped to solve the issue.

Probably thy are compound errors specific to your site. I am unable to reproduce it here.

Could you please let me know the steps that can reproduce those errors. Also, please try it on a fresh site.

Thanks for getting back. It really helped. I appreciate the help.

I have applied a fix and a made a new release.

Please use the latest version 2.1.5 of this module. Hope it helps.

Please post the link to that webpage if that is available for public.

Or probably you will be having JS error in the browser console. Please post that error message here.

Thanks!

I appreciate the concern. Unfortunately only the current way helped to solve the original problem, to crop same image in multiple places. Please post if you have a better idea we can pursue.

Meanwhile, I am closing this until then.

Back porting #22 for Drupal 10.1.x.

I am facing same issue as the scenario 1 given in comment #11. Rebuilding the cache did not help.

Verified that above patch is no longer working.
I improved it. Now it is working.

Getting similar error. Running for the wysiwyg_template → against its 3.0.0-rc2 tag. On a Drupal 10.2.

Just re-rolled #20 for 10.2

Faced same issue with the crop_image → module as a field widget from that module extends FileBrowserWidget from the entity_browser module. I already made a new release of the crop_image module to fix the issue.

So, any other module out there extending plugins of the entity_browser module are going to get hit with this. Those module will be required to update anyway.

We tried using the Fullcalendar Block instead of using this patch. But that module cannot be used as a replacement, especially when we want to have views exposed form. Also we need to configure it in two places, and configuring the date filter is confusing.

As the patch got rejected here. We decide to create a separate module to have this feature. It is Fullcalendar Dynamic → . It is mostly a fork of the fullcalendar_view module. Please have look and please feel free to submit patches to fix any issues you encounter.

Re-rolled patch for the latest release 4.0.0

Re-rolled for the latest release 4.0.0

Re-rolled for latest release 2.1.0.

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

Thanks!
Made a new release supporting D10, including this fix.

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

Just rerolled #30 for 10.1.x

Exactly same as #47, just re-rolled for 10.1.x

I don't understand change in #11 thus just re-rolling #2 for 10.1

I don't see isDuplicate method in EntityBase class or anywhere other than in the jsonapi module which is on a completely different class.

What version of the Drupal you using?

Or probably it came from another patch you using?

I am facing same issue with a migration from D7 to D9.5.

@huzooka where did you set value for "needs_resave" ?

I developed a patch implementing this feature as well as additional other customization. Please see ✨ Customize display of signup fields Needs review .

I implemented it. It allows this customization in signup block configuration settings:

• Order of fields
• Control label display
• Add custom field classes
• Add custom field wrapper classes
• Set other additional attributes for the fields

Sample screenshot:

junaidpv → created an issue.

My profile2 type migration failed because somehow the profile2 type configuration in D7 having "roles" property with empty (0) for all non-selected roles. Filtering roles property from source solved the issue.

Here is the updated patch.

@Nupur Badola please open a new bug and attach the patch if you have.

Here is the working implementation with the help of a patch ✨ Provide Page and Page Variant as context values while rendering each component in the Layout Needs review for the Page Manager module.

junaidpv → created an issue.

Here is a very simple patch implementing it. But I feel it may to be correct place to add the content values. Please feel free to improve it.

junaidpv → created an issue.

Re-rolled for release 2.33.

Just a reroll of #18 for current 9.5.x

Try fixing CCF.

Building on #44. Adding similar improvement as #38 but to the datetime filter in core datetime module.

We were having this requirement and this thread had came in my search result. We could develop a solution. Hopefully people looking for a solution will find this helpful.

The solution is with help of a ViewsArgumentDefault plugin. It is somehow like an extended version of "User ID from logged in user" in user module. I created it like a completely new plugin. But I guess we can just improve existing "User ID from logged in user".

It is generic user module related plugin. Can be used for other related user cases. So, no need to go into media system.

Steps to use this:

1. Apply the patch to Drupal core
2. Clear cache
3. Add "Authored by" contextual filter for Media items.
4. On that contextual filter settings dialog. Under "When the filter value is NOT available". Choose "Provide default value" option.
5. Then select "User ID from logged in user with skipping for selected roles" as type.
6. Select roles you want to grant access to view items,
7. Make sure the "Skipping value" setting matches with the "Exception Value" under "Exceptions" field set.

@Kris77, Yes, that was by mistake. I uploaded the correct one in #3.

Same as #50 but handling "Undefined variable $element" warning messages additionally.

Re-rolled for current branch.

Sorry, I attached wrong file in #2.

Here is the fix.

junaidpv → created an issue.

Facing same issue.

Here is the fix.

junaidpv → created an issue.

#196 used to work for me. But now I also need patch from #3293908-5: Expose Layout Builder Sections to entity view displays (jsonapi/entity_view_display/entity_view_display) → to work the importing back the content with the layout builder overriden settings.

Exporting works fine with #191, but it fails with this message when try to import the exported node with layout builder settings:

[error] Drupal\Component\Plugin\Exception\PluginNotFoundException: The "" plugin does not exist. Valid plugin IDs for Drupal\Core\Layout\LayoutPluginManager are: layout_twocol_section, layout_threecol_section, layout_fourcol_section, layout_onecol, layout_twocol, layout_twocol_bricks, layout_threecol_25_50_25, layout_threecol_33_34_33, radix_bryant_flipped, radix_bartlett_flipped, radix_bartlett, radix_boxton, radix_brenham_flipped, radix_brenham, radix_brown, radix_bryant, radix_burr_flipped, radix_burr, radix_geary, radix_harris, radix_hewston_flipped, radix_hewston, radix_mccoppin, radix_moscone_flipped, radix_moscone, radix_phelan, radix_pond, radix_rolph, radix_sanderson_flipped, radix_sanderson, radix_selby_flipped, radix_selby, radix_sutro_double, radix_sutro, radix_taylor_flipped, radix_taylor, radix_webb_flipped, radix_webb, radix_whelan, vefl_onecol, layout_builder_blank in Drupal\Core\Plugin\DefaultPluginManager->doGetDefinition() (line 53 of core/lib/Drupal/Component/Plugin/Discovery/DiscoveryTrait.php).

I noticed the exported layout builder settings part having extra level of "section". Here is the patch fixing that issue. Then it worked with importing node with same layout builder settings.