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.

smarterweb

Members
  • Content Count

    72
  • Joined

  • Last visited

Community Reputation

16 Good

Information

Recent Profile Visitors

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

  1. yes, just tested on vanilla PS 1.6 and works without issues. One module I can't even open, I get: ThirtyBeesException Unable to load template 'file:./_partials/header.tpl' in './layout.tpl' in file vendor/smarty/smarty/libs/sysplugins/smarty_internal_template.php at line 185
  2. Hi, we now have more and more modules that don't work in TB latest stable 1.1.0. Some module developers will not even support their extensions for TB and charge extra money just to make them compatible. If ThirtBee's code changes so much so that PS 1.6 modules are no longer compatible, that's a real worry. How do we best go about this? I s there something like a module converter so we can continue buying modules made for PS 1.6? Will someone from the TB team look into these issues or are we just left by ourselves and having to employ devs to fix the incompatible modules?
  3. then please tell me how to debug something like this: PHP Notice: Trying to get property of non-object in /home/website/vendor/smarty/smarty/libs/sysplugins/smarty_internal_templatebase.php(157) : eval()'d code on line 42 that's all I see in the log. not a hint as to what or where... maybe we can hire you @Traumflug to do some debugging on our site? How would we go about this?
  4. Yes, I see where you are coming from - however this is almost never a real life scenario. No one runs an out-of-the box install. We just want to disable php notices from being logged. That's all. Any idea how this can be achieved?
  5. Hi, in the past we where able to disable PHP notices in defines.inc but it seems this has changed now. I found ErrorHandler.php in classes and changed line 77 from @error_reporting(E_ALL | E_STRICT); to @error_reporting(E_ALL | E_STRICT & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT & ~E_WARNING); But this has no influence. All notices still get logged. How do I disable this in latest TB? Thanks
  6. We got contacted by a security firm about 2 potential vulnerabilities in the core of TB. To whom do I report this as I don't want to post details in a public forum?
  7. as reported here: https://github.com/thirtybees/thirtybees/issues/1016 we now had to revert back to 1.0.8 (which was easy thanks to the new core updater) If you have a multistore environment, there's some rather serious issues still and we will have to wait until they are fixed. all reported in git, just wanted to make aware of this in the forum as well. Guest checkout issue: https://github.com/thirtybees/thirtybees/issues/1015 Password masking issue: https://github.com/thirtybees/thirtybees/issues/1014 I hope these can be resolved quickly, so that we can finally update to 1.1.0 Thanks
  8. sorry just double checking: you did clear your TB cache, right?
  9. so what's the error you see when you switch on error reporting?
  10. sure thing, here you go. don't forget to clear cache 🙂 order-carrier.tpl
  11. yes, working fine with warehouse theme, however you need to alter the file order-carrier.tpl around line 82 from {if $option.unique_carrier} {foreach $option.carrier_list as $carrier} <strong>{$carrier.instance->name|escape:'htmlall':'UTF-8'}</strong> {/foreach} {if isset($carrier.instance->delay[$cookie->id_lang])} <br />{l s='Delivery time:'}&nbsp;{$carrier.instance->delay[$cookie->id_lang]|escape:'htmlall':'UTF-8'} {/if} {/if} to {if $option.unique_carrier} {foreach $option.carrier_list as $carrier} <strong>{$carrier.instance->name|escape:'htmlall':'UTF-8'}</strong> {if isset($carrier.instance->delay[$cookie->id_lang])} <br />{l s='Delivery time:'}&nbsp;{$carrier.instance->delay[$cookie->id_lang]|escape:'htmlall':'UTF-8'} {/if} {/foreach} {/if} If you are using the OPC checkout process. Otherwise you face the error 500 (this might be the same problem in the Panda theme...)
  12. Despite some people ranting about KnowBand, I personally found their support to be outstanding and yes they always fixed issues for us in a timely manner and even did some customisation for free. Agree we should get them onboard as their modules are really good (mostly...). Most of their modules work out of the box with TB anyway.
  13. ok, I replaced your attached file but the error remains the same. cleared cache and all of course.... We are using a different version of that file, but I found the foreach loop and replaced your code, but it's still giving us the same error. So we can't update to 1.1 unfortunately (I know it's a bug in the module, so will have to wait until knowband provides a fix)
  14. @datakick This is probably related to new version of smarty. Similar problem was in community theme / niara, and it was fixed by simply moving the block of code to the proper place. If you send me the module, I can fix it for you @datakick Can you possibly post the fix for the supercheckout module here as we are having the same issue? I think there are still many people who use this module and if TB 1.1. breaks the checkout module like this we are having a bit of an issue I guess...
×
×
  • Create New...