elund

My test shop is actually running Panda on TB 1.1.X., and I have not seen any problems so far. I did a manual update of Panda, since I don't have any license to my test shop.

I am on TB 1.1.0 I will do a backup before upgrading, but looks fine on my test shop.

Looks like it works fine for me: I was actually not aware of this 1-click upgrade for the Panda theme, so thanks for the tip 🙂 Best regards, Elund www.prospeed.dk

Good to know. I have only bought their GDPR module and it works out of the box.

@Havouza It's my impression that most well programmed PS 1.6 modules works with TB. Have you tried this FREE PS module: https://addons.prestashop.com/en/payment-card-wallet/24922-stripe-official-sca-ready.html ?

As long as the ThirtyBees community is not stronger as it is today, I think it make sense to maintain the compatibility with PrestaShop 1.6. There are really many good modules for Prestashop 1.6, but if you skip the compatibility, then there are suddenly no additional modules available to enhance the functionality of your shop to suit your needs. Since Prestashop 1.6 doesn't change much anymore, it doesn't necessarily cost extra money to keep the compatibility. You should just not change the architecture of ThirtyBees 😉

Hej Gitte Is it the Canonical URLs module from Linea Grafica that you are using, because I am considering buying it? Are you still using it? If yes, do you still need to modify core code? And are you satisfied with the module? Best regards, Elund www.prospeed.dk

Yes, sorry - server side caching was still activated for my shop

I have the same problem with tbupdater v.1.4.0 and cache is disabled in settings.inc.php: define('PSCACHEENABLED', '0'); if this constant is not used anymore, why not just remove the check in the tbupdater module?

I received around 50 spam mails before my host provider stopped all mails from my shop. Is there a newer version than 1.1.0 of the module?

@datakick - My login attempts is already set to zero, so this doesn't help me. @the-rampage-rado - Which free PrestaShop module did you install instead of the Thirty Bees module? I use the Panda theme: https://www.sunnytoo.com/product/panda-creative-responsive-prestashop-theme. @SLiCK_303 - did you get your spam problem fixed?

Nice - I didn't know this override check module, but looks like the nocaptcharrecaptcha override is active: Also override is not disabled in the settings:

The module "No CAPTCHA reCAPTCHA" is installed on https://www.prospeed.dk and I have not recieved spam mails for more than a half an year. Suddenly without changing anything I started recieving russian spam mails a few days ago. My host provider tells med that it is not enough to have a frontend implementation, because you can make a "POST" request directly to the url https://www.prospeed.dk/kontakt-os. So a validation must also be done in the backend. Does "No CAPTCHA reCAPTCHA" by Thirty Bees do validation in the backend? If yes, how do I troubleshoot? If not, can anyone recommend another CAPTCHA module?

Wauw, that fix my issue after the upgrade to 1.0.4. Thanks a lot :-)

Where is "displayDiscountPrice" defined and set?

@traumflug said in Problem with price on product page after upgrade to 1.0,4: Hmm. @yaniv14 can't reproduce this on 1.0.6, see comment on the Github issue. Which leads to the question: what is different between your installation and Yanivs? Any additional modules? A custom theme? Does it happen with new products as well (it might be result of something stored in the wrong place in the database)? I use the TB compatible Panda theme from https://www.sunnytoo.com/product/panda-creative-responsive-prestashop-theme. If the line below is the only change to the community theme, then it unfortunately doesn't help me, so I have to investigate further. ~~if (discountedPrice != 0) {~~ if (displayDiscountPrice != 0 && discountedPrice != 0) { SInce it worked before I would assume there must have been a correction to the core code causing this issue. The correction to the core can of course be the right thing to do.

This is still a problem in version 1.0.6

The Vagrant file uses a provisioner called Ansible. The ansible playbooks can be found in the playbooks folder So far so good - but to get a jump start - in which YAML file can I add PHP config? I would like to add XDebug configuration to the php.ini file.

With "$ git clone https://github.com/thirtybees/vagrant" you get version 1.3 of Thirtybees (TB) You can then set the TB version in the file /playbooks/roles/thirty-bees/tasks/main.yml. But what do you then do next to get (update) the TB-version (for instance version 1.5)?

Looks like you have changed the Web Service API back to Prestashop structure in TB version 1.0.4? Why? After upgrading to version 1.0.4 (and 1.0.5) I had to switch from the thirtybees API to the Prestashop API, to get the integration with pakkelabels.dk (package label) to work again. By the way, pakkelabels.dk support the Thirty Bees community with this module.

Besides graphvisifire you also have to delete the GraphGoogleChart and GraphXmlSwfCharts modules. These 3 modules are not mentioned in the upgrade process, but after deleting these 3 modules, ThirtyBees works fine

@the-rampage-rado said in Problem with price on product page after upgrade to 1.0,4: Are you sure your config is correct - special price? Such bug was present on PS where the 'you save' amount was changed with the savings amount. Yes, I am pretty sure - or at least - it worked fine before the upgrade ;-)

After upgrading to version 1.0.4 I have problems with the price shown on the product page when using quantity discount as shown below. Is this a bug in vesrion 1.0.4 or a compatibilty problem with my theme and version 1.0.4? It worked fine with version 1.0.3.

I have experience 2 issues after upgrading from 1.0.1 to 1.0.2. Duplicate URL Redirect V1.5.1 from http://www.presto-changeo.com causes the error "Too many redirects". Have you done done changes in version 1.0.2 so that this module is maybe not needed anymore? It does NOT help to disable and enable freindly URL to regenerate the .htacess file. So I need to disable the module. All my logos were replaced by a Thirty Bees Logo. That's of course easy to fix, but what is the purpose of this? ;-)

It was actually not my intention to start using a test framework. I just want to use a debugger. Regarding the PHPUnit error I had used a wrong run/debug configuration. Now I have set it up like shown below. It's probably not quite correct, so a few hints would be nice.