Account created on 9 April 2015, about 10 years ago
#

Recent comments

The issue does not seem to be fixed in the latest beta and dev releases:

Uncaught PHP Exception Paytrail\\SDK\\Exception\\ValidationException: "Amount doesnt match ItemsTotal" at vendor/paytrail/paytrail-php-sdk/src/PaytrailClient.php line 213

ApplePay is enabled and domain listed in the merchand's panel because we have had it available in the Paytrail payment page, but I will ask help from Paytrail if they need to do something so that ApplePay becomes available with your module.

Thank you for very quick response and fix! A purchase with decimal quantities was successfully processed.

By the way, I am missing ApplePay which we have enabled if we use Paytrail's payment page. Is there some additional configuration to enable ApplePay (which I can see in test mode)?

Paytrail proposed this kind of approach:

The description field can be used to convey information about the contents of the order item. This could also include the quantity, for example: "1.5 meters" or "1.5 kg".

In this case:

The units field should always be set to 1, if the quantity is provided in the description field.

The unitPrice field should contain the total price of the sold product (not price per unit, but the full price for the quantity).

This way, the Paytrail interface would display both the sold quantity (e.g. 1.5 meters or 1.5 kg) via the description field and its price via the unitPrice field.

Could the module handle this in case of decimal quantities?

Hi! We have had decimal quantities for ten years now and we have used Xocovis' Paytrail module where this has been handled also with the current Paytrail API.

I could find any fix other than disabling Colorbox for video media with a custom module. Quite disappointed to the lack of responsiveness of the module's maintainers.

Where happens the dynamic setting of the height (style) of elements colorbox, cboxWrapper, cBoxMiddleLeft, cBoxMiddleRight, cboxContent and cboxLoadedContent? For some reason the Colorbox module is not able to pick up the correct height of my local MP4 video (in media field).

I understand now that the issue is that my link field exists in Content/Node, because they are slide specific e.g. Product 1, Category B etc. and not media specific because same media is reused around the site. I suppose I need to use my hook for wrapping slides with content links as previously and figure out the namespace issue in case of video media.

Here are my style settings:

The links that are rendered around the slides point to the slide content node and not to URL in the link field of the node. However, the link field is correctly rendered as plain text if I add it into the fields of the view as Content:Link. It does not seem to matter if I select the link field under Fields or Caption fields in Style settings.

I tried Image linked by Link setting and the slide is wrapped with a link but it is not the right link which is one the fields of slide content. What am I doing wrong?

I already tested literaly all combinations of Content:Media settings, but none of them seem to affect how the video or image is displayed.

I suppose I have to try the CSS route.

I tested with Olivero theme and same behaviour: video is tiny and images are full width.

I tested with Olivero theme and same behaviour: video is tiny and images are full width.

Is this suppose to work with the current version of Slick Views? If I have a video in a slide of a Slick Carousel, it is rendered with video controls I will have to press the play button, it does not play automatically.

I'm trying to uninstall Commerce Wishlist and right after that I get the White Screen of Death and this error message. I have tried to look for references to Commerce Wishlist in the Admin UI but deleting any of them does not resolve this issue. How can I uninstall this module cleanly?

What is the schedule to get this feature into the production release?

I can confirm this issue on our Drupal 10 site with standard core modules enabled. Any update on this issue?

Any update on this issue? It is still a valid problem with the latest version 8.x-1.6

No change, sorry. Here is the new error message:

>  [notice] Update started: commerce_pricelist_update_8206
>  [error]  SQLSTATE[42000]: Syntax error or access violation: 1055 Expression #1 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'drupal_kuovi_test.cpi.id' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by: SELECT "cpi"."id" AS "id", "cpi"."price_list_id" AS "price_list_id", "cpi"."purchasable_entity" AS "purchasable_entity", "cpi"."quantity" AS "quantity", "cpi"."price__currency_code" AS "price__currency_code", COUNT(*) AS "cnt"
> FROM
> "drupal_commerce_pricelist_item" "cpi"
> GROUP BY "type", "price_list_id", "purchasable_entity", "quantity", "price__currency_code"
> HAVING (cnt > 1); Array
> (
> )
>
>  [error]  Update failed: commerce_pricelist_update_8206

It seems that the reason for this issues was that "drush cr" was not performing correctly. After emptying all caches from the admin UI everything works fine.

Currently the sorting behaviour seems different. PayPal is still always the first but the other payment methods are sorted by their weights defined in admin/commerce/config/payment-gateways and not by their ID.

Is there a hook in PayPal module that always renders it as the first/default payment method? How can I change the default payment method?

Thank you very much djroshi! I was already looking from a right place but I never figured out to change Product variations attributes to Product variation title. It was not very intuitive. :)

Where is this code snippet from? All our products are rendered with a variations dropdown even when they have just one variation.

Is it true that this functionality is still not in production after seven years?

I believe we have had this issue since Drupal 8 and we still have it with the latest Drupal 10.1.6 version so I really don't think this is a Drupal core bug.

Thank you very much, that was awesome! It didn't work out of the box e.g. $blazies->get('namespace') brings two values "blazy" and "slick" and formatting URL to plain text didn't work, but this is my final working code for this use case:

function hook_preprocess_blazy(array &$variables) {
  $settings = &$variables['settings'];
  $blazies  = $settings['blazies'];

  if (!empty($settings['link'])) {
    // Only scope to blazy and if an image, not video, instagram, etc.
    // Checks for more conditions like blazies.is, blazies.use, etc.
    // Or remove the namespace to apply to ecosystem if consistent.
    if ($blazies->get('namespace') == 'blazy' && $blazies->is('image')) {
      if ($link = $variables['captions']['inline']['link'] ?? []) {

          $variables['url'] = $link['content'];

          // Update internal blazy CSS classes, etc.
          $settings['media_switch'] = 'content';
          $blazies->set('switch', 'content');

          // Disables rendered link since already made as a wrapper.
          $variables['captions']['inline']['link'] = [];
      }
    }
  }
}

This is what we currently have customized in the twig template:

{% set slide %}
  {% block slick_slide %}
{% if item.caption.link %}
        <a href="{{ item.caption.link }}">
  {% endif %}
        {% if settings.split and not settings.unslick %}
      <div class="slide__media">{{ item.slide }}</div>
    {% else %}
      {{ item.slide }}
    {% endif %}
 {% if item.caption.link %}
        </a>
  {% endif %}
{% endblock %}
{% endset %}

The purpose of if item.caption.link statements is to wrap the slide with an A tag.

What is the correct way to do this in version 3.x if this part of the twig template is removed?

I'm sorry but I changed my mind and implement an A-Frame viewer in my Twig template and therefore I'm not interested in this module anymore. You may delete this bug report if you think it is unnecessary.

Production build 0.71.5 2024