datakick

@rubben1985 that's the thing with development, things that seems easy are usually the hardest one to implement :) There are really many areas that needs to be carefully adjusted - review criteria - it's not possible to use criteria for products - review lists - ensure that it's filtered by correct entity type. We don't want to mix different type of reviews together. This applies mainly for customer reviews page / all reviews page - email templates should be different / modified - there's no product title or image for shop review - rich snippets - store reviews needs different metadata than product reviews, otherwise google would be angry - review export needs adjustment - review import - and who knows what else :) But yeah, this feature is really needed, I get asked for this a lot.

@the-rampage-rado: Looking forward to the custom 'stars' feature! I'm a bit reluctant with implementing this feature, because couple more features will not work with it correctly, or will require custom hacks. For example sizing, half-stars, etc... But I'll probably implement it anyway, there are quite a many people what want this. @rubben1985: Do you plan to include store review? It's in the backlog, but it's a huge feature. Also, I probably make it a bit more generic, because there are people who want to review other things as well. For example brands, sellers if they have marketplace, etc... I haven't decided yet, but given the amount of work associated with this feature, I'll probably make it part of a premium module only.

Make sure you have routes defined for all languages.

Version 1.0.20 - support for images I'm happy to announce that new version 1.0.20 has just been released. This version fixes few bugs, and brings one major new feature - support for images. Your customers can now attach images to their reviews: Other changes extracted css classes to allow popup window customization - issue #71 fixed multistore bug in all reviews page - issue #68 check that dom php extension is loaded and more...

@b_otho said in Updating to 1.06 - Error with "Address::isDeleted": I just tried clearing APC cache through the module. Didn’t help. Please open file classes/Address.php and ensure that it contains method isDeleted, it should be somewhere around the line 385. ``` public static function isDeleted($idAddress) { $row = Db::getInstance(PSUSESQLSLAVE)->getRow( (new DbQuery()) ->select('a.deleted') ->from(bqSQL(Address::$definition['table']), 'a') ->where('id_address = '.(int) $idAddress) ); if (!isarray($row) || !isset($row['deleted'])) { return true; } return (bool) $row['deleted']; } ``` If the method is there (as it should, otherwise this file should be mentioned in Changed files list), then the issue really must be with the php cache.

@b_otho said in Updating to 1.06 - Error with "Address::isDeleted": Dyou mean Advanced Parameters > Configuration Information? I cannot see that anything should be wrong. If there are no changed files listed than it should definitely work -- the only other explanation is that the php APC cache wasn't flushed, so it's still uses the original php file.

@b_otho method Address::isDeleted was introduced in 1.0.4. Could you please verify that *all* files have been updated correctly - Simply open Configuration Information to see if there's any changed file. It is possible that updater could not update Address.php file, for example because of wrong owner or file permissions.

@b_otho the sql issue is already fixed in newer version. You can either update, or apply this fix manually

Work on this project has been temporarily suspended, I plan to return to it later this week.

@doclucas the sheet is no longer accessible, could you please fix the sharing permissions:

It is very strange that it happened only occasionally. The message from error log is still needed to figure out what went wrong, though. Could you please look into your server's error log and copy the error message here.

Couple of times... meaning not always?

You'll need to look into your server's error.log to see where the problem is. Then we can help

do you really need unique attribute group for every product? I guess all that's necessary is some small javascript code to filter out colors that are not used by any combination

thanks @Briljander. But I'm not helping all the time, just during coffee breaks :)

The git repository is not always a valid module. Quite often some build script is required to compile module zip file from source code

@exuraz I can't see column is_root_category in the screenshot. Please ensure that it has 1 for your Home category (id 2). If not, fix it.

@Purity it's probably the shared hosting thing. There is a really huge amount of work that updater needs to perform, and it takes considerate amount of server's resources to do so. Updater tries to be smart about it, and splits the work into series of small work items / chunks. The size of work item is determined by the Server performance settings option: But in the end, your server is expected to complete every chunk atomically - in one request. That means, for example, that your server must be powerful enough to to add 400 files to the backup zip file within once request. Shared hostings can employ multiple measures to ensure that one site will not consume all the server's resource. It can calculate how much CPU/Disk IO your site used within the last few minutes, and it can start throttling resource allocation to your site if you exceeded some limit. That can include decreasing of max-execution time, lower priority for IO operation, lower priority for PHP process, etc... This resource throttling is only fair --- your hosting provider have to ensure that other sites hosted on the same server won't be affected by your actions. But it can mean that long-running tasks like updates / data import / export / image regeneration / cache indexing / ... can fail. This is definitely a red flag, and you should consider different hosting solution.

@hfxracing you should see it in your back office. If not, you can download it here

@Purity that seems to be a bug, I'll investigate. It's definitely safer to turn off the cache before performing update.

@Troy-Roberts Error code 503:Service Unavailable can be returned by your server / proxy when it's under heavy load. The ajax request to upgrade database probably never made it through to the php layer. Most likely, sql migrates were not processed at all. What version did you migrate from? There weren't any sql migrates since 1.0.4, so if you have migrated from 1.0.4 or newer, it's safe to ignore this.

I'm happy to announce that the tbupdater module has been fixed, and can be used to update your thirtybees store to the latest version 1.0.6. There's no need for manual update anymore. To update your store, you will first need to update thirty bees updater module to the 1.3.2 version: Then you can open the module's configuration page, and migrate to the latest thirtybees version:

@hfxracing I don't thing you have. For example the image on your homepage should comes with 3 sizes: https://www.hfxracing.com/img/p/1/1/1/3/1113-homedefault.jpg https://www.hfxracing.com/img/p/1/1/1/3/1113-homedefaultsmaller.jpg https://www.hfxracing.com/img/p/1/1/1/3/1113-homedefault_smallest.jpg but only one home_default variant exists on your server. Maybe you have misconfigured images

That's because Uint8Array is not supported on ie and edge yet (and also es6 arrow function which is not supported on ie). This function purpose is to generate pseudo-random uuid v4. It's safe to switch to another implementation: ``` function uuidv4() { var uuid = "", i, random; for (i = 0; i < 32; i++) { random = Math.random() * 16 | 0; if (i == 8 || i == 12 || i == 16 || i == 20) { uuid += "-" } uuid += (i == 12 ? 4 : (i == 16 ? (random & 3 | 8) : random)).toString(16); } return uuid; } ``` I've filed issue https://github.com/thirtybees/thirtybees/issues/584

@hfxracing product images? Have you tried to re-generate images?