Jump to content
thirty bees forum

elund

Trusted Members
  • Posts

    56
  • Joined

  • Last visited

  • Days Won

    9

Posts posted by elund

  1. 1 hour ago, colorful-ant said:

    panda is not ready for tb (1.1.x) bleeding edge
    only manual update

    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.

  2. 10 minutes ago, vzex said:

    Can you please tell me what version thirty bees you are on to see the Panda update?

    I am on TB 1.1.0

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

    • Like 1
  3. On 5/1/2020 at 12:19 PM, Kashir2000 said:

    @Traumflug There is also another thing. There are not many people wanting for TB to rise for one simple reason: Having to maintain compatibility for 2 shops. A lot of devs dream of 1.6 being put to rest (yes, they also hate Prestashop 1.6), as 1.7 takes over. Maintaining backward compatibility with 1.6 (and/or TB) is additional work. So basically it's not personally aimed at TB or you guys, it's aimed at lowering costs and maximizing income. Because of state of 1.7 I'm seriously thinking about changing my business model. I don't want to be held responsible by my clients for bugs in 1.7. Still, my clients I migrated to TB expect FROM ME modules for prestashop to work or fix them. Their mentality is like: "If I had Prestashop, it would surely work". So either I go on war with them or comply with their insane requests.

    It's a shame, but this brings a lot of regret to devs like you and me.

    PS: Also, when I recommend thirtybees and explain all differences, I'm being held responsible for recommending it to clients. Some people are insane, and blaming their decisions on others. And saying "Prestashop would be better". That's where "brand" part comes in.

    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 😉

     

    • Like 3
    • Thanks 1
  4. 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?

  5. @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.

  6. I have experience 2 issues after upgrading from 1.0.1 to 1.0.2.

    1. 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.

    2. All my logos were replaced by a Thirty Bees Logo. That's of course easy to fix, but what is the purpose of this? ;-)

×
×
  • Create New...