How do you flag stores when they are updated with a specific input method ?

I installed the following module on my site :

https://www.drupal.org/project/form_mode_manager

I have created an "Input Modes" in "Display Modes" for the store type with the machine name commerce_store.shipping_methods

/admin/structure/display-modes/form

I created a custom module to automatically flag stores that are updating.

Need information on updating Drupal versions

Right now, I have installed Drupal version 8.8.5 and
latest recommended version which is shown there is 8.9.7

So should I directly update it from 8.8.5 to 8.9.7
or
Should I need to update all the intermediate versions till 8.9.7 ?

Instance a service class once in a form

I have a form that is used to play a game (users select between one of two images multiple times) that utilizes a service class that manages loading images, calculating results, etc. How can I instance this service class one time so that it doesn't get re-instanced every time I rebuild the form, do you have to do it in form_state?

I was trying to do it in `__construct` because I thought that was only called when you first instanced the form, but when you rebuild the form it gets called again so my service class gets re-instanced. 

The alias /store/my-store is already in use in this language

I have a store type that contains a paragraph field.

When I create a store, it works perfectly. But when I update the store by adding a paragraph, I have an error in the form :

The alias /store/my-store is already in use in this language

This error occurs since the update to Commerce 2.17

How can I correct this ?

UPDATE

If I edit my store and save without changing anything, it works.

It's not just the paragraph, if I change the store logo I get the same error.

There is nothing in the logs.

Need help correcting 2 warnings in my logs

Hi, when I go to my site, I have two warnings in them that appear regularly. I can't find the source of the problem. Can you help me ? Thank you

https:/www.s1biose.com

Workaround for Drupal Logger's extreme inefficiency

The default Drupal logger is so inefficient it can't even print out an array containing two content-types, what gives? I'm trying to log an array that contains two content-types but I keep getting the error that I've ran out of memory, which is ridiculous because I currently have my setting at `512M`. 

It seems crazy to me that it takes Drupal more than 512MB to log some text.... 

Pages

Subscribe with RSS Subscribe to RSS - Drupal 8.x