the.rampage.rado

I think I remember seeing a module where instead of add to cart functionality the button redirected to external affiliate website. I can't remember. It it was of Woocommerce?! Long story short - I would like to switch on of my websites to aff marketing.

Excallent work @wakabayashi Together with @datakick's work on packs this will bring TB to new heights!

I purchase goods on daily basis from Germany and in none of the websites I purchase there is GDPR compliance or detailed cookie settings or else?

Customer protection is always good thing. I personally hate when 'black friday' promos are -5% off the normal price when you check in price comparison websites but now shows -40%. But as small and medium merchants how much interaction do you have with the regulators in your countries? If you have normal looking shop, you pay your taxes and treat all customers with the needed respect I doubt you had any talks with the regulators regarding your online presence and EU directives. As of now I have none GDPR requests in any of my 3 webshops.

@datakick - can we merge this one as well@ Unrelated but very nice feature that works flawlessly in the time I'm using it. https://github.com/thirtybees/thirtybees/pull/1416 Thanks!

You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')) GROUP BY fv.id_feature, IFNULL(fv.custom, 0)' at line 3 in file controllers/admin/AdminFeaturesController.php at line 745 SELECT id_feature, IFNULL(fv.custom, 0) as is_custom, COUNT(fv.id_feature_value) as count_values FROM `ps_feature_value` fv WHERE (fv.id_feature IN ()) GROUP BY fv.id_feature, IFNULL(fv.custom, 0) $ids = array_map('intval', array_column($this->_list, 'id_feature')); 728: $extra = []; 729: foreach ($ids as $id) { 730: $extra[$id] = [ 731: 'value' => 0, 732: 'custom' => 0, 733: 'products' => 0, 734: ]; 735: } 736: 737: $conn = Db::getInstance(_PS_USE_SQL_SLAVE_); 738: 739: // count feature values 740: $valuesQuery = new DbQuery(); 741: $valuesQuery->select('id_feature, IFNULL(fv.custom, 0) as is_custom, COUNT(fv.id_feature_value) as count_values'); 742: $valuesQuery->from('feature_value', 'fv'); 743: $valuesQuery->where('fv.id_feature IN ('. implode(',', $ids).')'); 744: $valuesQuery->groupBy('fv.id_feature, IFNULL(fv.custom, 0)'); 745: $res = $conn->executeS($valuesQuery); 746: if (is_array($res)) { 747: foreach ($res as $row) { 748: $id = (int)$row['id_feature']; 749: if ($row['is_custom']) { 750: $extra[$id]['custom'] = (int)$row['count_values']; 751: } else { 752: $extra[$id]['value'] = (int)$row['count_values']; 753: } 754: } 755: } What is causing this issue? I'm on almost latest bleeding edge and I have features in other 2 shops with this version. I didn't need them in this one until now. Cheers!

ruzzian war in Ukraine

You can try rolling back to php 5.6 and see if it works. I have this issue on my modded version of the module from Warehouse theme. After you make the changes in backoffice and save turn back php 7.3 or whichever version you use.

This is not WP. Every theme has its own editor.

I don't want to go anywhere near anything with Z in it right now...

Latest Warehouse for PS1.6 works like a charm.

If you switch this setting it messes with .htaccess file. I would suggest to backup it with working settings and then delete it completely. Then set the required settings in BO. If this does not work try clearing all caches - 2 TB caches, manually all your theme cache files and smarty files and if you have some serverside caching enabled it too. Refresh couple of times or try new browser or incognito mode. Some combination of those items should solve your issue 😉

I have only the basic configuration from the module for pages: And here the configuration is as follows:

No complains from clients here. Using the latest PS module with the latest TB on php 7.3 and latest PS1.6 Warehouse. No settings for punches are needed for the theme.

When you change those URLs you have to recreate your htaccess file if you use Pretty URLs function. It's not a bug.

I looked twice and I don't see it. Whatever... If you're selling TB compatible module on TB store at least it would be nice to present it working on TB... (or PS1.6 at least...).... Otherwise the idea is cool, let's see how it's implemented.

In your demo the backoffice is in PS1.7 and there's no such module (not enabled for demo user at least)

With the current dev onboard you can be sure that every commit is tested and he knows the ropes very well. I think in the past 6 months I saw one reverted commit. Feel safe to update to edge when you notice something cool that you want to be fixed in your installation. Bugfix versions will come too.

And for further security make two backups - one from your hosting and one by FTP. Also make 2 backups of your original DB.

There were absolutely no design changes in 1.3 compared to any previous TB version. :) If you had some manual changes to the core files of Niara or other theme or BO then it's up to you to fix them in 1.3.

It will be released but until then you can update to edge. It's tested almost daily.

Why don't you update to 1.3 and see if there's anything that's better? The update is harmless, no new features, no removed onse. Just lots and lots of bugfixes.

Turn debug mode on and tell us what's showing when you experience an error.

Dollibarr is pretty much dead in the water anyways... Try some newer CRP and find the proper connector. I know it's hard and probably that's why you went with dolibarr. EDIT: Dead in the water is little harsh, obviously the project is alive but I believe you should consider other options.

The suggested edit will never solve your issue. It was in connection to your 'in development' installation. To try and solve your issue you should try the following: 1. Clear all caches 2. Update your store to the latest version (1.3) 3. Regenerate your thumbnails (in Images menu) 4. If still no images present in Front End please right click on some missing image and find the complete URL. Copy and paste it in new tab and see if it opens. If it opens please clear your .htaccess file and regenerate it by disabling and then reenabling pretty URLs (in URLs menu section).