🇺🇸United States @thalemn

thalemn → changed the visibility of the branch 3381732-type-error-count to hidden.

thalemn → changed the visibility of the branch 3381732-type-error-count to hidden.

Thanks @roderik. Actually I did finally arrive at your suggestions, and I updated the composer.json file to use version 4. Now it's recognizing that the library is there, all I need to do is configure the module settings with my certs, etc.

thalemn → created an issue.

thalemn → created an issue.

thalemn → created an issue.

I concur that the issue is with the mailer module (symfony). I have posted an issue there. My apologies and this issue can be closed.

thalemn → created an issue.

thalemn → created an issue.

I just discovered this issue, too. I have a number of views that were deleted when I uninstalled entityqueue, however none of the views had a dependency on entityqueues.

thalemn → created an issue.

Thanks for your solution. I'll take a look at our situation and see if we can make it work.

@Nuuou thanks so much for your quick reply. I think we can implement something based on your description, but would you be willing to provide a patch for the entityqueue module that would provide this solution for everyone?

We would like to use Entityqueue with Search API...@Nuuou: can you share your solution for D10?

Thanks!

I'm using search_api 8.x-1.29 and have a view based on the index of commerce products. Like the OP, I have the same issue: I cannot filter out product types that I want to exclude from the view. There's a similar issue on commerce: https://www.drupal.org/project/commerce/issues/3016759 → .

Is there something I'm missing in configuring the index and fields in order to filter by commerce product type? I've added the entity type field to the index but that doesn't work as expected.

What is the best course of action?

thalemn → created an issue.

Thanks for the patch. I applied the patch (using composer) and it does provide feedback if the product is out of stock (that's our primary need).

The only odd behavior is if I keep hitting the Add to cart button (without reloading the page), and the product eventually is out of stock, I get no feedback. But once I reload the product page, the out of stock message appears as expected.

This is a product you can test: https://bookstores9-dev.umn.edu/product/apparel/antigua-university-minnesota-morris-half-zip-pullover

Any thoughts?

Thanks!

thalemn → created an issue.

thalemn → created an issue.

Thank you. I have applied the patch in #9 and the hover issue has been fixed.

Looks like the dev version has been updated for D10 compatibility

thalemn → created an issue.

Yes, let's get this done. Thanks.

@Harish1688

Thanks for providing the gif.

There appears to be a step missing in your gif demo: when you switch from horizontal to vertical, click on an admin link to open the page (for example, click on Block layout link to open the Block layout page (/admin/structure/block). After that page opens (with the admin toolbar in the vertical position), switch the toolbar back to horizontal. Then the horizontal links do not hover for me.

Can you please try again?

Demo of hover issue

+1 for this feature

I agree with the need to integrate this module with the commerce stock module.

Our issue: when adding a product to the cart that doesn't have sufficient stock, the page breaks.

1. There is no modal window.
2. The status-danger message is outside of the page template container.
3. The cart icon breaks and now uses the dropdown display option for products (which has been set to No).

I am not sure how to debug these issues.

I looked at sortableviews but couldn't get it working with our Search API recipe.

Any updates on getting draggableviews working with Search API for D8-D9?

Thanks.

This thread was very helpful for my situation too. I embedded a view via twig tweak and needed to pass a taxonomy id value to the view contextual filter. The field from my content (commerce store) is a taxonomy field to toggle the use of Regular or Special/Holiday hours: store.field_hour. I set that field as a variable to use in the view: {% set hourActive = store.field_hour[0]['#plain_text'] %}. So the embedded view looks like this: {{ drupal_view('hours', 'block_1', hourActive ) }}.

The part that I was missing was the ['#plain_text'] at the end of the field for the variable.

The other aspect of this solution was configuring the view contextual filter. After some experimenting, the solution that worked for me was to configure the contextual filter as: When the filter value is NOT available: Display contents of "No results found".

I also had to create a taxonomy relationship in the view, so the same taxonomy field used in the store (to toggle Regular or Special/Holiday hours), is used in the Hours content type to connect the two via the view contextual filter.

The result: a user can edit the store, select Regular or Special/Holiday hours, and easily switch between the two. I hope this helps others who have a similar situation.

Hi,
We are migrating to D9 now and plan to have two date entities: Normal store hours and Special store hours. The Normal hours will be the default displayed, then when we need Special hours, we'll develop a boolean solution to toggle Normal off and Special on. The Special hours will be modified as needed, whereas the Normal hours will never change. Does that make sense? Any thoughts or suggestions are welcomed!