Contrib.social

BigPipe may break images from getting displayed to authenticated users

Open on Drupal.org →
Created on 26 July 2019, about 6 years ago
Updated 27 April 2023, over 2 years ago

This is a tough one to describe, as it is somewhat conditional.

Using Views as blocks. The view is of a Content Type with three sections (not using Paragraphs or Field Collections), each with a image field with a default image and a formatted text field. If the text field is present it is re-written with an element for the Background Image Formatter to target (targets use unique css identifiers - the Image field is not included in this and no Tokens for the Image field were used).

When a user is anonymous, everything is fine and all background images are displayed in all possible variations (one, two, or all three sections).

When the user is authenticated, then there is a much different behavior. If only one re-written field/element is rendered then the background image is rendered. Reviewing the page source shows all three style tags in the head with the correct css settings. If more than one field/element is rendered then no background images are visible and the style tags have not been rendered in the head of the document.

It does not matter if the logged in user has access to the admin toolbar or any other drupal overlay things. All permissions are install default and it doesn't matter if the user has any elevated permissions. (Can it be permission based if it works with one image but not multiple?)

Module was originally installed as 1.6, but has been updated to 1.10 with no change in behavior. On Drupal 8.7.1.

*****

Edits: add correct module version & add drupal version & a word.

More edits: I've been digging around the module and I can see it is building the elements correctly in viewElements() for all cases, and firing when required.

🐛 Bug report
Status

Active

Version

1.10

Component

Code

Created by

mlumadue

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 2 years ago →
    🇺🇸United States jmouse888

    Three and a half years later, still having the same problem. Running Drupal 9.5.8 and bg_image_formatter 8.x-1.16,

    However, some how it's only happening our front page. All internal pages are rendering the inline styles just fine, even with authenticated users. Only thing different for the front page is it's using a different page--front.html.twig. The rest of the site is using page.html.twig

    From browser source code, BigPipe are loaded for both page templates. Don't know why it will work with one but not the other.

    Uninstalled BigPipe and everything is working.

    May be if I trace the difference between the two page templates may result some clue. Will investigate further down this route.

  • Comment 18 days ago →
    🇨🇦Canada dadderley Vancouver

    I am using the Background Images Formatter for banner blocks.
    It worked just fine until recently until I upgraded my site to Drupal 11.

    I am using Drupal Version 11.2.3
    Background Images Formatter 8.x-1.18

    The Background Image would not show for logged in users until I did a hard refresh of the page.
    The actual style for the BG image:

    .banner {
    background-color: #FFFFFF !important;
    background-image: url(https://www.mysite.ca/sites/default/files/styles/background_mysite_banner/public/2023-12/6_health_professionals_group_smile_bg_headroom3.png.webp?itok=pms8eNgp) !important;
    background-repeat: no-repeat !important;
    background-attachment: scroll !important;
    background-position: left top !important;
    z-index: auto;
    background-size: cover !important;
    -webkit-background-size: cover !important;
    -moz-background-size: cover !important;
    -o-background-size: cover !important;
}

    would not be injected into the html at all on the first page load for a logged in user.
    No problem for anonymous users.

    I found this issue.

    I uninstalled the Big Pipe module and this seems to have cleared up the issue.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024