musicmaster
-
Posts
675 -
Joined
-
Last visited
-
Days Won
43
Content Type
Profiles
Forums
Gallery
Downloads
Articles
Store
Blogs
Posts posted by musicmaster
-
-
1 hour ago, SLiCK_303 said:
update my mails, modify like 3 theme files, add a theme file, and update a few of my overrides
Sounds like quite a lot.
Could you share some of those solutions so that other people can solve them without having to ask?
-
1 hour ago, SLiCK_303 said:
update my mails, modify like 3 theme files, add a theme file, and update a few of my overrides
Sounds like quite a lot.
Could you share some of those solutions so that other people can solve them without having to ask?
-
Such a big order makes it almost impossible to find a cause. You need an order with one or two products - maybe in high quantities. Only in such a situation makes it sense to do the calculations manually and look where things go wrong.
BTW: existing orders will not change due to your change in settings. Only new ones will.
-
42 minutes ago, datakick said:
There are no 'known' problems with core updater. All reported problems were fixed and new versions were released. You can download the latest version here.
Can you use downloaded versions for upgrade? How?
-
On the Modules page click on Check for updates. After that you will see the modules that can be upgraded and a button to do so.
-
On 10/20/2021 at 7:39 AM, datakick said:
If this prefix changing is not the right approach for you, for some reason, you will have to copy every table independedly. Use sql like this for every table (ps_product is source, tb_product is target)
truncate tb_product; insert into tb_product select * from ps_product;
If the columns or their position are different, you will have to enumerate all fields as well:
insert into tb_product(id_product, id_supplier, id_manufacturer,.....) select id_product, id_supplier, id_manufacturer,..... from ps_product;
Very tedious task
If you need to do that kind of things you can better use my tool Copy_shopdata. It handles such problems for you.
But in this case it is very likely not needed.
-
1
-
-
The issue I run most often into is the inability to attach files with the customer service messages.
Probably I am biased because I sell software. But I can imagine that other people will find it handy too for sending manuals, product previews, etc.
-
1
-
-
What is the work queue? And to what extent will it be something programmers need to take into account when they develop something for TB?
-
1 hour ago, datakick said:
Of course I can ask them to look into database 🙂 But fortunately I won't have to
The disadvantage is that only you will be capable of determining which revision is older and which is the latest. For almost everyone else it will be just too much effort.
-
8 minutes ago, datakick said:
Your server probably do not have updated trust stores / root certificates. You need to update your server packages. How to do that depends on your distribution. Some hints can be found for example here:
Is this really necessary? I never before heard of a software package refusing installation because an expired certificate - a quite common problem.
-
14 minutes ago, datakick said:
Why?
For people that will use Stable releases this is not an issue. The revisions will always match official release tags, such as 1.3.0 or 1.2.0.
If you are using bleeding edge, then you will see current exact git commit. This information for machines, not for humans. Revision is precise and it nicely correlates with information on github.
I understand that from human point of view, it's nicer to see 1.4.134 instead of d601a7dfa69025341ea598f558885b6cbbd7b7b4. However, nobody would be able to figure out what exactly is part of version 1.4.134, or what are the differences between 1.3.0 and 1.4.134, simply because 1.4.134 would not tracked in repository.
With revisions, we can look at github and see it all.
What is part of this version? https://github.com/thirtybees/thirtybees/tree/d601a7dfa69025341ea598f558885b6cbbd7b7b4
What are the differences between 1.3.0 and current bleeding edge? https://github.com/thirtybees/thirtybees/compare/1.3.0...d601a7dfa69025341ea598f558885b6cbbd7b7b4
Experience learns that even minor revisions can bring errors. So when someone reports an error it is always good to know exactly what version he used. You cannot ask someone to have a look in his database for what _TB_REVISION_ he has.
-
24 minutes ago, datakick said:
I believe you were on some bleeding edge version before?
If that's the case, then rest assured -- this is the one-time issue only. Next update will not be affected.
When updating to bleeding edge we didn't actually saved exact git revision that was being used. In your store the only available information was that this is some variant of 1.2.0. Not very useful.
During update, core updater asked server for a fingerprints of files for version '1.2.0', and checks it agains files on your server. Of course, every files that were modified between 1.2.0 and the bleeding edge version you have on your store will have different fingerprint, and so they will be considered modified.
The new core updater fixes this issue -- we now define new constant _TB_REVISION_ that points to exact git revision or tag. During update, core updater will ask for fingerprints of files for this exact revision.
Isn't it possible to use normal subversions instead of revisions? Like 1.03.01 and 1.03.02?
-
One little other thing: the modified files. It seems to me extremely unlikely I changed all these files. Maybe one or two, but my impression is that most were changed in some system operation.
-
Updating indeed allowed it to go further. Thank you.
The database software is MariaDB 10.4.8
-
1
-
-
4 hours ago, datakick said:
definitely not 3 gigs, maybe 3 megs. But you are correct, we log too much. I've released new version of core updater with optimised logging.
Looks like the the API request didn't finish for some reason. This is server-server communication, so definitely not browser issue. Maybe you have some sort of antivirus / security software installed on your server?
When you asked for feedback about the Core Updater I reported too that it remained stuck at 42.86%. There was never a report that that was solved. I just checked for the log files from those tests: 4.3 and 8.9 GB. So Slick_303 is right.
By doing a new "upgrade" that I broke off almost immediately after it got stuck at 42.86 I managed to get a shorter log file. I have it attached
-
41 minutes ago, Pietroalberto said:
i don't have full access on whm and i don't see the transfer tool ,.
Is it easier to do a new installation and update afterwards or is it better to transfer the database? (and how do you transfer the database correctly ??)For a database export and import should work ok. Don't forget to cleanup the database before you start.
-
4 hours ago, Darren said:
thanks for the suggestion, will take a look at both, the wizard one certainly not cheap, amazing how much more PS modules are compared to woocommercce etc, but, my site just wont work without a module like this and spent so much time getting it ready now in PS it would be soul destroying to back track lol.
I am not sure whether AWP supports your second scenario. I doubt it. So you should ask them.
3 hours ago, led24ee said:Also stock keeping is very stupid. You can see overall quantity, but when You need to see how many each item you have, you must look separately.
You can do that on the Prodcombi page of Prestools.
-
You can use Prestools for managing the price of large numbers of combinations. It allows you to set prices on attributes. It is free
However, the database structure can only handle a few thousand combinations. Otherwise it becomes too slow. The alternative is the module Attribute Wizard Pro but that is far from free.
-
2 hours ago, datakick said:
Did the ajax request failed, or just took a long time to process?
I had it once again running and got this.
I am afraid it is not a good idea to have so many ajax calls (the counter is here at 1684). On Windows computers they attract anti-virus checks and as a consequence they are slow.
-
It looked like CHECKING YOUR INSTALLATION stayed forever at 42.86%. I did it on a bleeding edge webshop that probably already was up-to-date.
-
Is it really necessary to declare this kind of stuff as "critical"?
It seems to me that that word should be reserved to things that are likely to cause errors in your shop.
I also found the buttons at the top right hard to find.
-
I made something similar here: https://www.topsnoep.nl/relatiegeschenken/2863-notenmand-zelf-samengesteld.html
In it you select a basket and one or more products to insert into it. It uses customizations and involves about a hundred lines of code.
-
Just a little trick:
The problem is well known. Searching for more than one word gives all products that contain at least one of the words. It is rather easy to change that. You need to change just a few lines in classes/Search.php
On line 232 of Search.php you will find:
$eligibleProducts2 = []; foreach ($intersectArray as $query) { foreach ($db->executeS($query, true, false) as $row) { $eligibleProducts2[] = $row['id_product']; } } $eligibleProducts = array_unique(array_intersect($eligibleProducts, array_unique($eligibleProducts2))); if (!count($eligibleProducts)) { return ($ajax ? [] : ['total' => 0, 'result' => []]); }You should change that to
$eligibleProducts2 = []; foreach ($intersectArray as $query) { foreach ($db->executeS($query, true, false) as $row) { $eligibleProducts2[] = $row['id_product']; } $eligibleProducts = array_unique(array_intersect($eligibleProducts, array_unique($eligibleProducts2))); $eligibleProducts2 = []; } if (!count($eligibleProducts)) { return ($ajax ? [] : ['total' => 0, 'result' => []]); }This was done in TB 1.02. If you have a different version the line numbers may be slightly different.
-
2
-
-
What about disabling pretty urls / deleting .htaccess?
Without pretty urls you see the real paths of the images. And that means that you can look with FTP on the disk whether they ware there or not.
Upgrade to 1.3.0 not working
in Technical help
Posted
Sorry for posting the same thing twice. The forum has become a bit strange. Suddenly it sorts the posts by vote. But that means somehow that the latest becomes immediately after the original post. It also means that when you reply and press the "submit reply" button that button after some busy time becomes active again while the text you posted is still in the window. Rather confusing...