Live feed

Thank you for this, I have put links on the module's front page. much appreciate the help here.

@kaaarrrtik

I replicated the issue and your patch in the MR works fine for me!
Great work
Moving it to RTBC

@kaaarrrtik

I replicated the issue and your patch works fine for me!
Great work
Moving it to RTBC

Thanks, please proceed with MR's here!

Thanks, this is a good idea!
Added ckeditor_drupalbreaks

I have reviewed it, and the error seems to have been resolved. I am attaching a screenshot for reference. Moving it to RTBC.

@kevinquillen is fakeobjects planned to become Drupal 11 compatible? Otherwise I think it would make sense to put some information on the module page that the module is deprecated?

Some other modules depend on this and can't be made Drupal 11 compatible, but I could neither find a statement if it's planned, nor activity in the D11 compatibility issue.

Thank you for your feedback! :)

thanks auto bot team yeah!

anybody → created an issue.

@dsnopek any plans to finish this and make the module D11 compatible? Or is the module unmaintained?
Thanks! :)

The MR !26 looks good.
@atul_ghate Can you please resolve the merge conflicts?
Also kindly update the commit message to use the correct issue ID.

Thanks.

Tried out the MR, This seems to be a solid way of defining the top bar elements. Thanks @plopesc!

anybody → created an issue.

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

I have reviewed the issue and verified that all PHPCS issues have been resolved. The GitLab CI pipeline is passing with no phpcs errors. Based on this, I am moving the issue to RTBC.

Simple rebase, so restoring RTBC

Patch for 2.0.0-beta8

rajeshreeputra → opened merge request !20

Would there happen to be a way to reproduce this?

There is an issue with creating cases where one or more of the timeline activities has users pre-assigned (ie assigned by default in the Case Type).

I tried adding a configuration similar to this although I am unable to reproduce this - https://monosnap.com/direct/yjflNRZtIEqndOWuaPWot8mpeTJ14p.

As a side note, there are fixes for CE 4.0.x. Might be worth a try to see if it still happens on CE 4.0.x

1. Merged 11.x into the branch
2. Retested with Footnotes module (disabling the fix that the module itself is applying)
3. Balloon within modal appears again:

Automatically closed - issue fixed for 2 weeks with no activity.

I think hook_entity_bundle_create is meant to be in the entity_crud group too, but the doc has @see instead of @ingroup, which we should fix too. That would give us the following extras:

• Drupal\field_ui\Hook\FieldUiHooks::entityBundleCreate()
• Drupal\jsonapi\Hook\JsonapiHooks::entityBundleCreate()
• Drupal\entity_schema_test\Hook\EntitySchemaTestHooks::entityBundleCreate()

And some more for the list in #4:

• \Drupal\field_ui\Hook\FieldUiHooks::entityViewModePresave
• \Drupal\field_ui\Hook\FieldUiHooks::entityFormModePresave
• \Drupal\field_ui\Hook\FieldUiHooks::entityViewModeDelete
• \Drupal\field_ui\Hook\FieldUiHooks::entityFormModeDelete

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

@ugintl try both, you'll very easily understand the differences.

No concerns here, looks fine to me! I haven't actually tried re-indexing. Minor comment added only

eswiderski → created an issue.

ajitdalal → opened merge request !8

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

Missed a few that don't have the right docs, i.e. "Implements hook_ENTITY_TYPE_":

• Drupal\block_content_test\Hook\BlockContentTestHooks::blockContentInsert()
• Drupal\block_content_test\Hook\BlockContentTestHooks::blockContentPresave()
• Drupal\block_content_test\Hook\BlockContentTestHooks::blockContentUpdate()
• Drupal\block_content_test\Hook\BlockContentTestHooks::blockContentView()
• Drupal\config_test\Hook\ConfigTestHooksHooks::configTestDelete()
• Drupal\config_test\Hook\ConfigTestHooksHooks::configTestInsert()
• Drupal\config_test\Hook\ConfigTestHooksHooks::configTestLoad()
• Drupal\config_test\Hook\ConfigTestHooksHooks::configTestPredelete()
• Drupal\config_test\Hook\ConfigTestHooksHooks::configTestPresave()
• Drupal\config_test\Hook\ConfigTestHooksHooks::configTestUpdate()

This is great, nice to be able to handle giant single nodes, e.g. guides or books perhaps. Added some comments to the MR, but the only general thing is I think we probably need to make this an opt-in given there are some less configurable hosts well used in the drupal community like Pantheon that have very infrequent cron

@larowlan, Worked on the MR comments.
Kindly check :)

Gitlab CI is implemented properly ~~ not sure whether we need to handle other fixes, still marking this one RTBC as all changes doesn't impact.

Please review.

I also meant to change this to un-assigned.

Hello mkalkbrenner
Thanks for you response. I have checked composer file and the issue was related to solarium outdated version. I have now updated the solarium version and the solr cron running now. Thanks

With 11.1 and 10.4 beta's out moving to active.

kul.pratap → opened merge request !22

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

I tried again on a fresh install of 10.2.6 and was not able to reproduce the problem. Since 10.2.6 is in security mode now and will not be receiving bug fixes, I am closing this as outdated.

If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue → starting from "Install Drupal core".

Thanks!

deepakkm → opened merge request !19

Hi prudloff

Updated the M.R. and followed your suggestions. Added ```javascript and ```yaml

Thanks

atul_ghate → opened merge request !10283

Automatically closed - issue fixed for 2 weeks with no activity.

Created an MR that addressed this issue, also updated IS, steps to reproduce and title.

okay will do review thanks

globexplorer → created an issue.

It has been two years since more information was asked for about this issue and the last work here was 9 years ago. Since justification for keeping this open has not been given I am closing this.

Thanks to everyone who helped here.

Intended to open this in drupalci_environments

Looks good to me! I created ✨ In 'Add fields' UI, auto-expand level 3 if level 2 has only one item Active for now, maybe you can have a look there and see if that is what you mean

scott_euser → created an issue.

cmlara → created an issue.

Please review.

Working on it.

Automatically closed - issue fixed for 2 weeks with no activity.

MR #29 was merged yesterday

MR #29 was merged. Should we change this issue status to fixed?

scott_euser → opened merge request !13

MR looks pretty good. The other core issue, ✨ Provide a Config Action to add/edit a component in a layout Active is moving along since last mentioned here. When I looked over it, it seems like it would cover our use case. It's also been marked as a Starshot blocker, so the timeline should fit our needs here.

@plopsec, what do you think? If it covers everything we need, this issue would no longer be relevant correct?

scott_euser → created an issue.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

🐛 Facets with AJAX not working in most of situations Needs review has an elaborate fix for a different issue that happens to also resolve this - but that issue has been open for 5 years and may not land any time soon. I'm attaching a patch for this issue that just resolves the Session error introduced in Core 10.3

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

Hi
Not able to reproduce an issue on drupal 11.X

Upon translating a media, not seeing that fields are present twice on the form.

See the attachment.-

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

And unassigning since there has been no work here for many years.

The Ban Module was approved for removal in 📌 [Policy] Deprecate Ban module in Drupal 10 and move it to contrib for Drupal 11 Active .

This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project → and the Extensions approved for removal → policies.

The deprecation work is in 🌱 Deprecate Ban module Active and the removal work in 📌 [12.x] [Meta] Tasks to remove Ban module Postponed .

Ban will be moved to a contributed project after the Drupal 12.x branch is open.

@poker10, you need to create your own issue to become a maintainer of this module. My request was closed :(

mstrelan → opened merge request !10282

clarkssquared → opened merge request !273

mstrelan → created an issue.

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

clarkssquared → created an issue.

@atul_ghate, thanks for working on this issue. I am going to unassign because for Drupal core, it is preferred that contributors add a comment that they are working on an issue instead of assigning it to themselves. See Assigning ownership of a Drupal core issue → .

Just one final comment that I think needs addressing.

quietone → opened merge request !10281