🇺🇸United States @redbrickone

I was testing if I could update this module to 3.0 without the patch.. Looks like it may not really be an issue anymore.
You cannot add a scheduled time without a scheduled state. Same thing for unscheduling. It will not let you save the node until you add a scheduled state if you have entered a scheduled time.
The scheduling still works as expected if you only set up a schedule date and state and do nothing with the unpublish fields as well.
I am removing this patch from my project as this doesn't really seem an issue anymore on 3.0. Can anyone else verify?

I re-rolled the last patch to work with 8.x-1.4. Seems to apply fine now. I was having issues with it on the latest version of field_permissions with Drupal 10.4.1.
If anyone wants to test this out or add to an MR for this issue that would be great!

Hi all, I've re-rolled this patch to work with 8.x-1.8. I've uploaded it as https://www.drupal.org/files/issues/2025-01-09/views_ajax_history-310712... →
This works for me with 1.8 and D10.4.1. Adding this here if someone would like to add back to the issue. Thanks!

Hi is there any activity here? The latest patch does not apply with 8.x-1.8 so I am sticking with 8.x-1.7 until there's a resolution or this fix has been added to a newer version. Would love to see an update there. Thank you!

Hi is there any update here? Looking for a patch that would work with Drupal 10.4.1. I am keeping field permissions set to 8.x-1.3 in order to keep this patch that works with this version. When updated to 8.x-1.4 the patch no longer works.

This is the patch I am using: https://www.drupal.org/files/issues/2919343-3-thefieldisnotdisplayedbuti... →
This works fine with 8.x-1.3 but unable to update to 8.x-1.4 and still use this patch or the latest patch added to this issue.

Thanks!

I have a working patch locally for this issue. After some testing, I may add it here for review. Though, I am just formatting the dates and not giving the option to format or leave as a timestamp.

redbrickone → created an issue.

I'd love to see some movement on this issue.
I don't think a site having a lot of files saved on the server is a small use-case.

I'm working on a site that has +3GB of files.
I'm generally unable to even open the Files Unmanaged tab as it takes too long to load. If it does end up loading, it just says "There are no unmanaged files in your system!" after taking 5+ minutes to load.

When trying to delete all items in the Orphaned Files tab at once, the batch eventually fails and does not continue.
FWIW - My orphaned files is close to 115,000 images which is over 2300 pages of 50 orphaned files.

Is there a better method to clear these out other than doing one page at a time?

Upon further investigation of the module, I've narrowed it down to possibly being this code here as the culprit: https://git.drupalcode.org/project/layout_builder_iframe_modal/-/blob/1....

// Stores the last scroll position before rebuild happened.
  Drupal.AjaxCommands.prototype.openIframe._scrollPosition = 0

  /**
   * Scrolls to the position before the layout rebuild was triggered.
   *
   * The scroll only happens if the delta between then and now is above a
   * certain threshold. This prevents unnecessary scrolling.
   */
  Drupal.AjaxCommands.prototype.scrollToBlock = function () {
    var scrollY = Drupal.AjaxCommands.prototype.openIframe._scrollPosition
    if (scrollY) {
      window.setTimeout(function() {
        if (Math.abs(window.scrollY - scrollY) > 300) {
          window.scrollTo(0, scrollY)
        }
        Drupal.AjaxCommands.prototype.openIframe._scrollPosition = 0
      }, 200)
    }
  };

I'm running out of time looking into this for this week. I may be able to dig in more next if someone else doesn't find a solution by then.

I was hoping a patch from this issue would fix it but didn't have such luck: https://www.drupal.org/project/drupal/issues/3209129#comment-15605759 🐛 Scrolling problems when adding a block via layout builder Needs work

FYI I reverted back to drupal 10.2.4 and the issue still remains. I have updated these modules as well. Unsure which one introduced the issue though.

Better Exposed Filters 6.0.3 → 6.0.5
Ckeditor 5 Paste Filter 1.0.0 → 1.0.1
Config Ignore 8.x-3.2 → 8.x-3.3
Config Split 2.0.0 → 2.0.1
Diff 8.x-1.1 → 8.x-1.3
Focal Point 2.0.3 → 2.1.0
Gin Login 2.0.3 → 2.0.4
Linkit 6.1.3 → 6.1.4
Password Policy 4.0.0 → 4.0.1
Scheduler 2.0.1 → 2.0.3
Simple XML sitemap 4.1.8 → 4.1.9
SVG Image Field 2.3.1 → 2.3.2
Token 8.x-1.13 → 8.x-1.14
WebP 8.x-1.0-rc1 → 8.x-1.0-rc2
Gin Admin Theme 8.x-3.0-rc9 → 8.x-3.0-rc10
Drupal Core - 10.2.4 → 10.2.6

I'm also experiencing this issue on a site after upgrading to Drupal 10.2.6. I am experiencing this in Chrome.

I have also found a solution for this long outstanding issue: https://www.drupal.org/project/commerce_afterpay/issues/3208440#comment-... ✨ Support immediate payment flow RTBC

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

redbrickone → created an issue.

I'm also curious about the status of getting this in Drupal 10. Any chance to get a patch rolled to 10.2.2?

redbrickone → created an issue.

redbrickone → created an issue.

redbrickone → created an issue.

Is there any update on this? I am encountering this in Drupal 9 Views still.
I have a block view display and a page view display in the same view. Exposed form is on the block view. It sends the user to my page view every time.
If I remove the page view display from this view it works as expected.

Hi I have encountered the same issue on this version of Cloudflare as well. I am unable to modify the config values on the prod site to get these errors gone. I've created a patch that can be used to allow you to edit the Cloudflare admin config form which will let you enable a Zone & bypass these errors. It seems the root issue does stem from the drush DB updates after updating to this version. This is a workaround for those who need to get past these errors but the root issue should probably still be looked into. The MR in comment #6 should do the trick.

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

redbrickone → created an issue.

Gotcha, thank you! I will look into this. We also found a route just using CSS so we can probably close this issue. I was under the impression we couldn't modify the styles within the chart which doesn't seem to be the case. Thanks for your prompt reply, you rock!

redbrickone → created an issue.