lesley

Are you sure the issue isn't just the way your theme displays product images on mobile?

You need to figure out first if the image is the issue. Is there too much white space around the image itself.

I would think that is either how your theme displays them or they might need to be regenerated bigger.

Nope, the image structure cannot be changed. I would not worry about people searching in Google for images, I have had people focus a lot of effort on it to very little success.

There is not, you have to use the default image path system.

The edit button should be under the post to the right corner of it, it looks like 3 vertical dots. But yeah, when people look on the site at the modules, I don't think they will look at the footer, I think having it in the compatibility section would be nice too.

Can you add a note about the support in the compatibility section of the pages? I think that is where people will likely look to see if their versions of thirty bees are supported.

You cannot do this.

I don't think that is the issue. I honestly do not know what it is, but I think its something in the GA account.

I am not sure which ones are causing issues, this is the first report I have seen. As for adding them into the core, I think maybe limited features will be, but it needs to be separate.

What issues?

Can you make a gist, it might do better.

Oh, I meant that your last post was on a topic about Google Analytics not working on a site, not in this thread.

I moved your post, I think you commented on the wrong post. I have tried that in the past, there are a few threads about it. The turn into threads where merchants argue about what they actually need. One group thinks one thing another thinks other things.

I think that is separate. I am seeing by the tawk.to module there is another send pageview request. That might be what its picking up on, but the main script is loaded in the head tag.

Me neither. I am an expert in the US requirements, which are complying with the can-spam act. That is literally our only requirement.... It would be really helpful though to have a list of what we need to change to comply. Then we can look over everything, give a timeline and make sure everyone is compliant before the needed date.

Weird, it might be something configured wrong in your account. If you use chrome you can download and install Google Tag Manager. The tag manager shows you all of the Google Tags on the page and tells you if they are working properly. It says yours is, https://www.screencast.com/t/m9QuPSU1pC8 So it makes me think you might have the account in Google Analytics either setup to http. or www. But I think its in the account since the tag seems to be working.

Would you happen to be using ublock origin?

@zimmer-media To answer your joke, this is what developers have to consider. The EU is the 4th or 5th largest e-commerce market in the world. The top 3 markets do not have these restrictive issues. The top 1 market is 8 times the size of the EU. Of global e-commerce the EU represents about 8% of the world market. It does not make sense to focus a core of a software around such a small market segment. Especially when a lot of the requirements in that market segment are against best practices in the other top e-commerce markets. There are known conversion killers that the EU puts into place. With that being said, I don't want to come off anti-EU. America is the 2nd largest e-commerce market. We do not and will not support about 50% of American tax systems, because they are too complicated to upkeep. To come back to the EU, I have asked many times for people to create something we can go by. All I get is linked documents. I cannot read in french, german, or other languages. But If someone can provide me a bulleted list of what is needed, we can add those features. The whole EU law is a mess. Look at our forums, look at other forums. Users are arguing all over the place of what the requirements are. No one really understands them, I know I for one don't and I have seen our EU members argue over them as well. To sum it up, give us a list. We can try to add as many as possible. When we can cherry pick features out of posts, we add them as well. We have added things to the dev path of 1.1.x from the posts on this forum to help with compliance, but if someone could get us a whole list together that would be the best.

We are hoping that by the time we change things so that modules do not work we have a strong enough foothold that payment companies and other services will already support us. If not we will have to fork their code and support it in house.

I can say with a high degree of certainty that the yotpo module does work with thirty bees out of the box. I just refuse to fork it over and maintain it if they will not provide installation instructions on their site for thirty bees. But our JSON module was written along side Yotpo on a thirty bees installation, that is how we used the yotpo api to grab the rich snippets for the reviews. For payplug, even if they do not support us currently I would test their PrestaShop module. The odds are very likely it works. Because of france and how things are there, we would like to find an agency to partner with in france that is well known to help us land some of the more localized deals. We just have not found one yet.

Sorry for talking in english here, I know French is the prefered language. For Yotpo, it does not look like they are going to support thirty bees. About that all I really have to say is their product is overpriced and I personally feel like they are not a good company to work with. I helped negotiate their deal with PrestaShop many years ago and negotiated a big discount for them becoming a PrestaShop partner. For that I only got silence when I asked them to support thirty bees. A poor way to do business and return a favor in my opinion. On that note, if you use their free plan, our JSON module unlocks their API where you can use the rich snippets from their paid plans without having to pay. Payplug, I can contact them and see what they have to say, I am not familiar with them personally.

It is currently unfinished right now. It should be the same for the prestashop 1.6 branch essentially.

Without seeing the site it is impossible to tell. The core is not doing it, the only way I can see it happening is if you have resources statically programmed in.

This is a 1.7 version module, it will not work on thirty bees.