datakick

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?

I advice you create a module and put your overrides into the module. They will be installed when you install that module. Creating overrides manually might prevent thirtybees from installing modules that overrides the same file. Note that you won't be able to install any module that overrides the same function, that's just the fundamental limitations of this technology

Not significantly, as the only overhead is for php server to load more files.

can someone verify that this fix for full-page cache works: edit file classes/cache/CacheFs.php and change line 57 from $this->keys = json_decode(file_get_contents($keysFilename)); to $this->keys = json_decode(file_get_contents($keysFilename), true);

Thanks @dosbiner for your input. I plan to add few alternate flows to choose from, including one minimalistic/all in one form for logged in customers. But that's in the future, right now I need to finish these first 3 flows and iron out bugs.

Thanks for the info. Updates like this can really boost morale

I guess the error_log path is incorrect. You definitely do not have rights to write to server's root directory. It should look like this: /homepages/31/d658016058/htdocs/php-errors.log, or subdirectory with write access

you need to enable php error logs to figure out where the problem is

it's log for php server itself, so it's not anywhere in your tb. The location can vary. If you have some cPanel there's usually a way to access error/access logs through there.

what does the server's error log say?

You could also try to delete class_index.php file in cache directory. Many times the stale class cache is the root cause of such issues

Here's some info regarding shipping cost not changing when selecting carrier thirtybees version 1.0.3 my module did not work with this version, because it assumed that delivery option is serialized using json_encode. But this is true only for versions tb1.0.4 and newer. I've just released new version of chex module that fixes this assumption thirtybees version 1.0.4 and 1.0.5 my module does not work with these versions correctly. It's because of the bugs that were introduced into the core with changing serialization method :) If you have one of these versions, I strongly suggest you update to just released 1.0.6. These issues are affecting even normal checkout page, see here. If you don't want to upgrade yet, then at least you should apply these patches manually thirtybees version 1.0.6 I've installed this new version and tested the chex module. I can confirm it works smoothly tl;dr this module should work with all versions except 1.0.4 and 1.0.5