Acer

Ok cool, will implement, thank you.

Perhaps you're right. However, I couldn't find the entry in question ('page') using phpMyAdmin (it's not in tb_meta). So before I just added a new entry to the table, I refreshed - and all was good. Or so it seemed. So should I add an entry to tb_meta table for 'page' or is it in another table somewhere? (I'm on 30Bz 1.1.0)

Bytw: in my case (also a Panda issue), I did not have to implement the MySQL update. Just thought I'd let you know. Just implemented the changes to Meta.php and problem went away. Thank you

Hi Movieseals Thanks for the feedback here. I've given it a shot and all appears to be working (the headers are reporting Litespeed as they should) + really fast page loads 😄 Thanks again

Anyone here with the solution? Not sure if this one is still being monitored or if I should make a new post?

Pedalman, please update the link (I think it's linking to your shop). This is exactly what I was interested in - will check it out, thanks! Any other suggestions guys?

Hi guys I'm trying to install TB 1.1.0 on a new server, but I'm getting this error (Paypal, can't proceed with Next). Installed TB 1.1.0 on two other different hosts, and this is the first time I'm seeing this... Following the instructions to modify ConfigurationTest + Configuration hasn't worked.... Can you please share instructions on how to quickly fix this? As I see there's been a lot of activity on this post - not sure which is the solution / magic bullet? Thanks

Thanks for the reply. Are there any hardening tools available? Like Akeeba admin tools - Joomla, Sucuri monitor - WordPress etc for TB / PS 1.6?

Please see original post. How do we prevent this, are there hardening tools or techniques available? Also as there will likely be changes to files anyway as part of the course of normal development, as you say as well, the core updater will not be useful here. And checking manually is not practical... Any suggestions, thoughts and ideas re this and 30Bz site security?

Ok interesting. I think it the Business edition. The reason I'm asking is that apparently it only works with "the default theme + warehouse" and I've seen other TB guys ask on the Litespeed forums how to make it work... Are you using Warehouse, or which theme?

Hi So the Magecart thing was one scary thing (for Magento) - now there are reports that there is a Presta 'hack' that bypasses / or fakes the 'flyover' for a third-party payment gateway... Scary. I wonder how the site was infiltrated in the first place? How do we prevent or mitigate this? https://arstechnica.com/information-technology/2019/11/scammers-try-a-new-way-to-steal-online-shoppers-payment-card-data/ Also, are there any 'hardening' or security tools out there for TB / PS 1.6? Ideally free (similar to Akeeba AdminTools for Joomla, etc) Mind sharing any TB hardening techniques? With the festive season coming up + what happened to this PS site and the Magento sites - understandably I'm a bit nervous (I'm sure I'm not the only one). So how do we protect our TB sites from these f**kers?

Hi guys I'm wondering if any of you have had experience with configuring TB + Panda + Litespeed module? If so, mind sharing the modifications you've had to make to make it work please?

Ok cool, no problem 🙂 Thanks again for the patch 👍

Excellent! This is working, thank you 🙂 I assume that this patch is included in 30Bz Bleeding Edge (1.1.x+), hence the reason you didn't encounter it in your initial round of testing?

Any new insight into this?

it looks like this: http://localhost/development/local-dev-sites/new-onlinecopiers/coffee-and-tea/tea/bee-hive/tea

Windows on Xampp PHP 7.2. However, the URL seems to be correct and the other options {tags}, {reference} seem to work just fine...

I've checked this on a fresh install of TB 1.1.0 as well as an upgraded test install from 1.08 to 1.1.0 And I'm still getting this problem.... seems like it has something to do with {manufacturer:/}

This is odd... I'm running TB 1.1.0 and haven't made any other SEO Route changes... If I use {tags} instead of manufacturer - it works. Weird. But as soon as I use {manufacturer:/} it breaks... Even though the manufacturer exists and the path looks correct in the address bar. Eeek...

Weird, I'm still getting 404... (cleared cache, generated new htaccess) Am I missing a step? Is there a 're-index' I need to do somewhere? Have you tried this on your local?

Thanks, I've done this - but no change... (New htaccess, Cleared TB cache, Browser cache = nadda )

Hi Interesting that this doesn't handle multi-language. I understand your frustration. In my case, the problem was that it wouldn't update the feature on CSV import, it would keep on adding values to it. Hence the 'solution' above that effectively nukes the product features every time there is an import and replaces the features with the new ones specified in the CSV import. Impact on multi-lang wasn't even a thought... I guess my question to you is: is the reason you were looking at this post because you were using the free module "Advanced Feature values" as above? Because the reason the CSV import would add and not replace feature values is because of the functionality added by this module. If you're not using this module, then the modifications above are not necessary - and could possibly cause unnecessary headaches. Anyway, I know this is an older post, just thought I'd provide some feedback.

Hi I'm trying to add the manufacturer to the Product route, like so: {categories}{/:manufacturer:/}{rewrite} The URL appears to be correct, and the product URL seems to reflect the new URL... But I keep on getting 404... What am I doing wrong here? Your help is appreciated.

Hi guys Just out of curiosity: Any update on incorporating this into TB? And how do we get it into TB? @Traumflug

Ok cool, thanks