Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

the.rampage.rado

Members
  • Content Count

    250
  • Joined

  • Last visited

Community Reputation

25 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. the.rampage.rado

    Warehouse up to date ?

    If you use it hooked to the side you can use TB version of layered. But I use it on top of product list for all my shops and the merge procedure is too complicated for me so I use the good old moded version that comes with latest WH.
  2. the.rampage.rado

    Warehouse up to date ?

    Warehouse seems to work just fine with php 7.2 and TB 1.1.0 if you fix one file and follow the steps in the 1.1.0 topic.
  3. the.rampage.rado

    thirty bees 1.1.0 is released!

    OMG, I knew I'm missing something!!! But why I have made changes to product.tpl and many others over the years and I had no issues with "Never recompile template files"? Fix: - change the order-carrier.tpl file as described above. - in performance set "Template compilation" to any of the later two options. - enable caches - turn back to 'Never recompile template files"
  4. the.rampage.rado

    thirty bees 1.1.0 is released!

    I did disable all caches, cleared them from backend, then manually deleted all the rest files in /cache/smarty. Also disabled cloudflare (put it in dev mode) and used chrome in incognito mode to try and use OPC. Then tried ctrl+r and f5 to probably refresh it's cache if it's stuck. No luck with all this. This is on php7.1 if it makes any difference. Tried php 7.2 - works just the same - error 7.3 - db link error
  5. the.rampage.rado

    thirty bees 1.1.0 is released!

    Exactly the same - no change at all. Like the file was not changed.
  6. the.rampage.rado

    thirty bees 1.1.0 is released!

    Hello @smarterweb just compared your version - it's the same as mine and it's not working for me. @datakick also tried to help with the same fix but with no luck.
  7. the.rampage.rado

    No Captcha reCaptcha Module not showing on one page checkout

    Can you send me a link in PM?
  8. the.rampage.rado

    thirty bees 1.1.0 is released!

    Again no luck for me. Can you attach your fixed file so I can compare mine with yours. Probably I'm making some lame mistake. I've turned 5 step checkout but it on it's own have some issues and I would like to return to OPC.
  9. the.rampage.rado

    No Captcha reCaptcha Module not showing on one page checkout

    I tried with latest firefox and latest Chrome both of them have no issues displaying the captcha in account creation with the following settings: 1. TB side of things - only account creation, 1.1.0 and Warehouse and on other websites - edge before 1.1.0 and Warehouse 2. module side of things - yes, 0, 0, 0, 0, yes till the end. If you switch to any number above 0 on Login attempts the captcha is shown but ignored - I had the same issue with the module - lots of Russian bot regs but it is a known bug since then. Think @datakick found out. it should be fixed soon.
  10. the.rampage.rado

    thirty bees 1.1.0 is released!

    Probably try to disable/clear your caches before the update?
  11. the.rampage.rado

    Modules to be updated - HELP

    Yes, sorry, this was a known bug and you've found the solution. :)
  12. the.rampage.rado

    Modules to be updated - HELP

    In most of these modules you won't see the change (it's internal documents/licensing/etc). Some of them are bugfixes and few of them introduce something new. I don't remember any of them to have any change in behaviour so I don't think you should be afraid to update. BUT YOU SHOULD MAKE A BACKUP OF YOUR FILES AND DB FIRST!!!
  13. the.rampage.rado

    thirty bees 1.1.0 is released!

    I'm reffering to this fix:
  14. the.rampage.rado

    thirty bees 1.1.0 is released!

    I updated to 1.1.0 with latest warehouse but I experience the bug with OPC and the fix does not work for me? Can someone help? It seems I have issue with order-opc, not order-carrier - It's exactly the same issue but strangely this will not fix it.
×