lesley

I think you will have to use a commercial module, or with an override and a modification. The dh42 ones cannot handle that.

Sure, that would be awesome.

Oh, and thanks for the contribution, every little bit helps.

Oh, we haven't, it will make it in the next release, we just have been working on a couple internal projects.

Which pull did we dismiss of yours? I did not realize we did one.

Presto-Changeo's sagepay module works with thirty bees, we have a few clients using it.

What about something like this, https://app.moqups.com/dh42/9CwbH6iqf5/view

@wakabayashi I don't know if you noticed, but we merged the heart of webp into the .4 release the other day. It will not be enabled until 1.1.x but we put it there for people that like to experiment.

I am not understanding, is he not finding the upvote buttons?

You have to set to use png's in the Preferences -> images section of your back office.

Possibly, you would need to test it though.

It looks like you are using localhost for your elastic instance, it might require you to use a domain name instead of a local host. @mdekker might be best suited to answer this one.

I am not positive, but it might require a domain name being attached and then adding a content policy for the domain.

It sounds like then you need to set the cors policy of your local instance to be able to connect to your elastic instance. https://enable-cors.org/server_apache.html

Every site no matter what the content is, is people login or not, needs to have SSL on every page by default. We will be removing the cart / contact only ssl in the future and try to push for ssl by default on installations.

Are you using the domain thirtybees.local? Or is that something we left in the module?

We would need to add a button though.

This would take a 3rd party module to do. I don't know if any support custom images though.

This is going to be fixed in the latest build, I just changed the build script to add them.

It would still need p tags for wrapping.

A lot of it has to do with the location. The short description is more versatile than the long description. The long description displays in one spot, the bottom of the product page. The short description displays in several spots, it can be displayed in any product-list, category pages, on the product page, ect. For flexibility, it could be changed to be in a div tag, but it would require people to update their themes. Also, it does help keep a site consistent. People tend to mark things up and use large fonts when allowed and it makes category pages look bad.

@wakabayashi Not really, here is the idea. It is in p tags so it can be targeted effectively. Also by default, we strip the html out of the short description. The mess of the change between list view and change between grid view uses a lot of javascript to target and move things, so not having it in a p tag would make it impossible to target and adjust that layout.

I know Yotpo does, https://support.yotpo.com/en/article/exporting-reviews-from-yotpo and also TrustPilot, https://support.trustpilot.com/hc/en-us/articles/204868067-The-Service-Reviews-page

No, it means a bug in our release candidate version.

Hmm, this might be a regression, we will get it checked out.