MockoB

No logo on my iPhone X either. You should use jpeg fallback for your logo in the tpl file I believe. Actually it tried to load something for part of a second but I’m not sure if it was the logo... it was something pink I think ...

Looks fine, just when I choose already registered, there is no way to change my choice. I have to go back and enter the checkout page again. Is it some kind of module you are developing or it is just page modification?

Try the 1st post.

It’s the same eu compliance law in Bulgaria (not gdpr) which everybody should adapt. It’s other thing that nobody is compliant with it ... Even more there is additional, local law in Germany, something about telecommunications i think it was, which is another win for the greedy lawyers there. As far as i know some Germany lawyers make a living by making merchants miserable.

They still can sue you like person, after all they could be your customers.

So lets hope they will support ps 1.6 or tb in future releases ...

You mean you use other mollie module, different than the one deveoped by the above mentioned pll?

Does the module have any support? Since @mdekker and @SnowyCat obviously don’t want to be associated with tb, what will happen with your payments if an update is needed?

I'm sure if you ask @datakick he will give you another free trial. And if you choose his module, I'm sure you will receive the best support ever!

Comment out the lines in the corresponding tpl files. I'm not sure if there are two of them, maybe one for logged users and one for guests. But you should do it next time you update the store also. I don't have tb installation at the moment so I can't tell you which the files are exactly, sorry.

@yaniv14 just solved it! Thank you! The reason for the issue is that the variable of the image of the blog is not used on the blog page itself and blog categories. It is used just on the article pages. So the code bellow checks if the variable is on the current page, if not, then serves the provided by me image: or you could use {$logo_url} instead https://your.site.here/img/desiredimg.jpg in the above code. But usually the logo img width/height don't fit the facebook recommendations.

Thanks @lesley Everything is working great, just the image property for the blog is set wrong. Same thing is with topic property, so I will give example with it. I need to associate both links below with blog property https://my.site.com/blog https://my.site.com/blog/category-number1 https://my.site.com/blog/category-number2 ... And to associate all topics with topic property https://my.site.com/topic-number1 https://my.site.com/topic-number2 ... Like I set it at the moment all links are associated with "topic" property, because I get the link from $page_name variable for the blog module. I need to specify different links like explained above for "blog" and "topic" properties. There are specific parameters for categories and topics. I don't know if they could be distinguished by those parameters...

I'm trying to update my open graph tags recently but I have an issue with the blog images, so little help will be appreciated. Here is my code below: {if isset($meta_description) AND $meta_description} <meta name="description" property="og:description" content="{$meta_description|escape:'html':'UTF-8'}" /> {/if} <meta property="og:url" content="https://{$smarty.server.HTTP_HOST}{$smarty.server.REQUEST_URI}"/> <meta property="fb:app_id" content="12345678910"/> <meta property="og:site_name" content="{$shop_name|escape:'html':'UTF-8'}"/> <meta property="og:title" content="{$meta_title|escape:'html':'UTF-8'}"/> <meta property="og:type" content="{if $page_name == 'product'}product{elseif $page_name == 'blog-module'}article{else}website{/if}"/> {if $page_name == 'product'} <meta property="og:image" content="{$link->getImageLink($product->link_rewrite, $cover.id_image, 'thickbox_default')|escape:'html':'UTF-8'}"/> <meta property="og:image:width" content="664"> <meta property="og:image:height" content="500"> <meta property="og:image:alt" content="{$meta_title|escape:'html':'UTF-8'}"> {elseif $page_name == 'blog-module'} <meta property="og:image" content="{$blog_article_img|escape:'html':'UTF-8'}"/> <meta property="og:image:width" content="713"> <meta property="og:image:height" content="356"> <meta property="og:image:alt" content="{$meta_title|escape:'html':'UTF-8'}"> {else} <meta property="og:image" content="https://your.site.here/img/logo.jpg"/> <meta property="og:image:width" content="1124"> <meta property="og:image:height" content="614"> <meta property="og:image:alt" content="{$shop_name|escape:'html':'UTF-8'}"> {/if} So my issue is with the blog module image property. It's fine if the shared link is the blog topic, but if I share my.site.com/blog the debugger tries to pickup the image I associated above. How could I assign image for the blog page (and categories) and separate image property for the articles. PS: This code is working on PS 1.5.6.1 so it should be working on thirtybees most probably also. The only thing to change is your images width/height, the the link of the additional logo (I had to add instead the default one) and of course you should remove the blog mentions and associated code, or change it with your blog page name.

Thanks for supporting the project @datakick it makes me more confident about it's future! You too @Traumflug !

Yes, but usually the URL is generated by the meta title and I rarely change it. And I will definitely need to add numbers in many of my product urls. I'm pretty sure it's not only me. For example I can't have www.mysite.com/mobile/iphone16gb or www.mysite.com/mobile/iphone32gb in case I don't need them as attributes but as different products ... you get the point.

What if I have 30 identical and in same time unique products? I usually use same meta title with the reference number included to avoid duplicates (same friendly url also). It's definitely a bug, so you should add it to the list in github.

@yaniv14 just curious, which tb version are your shops running with?

I think he means that without full page cache, thirty bees is just prestashop 1.6 with clean urls... he maybe doesn't know that there are thousands other fixes in the core and things are not that simple! I just being sarcastic, again. Just ignore me :)

When I tested the demo on my iPad, I can't select the payment method. It could be a bug or related to the above mentioned by others, I don't know. Here is screenshot of my iPad:

With 93 issues still open on github, you would like to give your precious time to break the compatibility with 1.6? After all, that was one of the fundamentals of the project! If you want to make something good for the project then read the feature requests on your page. Yes, there is such section!

Everybody deserves a break, it just looks his break is endless... Is it @mdekker, do you plan to participate ever again in the project?

:smilingfacewithopenmouthsmilingeyes:

@toplakd where your confidence comes from? Do you know something that the rest of community doesn't? It would be nice to share your observations concerning the current state of the module, since there is no one else related to it, who wants to share any news...

Thanks for the detailed explanation @datakick ! I really prefer SVG instead other conventional images and don't care about those additional 5k. But my preference is because it's sharp and clear on all devices, not as sophiticated as yours :)

I don't know really, but I see a lot of issues with cache and other stuff. And actually I can't think of nothing which deserves to update it. I know that 1.0.3 is really stable, although there are also issues with it, they are not so serious like the ones in next versions. Really if there was change log, everyone could decide by it's own. Personally the advantage of updating was lazy loading, retina images, webp standard and the fav icons. And just the one of all those is working, and it could be added to your site by simply applying the commits. I wouldn't recommend experimenting with your live site, but its personal decision. If something works, just don't break it.