Smile

As soon as I enable Emit SEO fields I get a 404 on FO and BO. Debugging on does not show anything. Its a installation in a subdirectory of the true store. We run 1.0.8 multistore. Does someone knows how to change this setting to of using the DB?

I think most people move to a WMS nowadays, I have used ASM in the past but it did not bring what I was hoping for. I agree an new design would be the best.

I finally found the time to test it. Love it but something I really miss is the option to go back to a product by clicking the title. See attached. It would be great if it is an option to make this possible. Also it would be great if you can choose the order of the fields (shipping address ect.). We use shipping which predicts the time of delivery by exact address. Showing a iframe with dates, pickup locations and more. This is not show now... (myparcel-netherlands).

That's an elaborate answer. Dutch and flemish seems the same indeed. Dutch is 2 times in the table. Normally the url should be indeed nl-NL and nl-BE. But TB uses the 2 letter codes in the url, while as you acknowledge it would be better to make it nl-nl. I think I can decide we leave flemisch for now. And better focus on improving other languages. We should use dutch also for flemisch.

Well is it not a design flaw that only one iso can be used? As explained in the first topic: Well some agency here added it for me. I think in the DB we changed it. And seems to work kind of but not really. Making the conclusion that iso can be used multiple times. Can you tell me how to add flemisch as a language? I mean iths both nl, but really different words... Alos different websites with hreflang.... Attached some DB pictures. Not sure how to proceed.

So here are the test results: Hreflang and multistore: Not working, only those can be found while we have also a nl-BE version running. <link rel="alternate" href="https://website.nl/PvChi2/" hreflang="nl-NL"> <link rel="alternate" href="https://website.nl/PvChi2/" hreflang="x-default"> Use iso codes multiple times: Still not possible in 1.1.0, see attached screenshots. Prevent store to not us a language that is not available for it. Still the store is presenting nl-NL language although it should present nl-BE language. See attached. I can give access to this test environment if needed to investigate. Or send a video....

Thanks, this is a perfect solution! Just made a small fix: {if ($page_name == 'search' || $page_name == 'order-opc')} <meta name="robots" content="noindex,follow" /> {else} <meta name="robots" content="{if isset($nobots)}no{/if}index,{if isset($nofollow) && $nofollow}no{/if}follow" /> {/if}

Just a small issue did arise... I got now double robots tags... Is there a way to solve this also in TB? Or do i have to exclude this one then on certain pages? Or are we missing some setting somewhere? This is generating the top line. {/if} <meta name="robots" content="{if isset($nobots)}no{/if}index,{if isset($nofollow) && $nofollow}no{/if}follow" />

In the end did you found a way to integrate it?

Ohh that easy! Very nice and helpful I learn step by step. Thank you!

Just search and quick-order so respectively I think: order-opc.tpl and search.tpl I guess... We use one page checkout.

Oud topic nieuwe vraag, hoe werkt de dag kiezen ect en bezorg datum in sendcloud?

We had the same problem, we tried to move all addresses to only use address field 1. DB query ect. In the end we did not finish it. Not sure why.

Yes we did, no change... Very strange.

Hmmmm, I am a rather noob in coding. I feel the direction you want to go. Not sure how to do this in my case.

I am looking in a way to add: <meta name=”robots” content=”noindex,follow”/> on certain pages. I tried it with HTML Box pro but is toes not save this rule. Is there an other easy way to get this only added on certain pages in the header? Maybe an enhancement for next version?

I would like to get the watermark module working also with webp format. See topich here for more details. I am willing to support it if we can come to a reasonable price 😉

Did you in the end find a good solution? We are currently trying to achieve the same in the long term. We first now work on a WMS and then we will look at other systems for POS ect...

Are you interested and or how should we proceed? No idea of the cost...

Hmmmm, it here a solution to that? How much time would it cost to get it also working with webp and make it a TB module? Very much interested in sponsoring it.

Well that can be the case 😉.... But in reality I have generated all product images again an and in product categories they are webp but on product pages they are still jpg.... @datakick thanks for your help all the time!

I noticed that not all product images where generated in Webp format. Investigating this I came along the following comment "Serve smaller images in the webp format to browsers that support it". Why can we not just generate also the bigger product images in webp format? Reading a bit about webp did not give me the answer....

I am generating new pictures with webp. But the webp images do not include the watermark. I am runnin TB 1.1.0 and Watermark v1.1.0 - by PrestaShop. Is this a known issue? The right sizes are ticket (Just ot be sure I ticket them all 🤣) in the watermark module.

Finally found it, could not change it in php.ini or cpanel, or .htacces, had to do it in user.ini Thanks all!

Well seems the execution time while in the php.ini it is set to 1000.... Maybe somewhere in the VPS it is overruled? Row 363 is red. ThirtyBeesException Maximum execution time of 120 seconds exceeded in file classes/ImageManager.php at line 363 Source file: classes/ImageManager.php 344: // Author: Tim Eckel - Date: 09/07/07 - Version: 1.1 - Project: FreeRingers.net - Freely distributable - These comments must remain. 345: // 346: // Optional "quality" parameter (defaults is 3). Fractional values are allowed, for example 1.5. Must be greater than zero. 347: // Between 0 and 1 = Fast, but mosaic results, closer to 0 increases the mosaic effect. 348: // 1 = Up to 350 times faster. Poor results, looks very similar to imagecopyresized. 349: // 2 = Up to 95 times faster. Images appear a little sharp, some prefer this over a quality of 3. 350: // 3 = Up to 60 times faster. Will give high quality smooth results very close to imagecopyresampled, just faster. 351: // 4 = Up to 25 times faster. Almost identical to imagecopyresampled for most images. 352: // 5 = No speedup. Just uses imagecopyresampled, no advantage over imagecopyresampled. 353: 354: if (empty($srcImage) || empty($dstImage) || $quality <= 0) { 355: return false; 356: } 357: if ($quality < 5 && (($dstW * $quality) < $srcW || ($dstH * $quality) < $srcH)) { 358: $temp = imagecreatetruecolor($dstW * $quality + 1, $dstH * $quality + 1); 359: imagecopyresized($temp, $srcImage, 0, 0, $srcX, $srcY, $dstW * $quality + 1, $dstH * $quality + 1, $srcW, $srcH); 360: imagecopyresampled($dstImage, $temp, $dstX, $dstY, 0, 0, $dstW, $dstH, $dstW * $quality, $dstH * $quality); 361: imagedestroy($temp); 362: } else { 363: imagecopyresampled($dstImage, $srcImage, $dstX, $dstY, $srcX, $srcY, $dstW, $dstH, $srcW, $srcH); 364: } 365: 366: return true; 367: } 368: 369: /** 370: * Generate and write image 371: * 372: * @param string $type 373: * @param resource $resource