orakili β made their first commit to this issueβs fork.
Patch #4 converted to MR and merged. Thank you.
orakili β made their first commit to this issueβs fork.
Thank you but this defeats the purpose of this module which is to provide an unconstrained field for the displayed user name. If uniqueness is needed then there is already the default user name field.
If this is made optional, then I'll reconsider it.
Closing this. PHP < 8 is not supported anymore.
Still unclear how to reproduce the issue.
orakili β changed the visibility of the branch 3364019-add-feature-to to hidden.
orakili β made their first commit to this issueβs fork.
Merged.
Tested with simple layouts and it seems to be working well. The code is clean. Thank you.
This should be handled via FieldProcessor plugin. See https://www.drupal.org/project/content_entity_clone/issues/3364019 β¨ Add feature to clone entities by reference fields Active .
Marking this issue as duplicate.
@davisben
Thanks for the proposed change. It's currently not working because `amazon_ses_hook_queue_info_alter()` should be `amazon_ses_queue_info_alter()`.
With the proper function name, the queue is indeed not processed during cron when queueing is not enabled and processed otherwise.
@opregonerog Thanks for reporting this. Could you provide some context and steps to reproduce the issue?
We faced the same issue and the changes from the MR seem to have fixed the problem.
Attaching the a patch for Drupal 10.3.2 backported from the MR as well since this version was also affected.
Patch from #104 didn't apply cleanly on 10.3.1. Here's an updated patch for this version back-ported from MR 553.
orakili β created an issue.
orakili β created an issue.
This doesn't seem to work with some entity reference widgets like the media library or the inline entity form β module.
@Murz, would you be able to indicate with what widgets this plugin worked?
Thank you for fixing the typos.
I couldn't reproduce the issue with the `#active` key but I didn't see any adverse effects of having it defined so that looks good to me. Thanks.
MR to separate deleting a configuration from enabling/disabling it: https://git.drupalcode.org/project/content_entity_clone/-/merge_requests/7
orakili β made their first commit to this issueβs fork.
MR based on patch from @dieppon: https://git.drupalcode.org/project/content_entity_clone/-/merge_requests/6 with some refactoring to reduce duplicate code.
Note: this will be adjusted to handle translation when tackling https://www.drupal.org/project/content_entity_clone/issues/3423495 π Cloning a translation of an entity loads the original entity Needs review .
orakili β made their first commit to this issueβs fork.
@dineshkumarbollu @ad0z Thanks for testing. I've updated the description to better reflect what is happening. The implied issue and the steps to reproduce it were wrong.
orakili β created an issue.
Sorry the patch in #76 was not replacing the file_validate_image_resolution
validator properly. Fixed in this new patch.
Updated patch for 10.2.x using the new validation constraints from https://www.drupal.org/node/3363700 β
Created a merge request. Note that it's against the current 8.x-3.x
branch which contains the latest code.
Ideally, a new 4.0.x
branch should be created to be consistent with the social_api
and social_auth
modules and the MR changed to target it.
Similarly, for consistency, once approved, a new 4.0.0
release should be created.
orakili β created an issue.
I cannot reproduce the issue, the module works fine on 9.5.9 sites for me. You can try it on https://simplytest.me as well to confirm.
Please provide more information.
For example try implementing a hook_preprocess_menu_local_task
and check what is in $variables['element']['#link']['localized_options']
, it should be something like:
'query' => [
'content_entity_clone' => XXX,
],
New release available: 1.0.2 with the fix.
New release available: 1.0.2 with the fix.
orakili β made their first commit to this issueβs fork.
As suggested in the description of
https://www.drupal.org/project/paragraphs_viewmode/issues/2971172
π
Does not work with Configuration Translations
Fixed
, it may be more appropriate to alter the configuration schema to use string
instead of text
so that the display mode IDs are not translated or mark those fields as explicitly non translatable with translatable: false
.
Here's the quote from the schema cheat sheet ( https://www.drupal.org/docs/drupal-apis/configuration-api/configuration-... β ):
The label, plural_label, date_format and text types are defined as translatable: true.
The attached patch changes the schema (just needs a cache clear to take effect) and reverts the main change from https://www.drupal.org/project/paragraphs_viewmode/issues/2971172 π Does not work with Configuration Translations Fixed .
Existing sites where the view modes IDs in the config were translated may need to update their config, I'm not sure.
orakili β created an issue.
Here's a patch. Please review.
orakili β created an issue.