Top News - Page 65 - Extly News - The essential news, powered by Perfect Publisher.

Release of PrestaShop 1.7.8.6

It has been decided to deliver a new maintenance release for 1.7.8.X branch.

In this release we fix a couple of issues, notably :

2 Major bugs
4 Minor bugs

1.7.8.6 is available!

Reminder: the 1-Click Upgrade module’s latest version is v4.14.1, don’t forget to upgrade it.

Issues addressed in release 1.7.8.6

Front office

FO - Create an account - the alert is duplicated when we create a new account with invalid firstname and lastname

Back office

Others

Acknowledgments

Contributors to this patch version, from both the Core team and the community at large:

Ali Shareei, Amit Kumar Tiwari, Daniel Martin, Franck Lefèvre, Jonathan Lelievre, Krystian Podemski, Lorenz Meyer, Mathieu Ferment, Matthieu Rolland, Mickaël Fernandez, Miguel Paolino, Nesrine Abdmouleh, NicolasCador, Pascal Cescon, Pierre Rambaud, Ricardo González Garza, Romain Soulard, Thomas Baccelli, Valentin Szczupak

Thank you!

Download PrestaShop 1.7.8.6 now!

Since version 1.7.8.6 is a “patch” update to version 1.7.8.5, upgrading from any 1.7.8 version will be easy: features will work better, and modules & themes which worked fine on 1.7.8.x will work just as well with 1.7.8.5. Upgrades from a standard 1.7.x version should work just as well.

Details: Category: Dev News

Laravel Dusk Browser Testing: Best Practices & Tips

There are various best practices that can help with building and maintaining Laravel Dusk browser tests (and I wish we had known all of these when we started with our test suite). In this article, see some of the lessons we've learned so you can write better Laravel Dusk tests yourself.

The post Laravel Dusk Browser Testing: Best Practices & Tips appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

Details: Category: Dev News

Using CSS variables in Bootstrap

Bootstrap v5.2.0-beta1 added a slew of CSS custom properties, or CSS variables, across the :root level and all our core components. Here’s a quick look at how you can utilize them in your projects.

With CSS variables, you can now customize Bootstrap easier than ever, and without the need for a CSS preprocessor. All the power of Sass is still there behind the scenes, but CSS variables adds a ton of power for the future. Use and compose new values, updates styles globally without recompiling, set fallback values, setup new color modes, and more.

Let’s dig in.

CSS variables?

Their official name is custom properties, but they’re often referred to as CSS variables thanks to their most immediate use case for setting specific values. Consider reading the MDN CSS custom properties article or the CSS Tricks guide if you need a primer.

In a nutshell, CSS variables allow you to name frequently used values. For example, instead of writing #6f42c1 everywhere, you can set --purple: #6f42c1. Then you can use that variable later on with the var() function.

:root {
  --purple: #6f42c1;
}
.custom-element {
  color: var(--purple);
}

We use CSS variables in Bootstrap to set many property values globally, across our components, and in some of our utilities.

Groups of variables

When we talk about CSS variables in Bootstrap, we’re referring to three major groups:

Root variables — Globally scoped variables available on the :root element (<html> usually) and accessible by any element throughout the DOM.
Component variables — Variables scoped specifically to each component, usually on the component’s base class, and their modifier classes and Sass mixins.
Utility variables — Used as modifiers within other utility classes.

Regardless of where they are, all of our CSS variables are prefixed with --bs-, so you know where they’re coming from and how they might be used across codebases that mix Bootstrap’s CSS with additional custom styles. You’ll also notice that we don’t put all our component variables at the root level. This keeps CSS variables scoped to their intended use cases and prevents polluted variables in the global :root scope.

It’s also worth mentioning two larger efforts that are still to come around CSS variables:

Adding CSS variables to all our forms
Adding more nuanced global theme variables and support for color modes like dark mode.

These are likely coming in v5.3.0 (our next minor release after v5.2.0 stablizes), so in the mean time, check out the GitHub repo to see how things are shaping up.

Root variables

Root variables in web inspector

Bootstrap has a ton of root variables and we’ll only be adding more in future updates for the aforementioned color mode support. As of this post, we have the following CSS variables on the :root element:

Colors — All named colors, gray colors, and theme colors. This also includes all our $theme-colors in their rgb format.
Body font styles — Everything from font-size to color and more, all applied to our <body> element.
Shared properties — For property-value pairings that we consider theme specific, like link colors and border styles.

Root CSS variables are used extensively across other parts of Bootstrap to allow you to easily override our default styles at a global level. For example, if you wanted to adjust the default border-radius and link color for our components, you could override a couple variables instead of writing new selectors.

// custom.css
:root {
  --bs-border-radius: .5rem;
  --bs-link-color: #333;
}

You can even use other root variables to override those values:

// custom.css
:root {
  --bs-border-radius: var(--bs-border-radius-lg);
  --bs-link-color: var(--bs-gray-800);
}

Without CSS variables, you’d have to use a preprocessor like Sass or write new selectors for every instance of these properties across all components. The former is relatively easy, the latter not so much. CSS variables help solve that.

Component variables

On our components, CSS variables get even more power for customizing. Nearly everything under the Components section in our docs sidebar now has CSS variables available to you:

Scrollspy and close button have no relevant CSS variables, so they’re excluded here.

Throughout our documentation you’ll find examples of customizing our default components by overriding their CSS variables. One great example comes from our own docs where we write our own button styles to create a purple button.

.btn-bd-primary {
  --bs-btn-font-weight: 600;
  --bs-btn-color: var(--bs-white);
  --bs-btn-bg: var(--bd-violet);
  --bs-btn-border-color: var(--bd-violet);
  --bs-btn-border-radius: .5rem;
  --bs-btn-hover-color: var(--bs-white);
  --bs-btn-hover-bg: #{shade-color($bd-violet, 10%)};
  --bs-btn-hover-border-color: #{shade-color($bd-violet, 10%)};
  --bs-btn-focus-shadow-rgb: var(--bd-violet-rgb);
  --bs-btn-active-color: var(--bs-btn-hover-color);
  --bs-btn-active-bg: #{shade-color($bd-violet, 20%)};
  --bs-btn-active-border-color: #{shade-color($bd-violet, 20%)};
}

Which looks like this:

Another great example is from our tooltips. You can add custom classes to tooltips and popovers in Bootstrap with data-bs-custom-class="custom-tooltip". Then, with one CSS variable, you can change the tooltip background and arrow color.

.custom-tooltip {
  --bs-tooltip-bg: var(--bs-primary);
}

Which looks like this:

Custom tooltip

There are dozens of CSS variables in play across our components. All of them are referenced in a new section on the relevant docs page. For example, here are our modal CSS variables. This is in addition to all the Sass variables, mixins, loops, and maps used for each component.

Utility variables

Not every utility class uses CSS variables, but the ones that do gain a good amount of power and customization. Background, border, and color utilities all have what we call “local CSS variables” to improve their usefulness. Each of them uses CSS variables to customize the alpha transparency value of rgba() colors.

Consider our background color utilities, .bg-*. By default each utility class has a local variable, --bs-bg-opacity with a default value of 1. To change the background utility alpha value, you can override that value with your own styles, or some new .bg-opacity-* utilities.

<div class="p-3 bg-success bg-opacity-25">
  ...
</div>

Here’s how .bg-success looks with all our .bg-opacity-* classes applied:

Background opacity examples

And the same is available for border color opacity (--bs-border-opacity and .border-opacity-*) and text color opacity (--bs-text-opacity and .text-opacity-*). So many color options are now available with these utilities.

By default, we ship with five values for these various opacity utilities.

Class names	Alpha value
`.text-opacity-10` `.bg-opacity-10` `.border-opacity-10`	`.1`
`.text-opacity-25` `.bg-opacity-25` `.border-opacity-25`	`.25`
`.text-opacity-50` `.bg-opacity-50` `.border-opacity-50`	`.5`
`.text-opacity-75` `.bg-opacity-75` `.border-opacity-75`	`.75`
`.text-opacity-100` `.bg-opacity-100` `.border-opacity-100`	`1`

Expect more CSS variables to make their way into our utilities. There’s a lot of power in real-time customization, even for what we consider immutable styles.

Ready to get started with Bootstrap? Checkout the quick start guide so you can put these new CSS variables to work in your next project!

Details: Category: Developer News

Laravel Roles and Permissions: Gates and Policies Explained

In Laravel, roles and permissions have been one of the most confusing topics over the years. Mostly, because there is no documentation about it: the same things "hide" under other terms in the framework, like "gates", "policies", "guards", etc. In this article, I will try to explain them all in "human language".

The post Laravel Roles and Permissions: Gates and Policies Explained appeared first on Laravel News.

Join the Laravel Newsletter to get Laravel articles like this directly in your inbox.

Details: Category: Dev News

Bootstrap Icons v1.8.2

Bootstrap Icons v1.8.2 has arrvied with some bug fixes and a refreshed docs design to match our main project.

Here’s a quick rundown on the icon fixes:

Fix cutoff bank icon
Fix house-heart and house-heart-fill fill-rules
Fix corners of pentagon icons to match other shapes
Fix fill-rule for x-lg
Fix cutoff tool icon

On the CSS side, we’ve also added font-display: block to help address our icon font affecting Google Lighthouse scores.

Looking for more new icons? Head to the issue tracker to check for open requests or submit a new one.

Install

To get started, install or update via npm:

npm i bootstrap-icons

Or Composer:

composer require twbs/bootstrap-icons

You can also download the release from GitHub, or download just the SVGs and fonts (without the rest of the repository files).

Figma

The Figma file is now published to the Figma Community! It’s the same Bootstrap Icons Figma file you’ve seen from previous releases, just a little more accessible to those using the app.

Details: Category: Developer News

Page 14 of 1117