🇮🇳India @DhruvR

Fixes are done and deployed.

Thank for the patch, working for me.

dhruvr → created an issue.

dhruvr → created an issue.

Minor update done for yml file, Thank you

Hello, Cilefen.

I have attached the sample YAML file in the project description. Please take a look.

Thank you for your support!

Hello , I wanted to ask if somebody has face this issue yet, or is it something with my setup.

Closing this ticket, if you still have any concern please reopen this ticket.

Closing this ticket, If you have further please open it again.

dhruvr → created an issue.

Hello @sahil,

The issue you're facing with the [customentityname:original:label] token occurs because the original parameter isn’t designed to fetch the label in the default language. Instead, it retrieves the previous version of the entity’s label (or other field values) before any updates.

For example, this feature is often used in scenarios like hook_presave to compare the current value with the previous one, such as:

if ($entity->field_date->value != $entity->original->field_date->value) {  
  // Perform some logic.
}  

Unfortunately, this means the token won’t resolve the way you’re expecting for multilingual alias generation. If your goal is to use the default language label, you might need custom token logic to achieve that.

Let me know if you’d like further guidance!

dhruvr → created an issue.

Thank you for your query!

The current module functionality is designed to work specifically with the Promotions module. The strikethrough (List price) and discounted price display are calculated based on the applied promotions.

For your use case, By overriding the product display template, you can dynamically show the List price as strikethrough and the Price as discounted without relying on this module.

Given your requirements, I would recommend not using this module. A tailored template-based approach will provide the flexibility and control you need for handling price variations effectively.

dhruvr → created an issue.

DhruvR → created an issue.

Hello @all, After looking at the source the solution of this error.

The issue got fixed patch given in relevant module config_rewrite page.

https://www.drupal.org/project/config_rewrite/issues/3203786 →

If anybody face this issue hope this help.

DhruvR → created an issue.

Nothing work for me can some one guide please

Thanks

Hello @all, Thank you for help the issue is resolved for me.

Thank you!! Going to review

Thank you!! Will be waiting for your response :) @Iarowlan

Hello @Iarowlan,

I see your point about accessing the display name directly from the database.
However, since the display name is derived from a combination of other user fields like first name and last name, we could utilize a concat SQL search approach.

Example:

SELECT *
FROM users
WHERE CONCAT(first_name, ' ', last_name) LIKE '%John%';

It would be beneficial to implement a method or hook that allows us to customize the search criteria for displaying results in the user autocomplete field.

DhruvR → created an issue.

The basic difference is in the Price Difference Formatter creating a separate formatter.

Which can cause lot of configuration update using price difference formatter for example:
Separate Views and multiple product fields configuration

Hello Ravi,

I was able to install the opigno profile using this command
composer create-project opigno/opigno-composer:3.1 opigno_latest

I was able to install the composer based version of the site by using this command
composer create-project opigno/opigno-composer:3.1 opigno_latest

Thank you Subodh, #3 is working for me.

DhruvR → created an issue.

DhruvR → created an issue.

This patch #18 Its working.