Dolfijn

Ah, I understand why you couldn't find it. It is all very confusing. The PrestaShop V2 is the name of the integration in the SendCloud platform. Which will be active from May 12. So, there is no V2 plugin version but a V2 PerstaShop integration feature in Sendcloud platform..

Not yet. It will be my next step in a few days (have to finish some other work first). I'll post my findings under this topic.

I received the answer. It is indeed a little bit different: Start quote: "From 12th May, 2025 we will deprecate the our PrestaShop V1 module which is the module you mentioned. We are not deleting the V1 module immediately, but we will no longer provide fixes or support. Our PrestaShop V2 module will be the main module for working with Sendcloud and PrestaShop from May onwards. As you mentioned, our V2 module is compatible with PrestaShop versions 1.7.0 to 8.2 but not 1.5.X. If you do not update to the PrestaShop V2 module before 12th May, your orders may stop importing to Sendcloud from PrestaShop. Switching to PrestaShop V2 ensures merchants stay compatible, secure, and benefit from all the latest improvements." End quote. So, as I understand it, from May 12, SendCloud will only use version 2 of the plugin, which will only support PS1.7 or higher and the developer of the version 2 plugin confirms that TB 1.5.x is not supported. This is bad news for every TB user that relies on the integration with SendCloud. Is there a way to get out of this situation, without the obvious solution of migrating back to PrestaShop?

Yes, I agree. In the mean time, I asked the developer just to be sure. If I have an answer I'll post it here too, for the record.

Thanks for your reply. I also asked SendCloud if they could clarify what is supported and not. And i must say that they responded with an clear and concise answer. Long story short. There integration will not accept any PrestaShop API older then 1.7 from early may 2025. So, I guess the only thing I can do is asked the developer of the plugin if it acts like PrestaShop 1.7 or higher, while using TB1.5.x. If not, I have to migrate back to PS 8? Not my preferred scenario, to say the least.

I'm not sure. It looks like this in the TB admin area (picture attached)

When working in the SendCloud portal, it always says: 'PrestaShop v2 is now available. Switch to the new integration to unlock new features.' I always ignored it but now it will be enforced (from May 2025). Does the TB SendCloud module support this new integration?

You can also add: https://www.gquipment.com

It solved the problem 🙂

Ok, I'll try that. Thanks for the reply

I get this error in the SendCloud integration log. I copied the message exchanged. Looks like I can't use the SendCloud integration anymore at this moment. What is happening? I'm using TB1.5. As far as I understand, it (sendcloud) is asking for an url (/currencies) that is not supported by TB? { "id": 626504775, "base_url": "https://www.gquipment.com", "full_url": "https://www.gquipment.com/webservice/dispatcher.php?display=%5Bid%2Ciso_code%5D&ws_key=***************************&url=currencies%2F", "method": "GET", "response_code": 401, "response": { "body": "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<prestashop xmlns:xlink=\"http://www.w3.org/1999/xlink\">\n<errors>\n<error>\n<code><![CDATA[26]]></code>\n<message><![CDATA[Resource of type \"currencies\" is not allowed with this authentication key]]></message>\n<additional_info>\n</additional_info>\n</error>\n</errors>\n</prestashop>\n", "headers": { "Date": "Tue, 17 Sep 2024 09:41:25 GMT", "Vary": "Accept-Encoding,User-Agent", "Server": "Apache/2", "Connection": "Keep-Alive", "Keep-Alive": "timeout=2, max=100", "Access-Time": "1726566085", "Content-Type": "text/xml;charset=utf-8", "PSWS-Version": "1.6.1.999", "TBWS-Version": "1.5.1", "X-Powered-By": "PHP/7.4.16", "Content-Length": "234", "Execution-Time": "0.004", "Content-Encoding": "gzip" } }, "request": { "headers": { "Accept": "*/*", "Connection": "keep-alive", "user-agent": "SendCloud/1.0 (prestashop; https://www.sendcloud.sc)", "Authorization": "**********************************************MVk6", "Accept-Encoding": "gzip, deflate, br" }, "payload": null }, "created_at": "2024-09-17T11:41:25.359375+02:00", "exception_type": null, "exception": "Error 401 (Unauthorized): We can't access the integration to request the orders.", "protected": false, "additional_data": "", "formatted_date": "17-09-2024 11:41:25" }

Ah, found it. I was looking in the Admin folders. Thanks again!

Sorry, I missed your reply. Thanks for the clarification. I find on the Internet that you can put them in the sitemap, but only as a location. Also, google does index pdf files :-) Only question I still have is where the TB code that generates the sitemap is located. Can't find it 😞

They made an typo in their server name that is linked with my service account.

I'm using the SEO sitemap module and i did not check the option to exclude attachements. But, they are nowhere to be found in the sitemap. The attachements in my case are datasheets, so valuable from a SEO point of view. Google doesn't index them. First, because they where blocked in robots.txt (if have fixed that) but now it is 'complaining' that they are not found in the sitemap. I'm happy to have a look at the code by myself but I can't locate it. I would have expected it somewhere in the Admin folders but can't find it. So, where is it 🙂