Acer

Do we really want to find out? Some could be compromised already and they won't know for a while

From what we gathered it seemed that the attackers could somehow override the Smarty cache setting regardless, which means it doesn't matter that we have it on the correct setting. Unless I'm completely mistaken? So what to do here?

While we wait for @datakick What are you guys doing to fix this on your sites? Do you know if it's possible to apply the Prestashop fix to TB in this case? @WBNet-Wout @musicmaster

Any idea when we'll have a patch available for 30Bz, please @datakick?

Now for Panda...

Do we know how well this behaves on Warehouse and Panda themes incl. their bundled modules?

Thanks @datakick for the update. Please keep us posted and let us know when a patch / update has been released.

Ah, perfect, thank you 👍

Cool, thank you. So when you say enable multiple values for individual features I assume there's no switch or toggle for that? And that it happens automatically?

Hi @datakick I also created this post So just to clarify: there's nothing to activate, it's on by default?

So.... What happened with this? Is it now part of 1.3 and activated by default?

Hi guys A while back I noticed there was talk of 'Multiple Values for a Feature' functionality (or lol, feature) finally being part of native ThirtyBees in the new version. I'm at this part of my project now and I'm still running an older version of TB and now I wonder if I should update to the latest? And how do I enable this feature? Or if I should rather still use 3rd modules to give my store this functionality? I appreciate the response. Thanks @datakick

Hi It's been a while... Do you have an updated link / is the Slack channel still active? And for that matter, is TB still active? @Smile @datakick

Ok cool, thank you 👍

Sweet, that's good to hear, thank you. So you're running the official 1.2 release and not 1.3 Edge? Also I don't suppose you're running Advanced Search 4?

Thanks @toplakd However, as far as I recall you keep your site as bare-bones as possible, with the absolute minimum amount of 3rd party modules - and you don't run Panda... I'm curious if anyone with Panda has had issues with 1.2. Also should I go with bleeding edge 1.3 - i.e. were there any significant bugs in 1.2 that were fixed in 1.3 or is 1.2 nice and stable with 0 issues? And can I run 1.1.x on PHP 7.4? @datakick - your 2 cents as well pls?

Hi We've just been told by our host that they are forcing PHP 7.4... Is it safe to update to TB 1.2 if you're running Panda? Or can TB 1.1.x run on PHP 7.4 without any problems (apart from warning notices in the log)? We're currently running on PHP 7.3. Also I'm curious if anyone here has updated a production / Live site to TB 1.2 yet and if they've run into any issues?

Thanks for this. Seems like this dispatcher override is being used... On a Local version of the site, after trying a few things (and bombing the site), I eventually restored the Modules folder from an old (recent enough) backup. An lo and behold, it could save custom values for a feature again 😕 Wtf... Unfortunately I can't try this shit on Live though as it's technically a different branch and its backups have this bug. Probably going to be one of those weird unsolved mysteries... Not ideal... However, does this not assist in giving a clue perhaps: ? I've checked the logs and it appears to be filling up with this error when I try to add a custom product feature value: [Tue Dec 01 12:47:23.753602 2020] [php7:warn] [pid 18120:tid 1916] [client ::1:52514] PHP Warning: preg_match(): Compilation failed: invalid range in character class at offset 55 in C:\\xamppnew\\htdocs\\development\\testsite\\classes\\Dispatcher.php on line 936, referer: http://localhost/development/testsite/admin3419jgisg/index.php?controller=AdminProducts&id_product=119&updateproduct&conf=4&key_tab=Features&token=ddb9b6bb5c007d48060cae23004fd3ec This is line 936 in my Dispatcher.php if (preg_match($route['regexp'], $uri, $m)) { Either way, I appreciate the assistance @yaniv14

Anyone? Any ideas?

I've checked the logs and it appears to be filling up with this error when I try to add a custom product feature value: [Tue Dec 01 12:47:23.753602 2020] [php7:warn] [pid 18120:tid 1916] [client ::1:52514] PHP Warning: preg_match(): Compilation failed: invalid range in character class at offset 55 in C:\\xamppnew\\htdocs\\development\\testsite\\classes\\Dispatcher.php on line 936, referer: http://localhost/development/testsite/admin3419jgisg/index.php?controller=AdminProducts&id_product=119&updateproduct&conf=4&key_tab=Features&token=ddb9b6bb5c007d48060cae23004fd3ec This is line 936 in my Dispatcher.php if (preg_match($route['regexp'], $uri, $m)) { This is the code I have in the Override/classes/Dispatcher.php file <?php class Dispatcher extends DispatcherCore { /* * module: sturls * date: 2020-07-09 07:23:13 * version: 1.0.0 */ protected function __construct() { if (Module::isEnabled('sturls')) { $module_inst = Module::getInstanceByName('sturls'); $this->default_routes = array_merge($module_inst->hookModuleRoutes([]), $this->default_routes); } parent::__construct(); } /* * module: sturls * date: 2020-07-09 07:23:13 * version: 1.0.0 */ protected function loadRoutes($id_shop = null) { if ($id_shop === null) { $id_shop = (int)Context::getContext()->shop->id; } parent::loadRoutes($id_shop); if (Module::isEnabled('sturls')) { $module = Module::getInstanceByName('sturls'); $language_ids = Language::getIDs(true, $id_shop); foreach($language_ids as $id_lang) { foreach($module->lang_field as $k => $v) { $route_lang = Configuration::get($module->_prefix_st.strtoupper($k), $id_lang); if ($v != $route_lang) { foreach($this->default_routes as $route_id => $route) { if (strpos($route['rule'], $v.'/') !== false || $route['rule'] == $v) { if ($route['rule'] == $v) { $rule = str_replace($v, $route_lang, $route['rule']); } else { $rule = str_replace($v.'/', $route_lang.'/', $route['rule']); } $this->addRoute( $route_id, $rule, $route['controller'], $id_lang, $route['keywords'], isset($route['params']) ? $route['params'] : array(), $id_shop ); } } } } } } } } Initially I thought that it could be the "multiple values for a feature" module that I'm using, but I've since disabled that and I'm still getting this error... Any ideas?

On a product features tab, enter a customised value: After save, value remains blank, like it did not save:

It's the built-in TB product features one. Calling in the air-support, or Orbital Ion Cannon, if you will... 😉 @datakick @Traumflug

Hi I've encountered a bug where Customised Product Feature Values are not being saved in Admin. Presaved features work, but it's impractical to create a value every single time first. This occurs on three of my sites, one on TB edge and the other two on 1.1.0. Using different browsers doesn't appear to be making a difference. Has anyone encountered this one before and is there maybe a code fix I can implement?

Ok all sorted now. So this appears to have been a configuration issue on the Site's server in relation to Office 365. Not a ThirtyBees problem. Even though the mail configuration was technically correct, we had to add an additional syntax to the SFP record. As the server is sending the mail on behalf of an email address on Office 365, we had to tell Office that it could trust the server. Bizarre thing is that technically all mails should've landed up in Office 365's Spam or Quarantine box. That didn't happen. Most mails were sent / received successfully. Just some mails went missing when some users did tests and these mails were nowhere to be found. No Spam, nothing in Office 365 error log, etc. Even though all mails were sent from the Shop's email address on the site... Yeah WTF. Always fun running into "magical" IT problems - the ones that are random, only breaks when it wants to, defies logic and understanding, difficult to troubleshoot and hard to explain. Magic. If anyone ever experiences this, this is what we had to add on the DNS/Zone SPF TXT record for the Site's server (added in red): v=spf1 include:spf.protection.outlook.com include:spf.host-h.net -all

Thanks Traum. But nothing in the mail logs. Some of the mails from these users are coming through though. I'd understand if they were all blocked... The thing is that is that as far as I understand it is the actual site email address that's sending these mails and not the user? As some of these forms are in a Lightbox (pulling in the Contact form) and it's using Ajax, could it be Ajax that's causing this? I used Nemo's old tutorial on how to do this. http://nemops.com/prestashop-ajax-contact-form/#.XYN8VSgzaUl But instead of creating the lightbox with 'ajax', I set it to iframe (to increase performance) - could it be this? All mails from the actual Contact form page appears to be working fine though. And for me and others the Lightboxes are always sending... This is the code I use to create the form in the Lightbox: $.fancybox({ type: 'iframe', preload: true, href: getcontactformurl, closeEffect: 'fade', autoDimensions: false, autoSize: false, width: '400px', height: 'auto', async: true,