undecided

Update: If I set "Shop default currency" then the PayPal module appears at any time regardless the currency someone has selected on the website. So that little part is solved. The main problem still exists. The customers jumps to PayPal and the amount to pay will be shown in his selected currency and not in AUD. When the customer then tries to pay he gets the message that the currency is not supported, which is correct but not what I want and also not very helpful as the customer will get no information which currency is supported. I "simply" want that the customer sees AUD on the payment page of PayPal no matter what currency he has selected in the shop. Any ideas how to achieve this.

I have a maybe unique question/problem. If PayPal is used for paying, I only want to accept a specific currency when the payment is processed. Currently I make the same thing on a PrestaShop 1.6 with the old native module. The customer can shop in all available currencies (eg. USD, AUD, CAD, EUR, CHF), but when pressing on "Pay with PayPal" at checkout, the amount the customer is being charged is always AUD (which means that I only receive AUD payments from PayPal). If I select AUD as restricted currency in TB, the PayPal module does only appear when AUD is selected by the customer in the FrontEnd. If the customer shops with EUR, PayPal does not appear and if I set "customers currency" under currency restrictions, the customer can pay with all available currencies which I do not want to happen. Is there a way to achieve this or do I have to use the old PS module?

The native PayPal module does not work as it claims that there is no TLS 1.2 support. As I know that this message is not correct (my servers supports even TLS 1.3 and stripe is working as well as PayPal on a PrestaShop 1.6 installation), I am wondering if I can bypass the modules TLS check so that PayPal appears on checkout page. Edit: The problem that PayPal did not appear was not the TLS, but the fact that the currency was restricted to a specific one which I had not used when testing it.

How can I achieve that instead of the email address a link to the contact page is displayed in the footer? (I am afraid of getting lots of spam when showing the email address direct in the footer) When using PrestaShop 1.6 I solved that issue with the following change in the blockcontactinfos.tpl but either I am missing an other change I cant remember or it is not working with TB or the Cisero Theme. Change of PS 1.6 blockcontactinfos.tpl {if $blockcontactinfos_email != ''}<li><a href="link to page"><i class="icon-envelope-alt"></i></a>{l s='Contact us' mod='blockcontactinfos'}</li>{/if} BTW, I don't need the envelope icon, a simple link named "Contact Us" which can be clicked to come the the contact page would be enough. Code of blockcontactinfos.tpl in Cisero Theme {if $blockcontactinfos_email != ''}<li>{l s='Email:' mod='blockcontactinfos'} {mailto address=$blockcontactinfos_email|escape:'html':'UTF-8' encode="hex"}</li>{/if} EDIT: Problem solved as follows {if $blockcontactinfos_email != ''}<li class="item"><a href="https://domain.com/contact-us" title="{l s='Contact us' mod='blockcms'}">{l s='Contact us' mod='blockcms'}</a></li>{/if}

I think you have expressed your feelings in many posts over the time and as you can't see any future, I really recommend to evaluate a different system and change as soon as possible. To succeed i that, I'd like to give you an advice. Invest the time in research and building up a new shop rather than grizzle here about what is going wrong or should be done.

It's not only cloudflare or other CDN's, but I do not know the reason for the issue. In the past I never have been logged out automatically, but after I changed the server (same hosting, just service upgrade) I faced the same problem of being logged out automatically and I do not use any CDN. As the problem was solved with disabling the cookie check I have never searched for the real reason, but if somebody might have some idea it would not be bad to know the reason.

Go to administration - preferences in the Admin panel and set "Check the cookie's IP address" to NO After that clear your browser cookies and cache.

In my opinion, the basic thinking is right, but maybe not great explained with talking about to fix a bug. If there is a bug in the software, it should proper be explained so that it can be fixed by the "owner" oft the software or someone else. This should not be connected to the term of being paid by the one how discovered the bug. However, nobody can expect the bug to be fixed within a certain time and might life with the possibility of it being not fixed at all. The overall problem is that for most people open source is equal to free of cost.

You might consider to set up a demo for front and admin so people can check out ME before install it.

Thanks for sharing the information. In that case, it is handling the gift cards also as simple cart rules and does not cover shipping cost (unless you offer free shipping).

May I ask how that module is handling the gift cards at the checkout? Can the shipping cost also be paid by the gift card or is it also a simple cart price rule?

I have also used the free module GiftCard3. The only downturn is, but I guess also for some paid modules, is that the gift card can only be used for products (it uses a voucher, cart price rule) and not for the total amount, which means that if you do not offer free shipping your customer will have to pay the shipping cost with credit card or whatever.

Never said it does not look beautiful. I personally like the look of the default theme (niara), but compared to other default themes like Spree or PS 1.7, it looks old fashioned, but yes, you can handle that with some work on it. What I have more in mind is the admin area which I am very used to, but the design of the 1.7 admin area (even though it's completely finished) makes work a bit easier. As for now, I stay with PS 1.6 and really hope on the new team to bring TB back on track (at least with the basic system of improvements and updates, the design is secondary). Since I have learned a lot about the structure of PS 1.6 it's much more easy for me to make changes there or in TB than in the new Symfony framework of PS 1.7 or even a complete new shop system.

That is one reason why we tend to switch to PS 1.7 in case the TB project does not get a future and a fresh design and have dismissed opencart as well as modified which we were considering as an alternative. We are really hoping that the new guys at TB will get back on track and might find the time to fresh up the design (not only the visible shop, but also the admin area).

Frankly speaking, I'm still with PS 1.6 as there was no reason for change in the beginning times of TB and later there were some issues (uncertainty about the future of TB) that kept me away from using TB as productive system. Now I will see what today's outcome about the future if TB is and then decide if I'll keep an eye on TB or another system as we plan to update our shop in 2021. The best would be TB, but if we don't see or have the feeling that it will be a successful system, we think of giving PS 1.7 a chance.

Let's see if it's like the Brexit with last minute agreement or if it will be a fork.