led24ee

So there is not easy way to add additional field to "Client address" for e-mail ? Client primary address remains the same, just add field named CC (Carbon Copy) ? Or even this need also core modification ? For example shop e-mail has this functionality. And yes, I have no idea how this is done.

Ever heard that there are companies where is more than 5 employee ? And they have even financial department. And what a surprise, there are clients who just send letter what they need. They don't log in, they don't search or select something. They just ask and it is my business to find proper item, make invoice and organize transport. Of course if You have never heard about B2B then this may be new. But attitude like this is main reason TB is not popular. There is always some smartass who thinks that things that he has never heard are only for idiots. If You don't have solution then it is pretty easy to just skip this thread.

This was created for completely another purpose and this leaves only one e-mail. I need add another e-mail for invoice, but also keep existing email. Theoretically this can be as CC: or BCC:

Is there any solution for client have multiple e-mail ? f client need that invoice is going to some other place (finance department for example), but conversation is with current address ? So invoice is going to two different e-mail. Thank You

What is the point of forum when everything must be in github ?

It's as good as dead. Is there any suggestion for alternative ?

Well, I just tried and even if the pictures are in same server I got this error. So probably this test shop is damaged. This was anyway for purpose to find out any error in CSV file itself. But now I better make fresh install for test shop.

There are two shop. Both with separate IP. I use this exact CSV with both. Error only appears when test shop is trying to get images that are in other shop image folder. So this can be some server limits or rules. Both shop are using PHP8.3 and TB1.6

Is this real thing ? First my browser (FF) can't download it, because there is some virus. If I still mange to download then in testshop I got warning that this doesn't contain what is expected.

Well, it obviously is in wrong place. There is one thread about CSV import. I was pretty sure I used this. Sorry.

TB 1.6 gives this on CSV import: Errors occurred: Image entity products not found Image entity products not found Image entity products not found Image entity products not found Image entity products not found What can be cause of this ? Pictures in CSV file point to URL and these pictures are correctly visible when I put this address in web browser. So address is correct and file is also present. Any idea ?

I'm still waiting for slider option for this module "Block Layered navigation". Is this ever gonna happen ?

In Estonia next year must be also.

I have so many errors that I'm not sure is this caused by TB or not. So I can't report nothing. I have transport module where developer renames database table and then he forgot to put this in every update. ...only 2 hours to find out. And after this he also put some new column and again this was only in next update. So if You don't update every time but for example after 3 or 4 version then You got constant headache and compared with medium grade hangover this hangover is like paradise. In my case this transport module blocks all possibilities to make changes in product ... Then I found another payment module where is error in syntax. I gave all info to developer and answer was "This is impossible to fix." Then I sent video (half minute to google) where is shown fix to this error and it takes about 30 second to fix. After this I haven't get any answer from developer. Here (I mean TB) you got answer, maybe this would be not solution, but in any case this is better than silence. Bad thing is that my coding skills can't be measured, because there simply isn't any. I keep trying, but maybe is better to build all from zero.

For me almost all payment and transport modules stopped working. For transport there is bug in this module, this is not caused by upgrade or TB. And some old module start working again. So there are some changes that can't be easy "to digest"