🇺🇸United States @shelane

Thanks

This module is specifically for a Bootstrap theme and is not intended for non-Bootstrap themes. I do not have any suggestions as I do not know what modules may be available for a tabs views style.

I have not been able to repeat this as of late. Thank you for your time.

In light of the other script and changes I made to it to remove jQuery, try this using the dev branch:

(function () {

  'use strict';

  /**
   * Attaches the behavior to the user's custom carousel functionality.
   */
  Drupal.behaviors.bsCarousel = {
    attach: function (context, settings) {
      // Select the specific carousel element
      const carousel = document.querySelector('#views-bootstrap-home-slider-block-1');

      if (carousel) {
        // Ensure the carousel has more than one slide
        const slides = carousel.querySelectorAll('.carousel-inner > div');
        if (slides.length > 1) {
          // Attach the event listener for the 'slid.bs.carousel' event
          carousel.addEventListener('slid.bs.carousel', function () {
            console.log('CAROUSEL HAS SLID');
          });
        } else {
          console.log('Carousel has only one slide, event listener not attached.');
        }
      }
    }
  };

}());

shelane → created an issue.

I just saw that there is some javascript in the module related to the carousels. I'm going to update it to remove its dependence on jQuery and see what else it may be doing to interfere.

kwiseman: this may be related and I would appreciate an MR for the fix you found.

The problem is that allowing all of the tags from xss::getAdminTagList() in accordion and tags would break the required structure for these Bootstrap components. The list is limited for the accordion collapse element, but not the accordion body and for the tab, but not the tab-pane area.

It was indeed the case that the "responsive" variable is not getting read. It is likely due to a conflict with the views table processor. However, the proposed solution put the hard-coded style unnecessarily. With the variable changed in the preprocessor and the template, the class is added, and that class has that style setting. I appreciate the efforts though.

shelane → created an issue.

Thank you.

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

That is interesting. I'll see what I will need to do for that workflow. In the meantime, leave it at "Unformatted List" on that screen and then set up the format and settings on the next page.

I'm hoping to get to this at DrupalCon.

You only have to click on the star to follow to get notifications of changes.

Can you try:

Drupal.behaviors.bsCarousel = {
  attach: function (context, settings) {
    $(once('bs-carousel', '#views-bootstrap-home-slider-block-1', context)).each(function () {
      // Ensure the carousel element exists
      $(this).on('slid.bs.carousel', function () {
        console.log('CAROUSEL HAS SLID'); // This should now work
      });
    });
  }
};

This module only provides the style processing for view data. All of the JavaScript for Bootstrap carousel behavior should be provided by the theme.

Interesting question. I don't know. If you know of a views style module that does this, let me know and I'll see what they're doing for that.

Since I have merged two other issues, there is now a conflict on this branch.

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

I have some work to do on
✨ Allow weights for social media items Active
✨ Refactor the share buttons template Active

That may impact this request and I'd like to get those done first.

With testing I found that that the visual display no longer works with the proposed changes. See attached screen captures.

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

Sorry, I have been out sick. At this time I do not want to add additional maintainers. I will continue to respond to feature and merge requests and if there is a feature that you would like to see in this module, please make an issue. I credit all who contribute ideas and code to the module.

I see that you have interacted with Joseph in the Bootstrap theme issues. Considering that this module is not providing any of the javascript, I was going to recommend checking there.

He created the jQuery Downgrade module → and also noted the release notes → .

It didn't kill my site, so I'm not sure that was the cause for you. However, it does need to be removed since we are no longer supporting Drupal 8.

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

Thank you for your interest in contributing to the CKEditor Bootstrap Table module. I appreciate your enthusiasm and offers to help.

Typically, I don't grant commit access to individuals who haven't actively participated in the project's issue queue with patches and merge requests (or at least by conducting reviews). After a quick review, I didn't notice any such participation from you regarding the CKEditor Bootstrap Table module.

Additionally, this isn't solely "my project." I became a co-maintainer primarily to facilitate the D10 port.

I plan to dedicate some time to work on D11 releases in the coming weeks. Your assistance with thorough reviews and marking issues as RTBC (Reviewed and Tested by the Community) where appropriate would be greatly appreciated. This would not only expedite the D11 compatible releases but also help me feel more confident in adding new committers.

Thank you once again!

Best regards.

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

This cannot be fixed by the maintainers of this theme as none of us own the site.

If we do this, it will only be for the current Drupal versions.

Wait, what? ... Who decided this on such a large project without a readable user discussion?

The original creator and maintainer of the Bootstrap theme stopped doing Drupal several years ago. There is no one who was part of the original decision making of the architecture of this theme around to make decisions going forward. For those of us who picked up the mantel on it, it was to help keeping it working for those that relied on it and needed it to be updated for the major versions of Drupal.

There was no plan to make this theme compatible with Bootstrap 5 and the effort would have been significant. Anyone at any time could have offered to come in and help upgrade it. No one came to make this theme upgraded to Bootstrap 5 with the same architecture that it had. Also, Drupal now has SDC, which didn't exist at the time these theme was created or when the original maintainer was around.

So, those of us who have been maintaining this theme were approached by the maintainer of Bootstrap Barrio. Since it was the other Bootstrap theme with the most number of users. He suggested combined forces to offer this theme with a Bootstrap 5 version from Bootstrap Barrio. We agreed. No user discussion is necessary because the users cannot make the decisions for the maintainers on how to move forward when it wasn't going to move forward at all.

It may be a little while (a couple of weeks or so) until I do a release as I'm trying to address more issues as time permits.

Without more information, I cannot reproduce the issue. Reopen if you want to post this information.

There is one issue with the UI that the other modules fix that until this point I have not figured out. However, now looking at their examples, I should be able to update this module to do the same. And that is ✨ Allow weights for social media items Active .

It seems that this request should be for overriding on a per-node basis. Is that correct? Or are you looking to override all shared links to a single URL? That seems a little contrary to the point of the sharing module.

I have recently merged a submitted MR for making a sub-module that allows overrides for sharing on a per-node basis. I can see having an override URL option as part of that.

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

Also, what theme are you using? What version of Bootstrap are you using?

I checked in the 5.5.0-rc3 release and the dev release (only one additional commit).

The stack trace doesn't say anything about the views bootstrap module. It looks like it has something to do with the Views Reference Field module.

I am able to see the settings form both when editing an existing view and creating a new view.

Please submit an MR so it can be compared and tested.

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

Thanks.

Thank you.

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

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

smustgrave → credited shelane → .

I have no objection.

Thanks.

shelane → created an issue.

It's clear by the commit logs that Better Social Share is the newest. The philosophy behind Better Social Sharing Buttons and AddToAny are very different. Better Social Sharing Buttons makes use of direct calls to the social media's own sharing URLs and does not collect or send any of the users data to any other service.

I agree. Can someone create an MR for this?

My apologies. This has been addressed in dev. It would be great if a release was put out that includes this.

shelane → created an issue.

Thanks.

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

Which Bootstrap theme are you using? Is there a setting in the theme for making the images responsive?

The Social Media Links Block and Field module is different functionality from this module because it is for placing links to your (the web site's) social networks.

The purpose of this module is to allow content (e.g., a node) to be shared on a visitor's own social media sites. However, the the web site owner can still choice which social media networks to provide the functionality for.

I'm not sure why the maintainer of "Better Social Sharing" felt the need to create a brand new module instead of reaching out to perhaps collaborate with this module. I was not aware of its existence until you posted this.

The AddtoAny, ShareThis, etc type modules allow those companies to collect data on your users. Well, that opens up a can of worms to for GDPR compliance or new laws for privacy in some US states, such as California.

Does this mean that I can mark this as fixed?

This module assumes that you are already using a Bootstrap theme and would already have the Bootstrap library. I'm not sure why you would want to use the Bootstrap styles for a view without a Bootstrap theme.

The module will not provide a mechanism to attach the Bootstrap library files. However, if you really want to, you can copy the templates to your theme, create a Bootstrap library and attach them through the templates. These does leave the possibility that you will not get any template updates if the module is updated. And I would not recommend doing that.

The grid was working as it was. It correctly had col-val for the class. The carousel breakpoint class was incorrectly putting the xs. I updated the code with the forms, preprocess functions, schema, template, etc.

Thanks.

I was just looking at that. There are two functions in the ViewsBootstrap utility class that are not used anywhere. There is getColSize, which was used (or is used) in the 8.x-3.x branch. Then there is getColumnPrefix.

  public static function getColumnPrefix($breakpoint) {
    return 'col' . ($breakpoint != 'xs' ? '-' . $breakpoint : '');
  }

It seems even when it was added, it wasn't actually called anywhere. However, this may be useful in this situation.

shelane → created an issue.

Thanks

I just had to remove the latest patch from my site because it caused a previously working view to return no results.

Thanks.

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

Looks like there is a bit more wrong with the use of columns. It's intended that if you have 2 columns, the content should appear side by side in a single carousel. I'm not seeing that either before or after this MR.

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

Thanks.

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

Thanks for that check. I believe I addressed all of this issues in the new MR.

I can confirm here that the custom row wrapper class is set and remembered.

I have updated the documentation, which also includes pointing to the Bootstrap documentation on additional classes that can be added. Of course, you're not limited to Bootstrap classes. Add your own theme classes as needed to the various class field options.

I have made the code changes that I had in this MR in the related issue. There is now a new release. As I said, since I can't recreate the error described, I'm not sure if this fixed it or not. Let me know. If it does not, the more information you can provide me on how to recreate it, the better.