the.rampage.rado

Open the error, copy it and give it to the model. Give the model context to work with (I use Codex locally, create a local repository and work in it, it makes all the changes, you have to FTP the files to your test server and check if the fixes work). If you work with ChatGPT or other model where you can't give direct access to a repo you can paste also the php code from the file that is at fault. Usua,lly those fixes are very easy (bringing new php compatibility to the code).

I'm about to release my vibe-coded one, but it's perfect that we have an official one from you guys! Can't wait for the link, so I can test it.

Codex or ChatGPT will fix this in one prompt.

This is the idea of this community.

Which page is that? Homepage? Can you open your BO?

This issue is caused by bots that try to delete already empty cart they create I think.

Sorry, my initial answer was not 100% correct. It is not removed in 1.6 as it is, of course, part of the themes. In Niara it was removed with https://github.com/thirtybees/niara/commit/3ab40e7ae52e0c495a2b67f09131996fb6ed65ea (absolutely the same in the Community theme). If your theme still use it you can approach the issue in a different way:

Delete the line. There is no need for this anymore. Or update to 1.6 stable. Where this is removed.

I took few days off.... 😉

Do you have proposal how to fix this 'bug'? I believe it's architecture change that breaks compatibility with many things.

Yes, now drop the spam 🙂

I hope I have something to show in the recent days.

Yes, by using it you don't have to change your csv format. But of course it skips the whole column and if you need some data from there it becomes a problem.

I'm giving an example with Excel: In this case id 2 and 3 will override the price with 0 and not simply skip the import and leave whatever price there was. Empty cell = ;; You are missing one more separator; you are starting with ID, which is empty in the example and you should have it as ;1;test;;; If your example with only 1 row you can set up your import template to ignore those columns: But of course, this does not work in my example above as you won't import any price for 1, 4 and 5.

Yes, I created a feature proposal. Will update you if I can work out something with Codex. We have to be careful which fields we allow this for. If the whole column is empty, you can simply not import it. You can keep it in the csv that generates it, but you can skip it in the import template. But of course, if the column is partially populated, this does not work, as the fields that have nothing between the separators will also be overwritten.