datakick
-
Posts
3,116 -
Joined
-
Last visited
-
Days Won
485
Content Type
Profiles
Forums
Gallery
Downloads
Articles
Store
Blogs
Posts posted by datakick
-
-
LOL. How dare you use server resources you have paid for.
Change hosting provider.
-
1 hour ago, 30knees said:
I think the above is really important.
Can you describe a use case for this?
1 hour ago, 30knees said:Is there any way to block a cart rule from being applied to bulk discount product price rules?
I don't think this is possible right now. We would have to extend Cart Rules and add new type of restriction.
This is not related to loyalty points at all.
-
I've just pushed this to bleeding edge.
Your body tag will now have class depending on selected context, for example mulstistore-context-all, multistore-context-group-1 or multistore-context-shop-2
You can add custom css into <admin_dir>/themes/default/css/overrides.css
body.multistore-context-shop-3 .bootstrap #header_infos { background-color: lightgreen; }
-
1
-
1
-
-
That makes sense. Thanks for investigating, I've pushed the fix to bleeding edge.
-
1
-
1
-
-
{if !$priceDisplay}{convertPrice price=$product.price}{else}{convertPrice price=$product.price_tax_exc}{/if}
replace with simple
{$product.price}
On a related note -- I strongly recommend to remove all rich snippets markup metadata from this file.
Imagine you have product page that shows 9 related products in the footer. When google parses this page, it sees that this page contains information about 10 products. Which is not true - the page contains one product, and 9 links to related products.
Similarly, when google index your category page, it sees that this is page that contains 12 products. Again, that's not true. It is category listing page with links to 12 products.
Having product metadata in product miniature blocks creates unnecessary noise which can confuse search engines. Just get rid of them, and google will be able to better index your pages.
-
I don't have this issue. Do you have some reprosteps?
-
"Image Position" is considered only if you don't use "Image URLs (x,y,z...)" Field.
Your csv mapping can contain either "Image URLs (x,y,z...)" field - then these images will be downloaded and used.
Or your mapping can contain "Image Position" / "Choose among product images by position (1,2,3...)" -- in which case combination will be assigned existing product images.
-
Yes, data import is not per store, but for all stores.
-
10 hours ago, AndyC said:
I want to pay as I have some modules that may cause issues . I failed to upgrade myself so would prefer someone else to do it... I can ask on People per hour but would prefer it to be done my 1 of the team here
Hi Andy,
you can buy support time on our website. We will be happy to help upgrade your store. Are you talking about core update only, or do you need update of PHP as well?
-
Looks like PHP8 issue.
Try to edit file /classes/stock/Warehouse.php line 665, and change
$res = call_user_func_array('array_intersect', $list);
to
$res = call_user_func_array('array_intersect', array_values($list));
Let me know if that helped -- if so, I will add this to bleeding edge.
-
35 minutes ago, 30knees said:
Thanks both, UTM tags are fine, I just don't want to use a Google tracking pixel.
Do I need to use Matomo to track the UTM tags or can they be tracked with any of the thirtybees stats tools? I probably don't need the full capabilities of Matomo.
build-in stats in thirty bees does not process UTM tags. Those stats are based on webserver requests only, very low level.
If you want to track conversion, funnels, etc, then you really need to use tool like matomo or ganalytics.
-
1
-
-
you can use Matomo (piwik), its self hosted ganalytics alternative. There is native tb module for it.
-
26 minutes ago, the.rampage.rado said:
Will this speed up the last step in the order?
yes
-
Hi everyone,
I've releaesd new module MailQueue. This module uses latest thirty bees Mail Transport functionality, so currently it can be used in bleeding edge / 1.5.0 only.
Link to the module: https://store.getdatakick.com/en/modules/mail-queue
As the module name suggest, the main functionality of this module is to defer sending emails. Instead of trying to deliver email as part of business process, module will serialize and save it to storage (filesystem, redis, db). Cron or CLI queue processor (that runs in separate thread) will pick these queued emails and attempt delivery later.
You can create multiple outgoing queues, and create conditions to determine which emails should go to which queue. For example, queue for 'contact' form messages. Queue for shop admin recipients. Queue for emails that contains words 'binance' or 'viagra'. Queue for transaction emails, queue for marketing emails,...
Each queue can have different settings, of course (it wouldn't make it much sense otherwise)
- throttling -- how many emails can be sent per hour
- delay -- initial delay to send email
- failed delivery retry settings
- manual approval, etc
- retention policy -- how long do you want to keep email in the queue / after send
- sending channel -- every queue can be send using different email transport. You can send transaction and marketing emails through differnt SMTP servers
Some benefits of this system
- original process is not blocked by email sending. Slow SMTP servers can block order creation process even for a few seconds.
- process is not interrupted by SMTP errors - if SMTP server was down, exception could be raised, and this could block process to be finalized (order not completed)
- this supports sending a large amount of emails easily -- enqueueing emails is fast, so you can generate a lot of emails during one request - useful for sending marketing emails to a lot of recipients
- retry option - cron/cli can retry deliver email later if SMTP error occurs
- you can view email content before it is sent, and even after it was sent (depending on queue retention policy)
- delaying some emails (for example you can delay review request email by 3 days)
- pause queue in case of some attack
- email priority
- different sending channels
I'm currently looking for volunteers that would like to test this module, before I release it officially.
And of course, if you have some ideas or questions, let me know. I'd love to hear them all.
-
Review request link looks like this
https://domain.com/en/module/revws/EmailAction?id=<ID>&action=<ACTION>&product-id=2&rating=5&secret=<SECRET>
When the link is generated and send by email, parameter <SECRET> is calculated as md5("<ID><ACTION><SALT>")
where <SALT> is secret key stored in database, not visible to customer,
When customer click on email, EmailAction controller once again calculates the secret using <ID>, <ACTION>, and then matches it with provided <SECRET> parameter.
If the calculated hash value is different, link is rejected, and permission denied is thrown.
This can happen only if one of the following is true:
- parameter <ID> in url has been changed
- parameter <ACTION> in url has been changed
- parameter <SECRET> in url has been changed
- secret <SALT> was changed (in the database -- for example by resetting module)
-
I believe this is causes by some module. There are only a few places in the core that call this function, and none of them is in the product controller area.
Anyway, a lot of modules (for example modules to synchronize data or that generate feeds) uses on this function, because default 30seconds might not be enough.
If your hosting provider can't disable this, I would consider changing server.
-
This controller is available only after you enable Multistore feature in Preferences > General
-
1
-
-
6 minutes ago, Beeta said:
Is it normal that the password in the smtp password field of the module configuration is visible?
That will be fixed in next version of module
-
I'll look into it. I will probably not add an option to modify the address, but I could add link to admin address page where they can modify it.
This also bring out the (generic thirtybees) question what impact has modifying address on existing orders. I think that when we modify address, invoices for old orders will reflect that. And there may be some weird issues when you add/remove vat number...
-
1
-
-
That's server configuration issue - maybe php8 does not have pdo_mysql driver enabled.
Contact your hosting provider again.
-
You can create module that implements actionGetNotificationType hook. As an example implementation, I can refer you to productcomments notifications:
https://github.com/thirtybees/productcomments/commit/ad70c1b0505bbeac8fc57ccb588fbdd8a4962191
-
2 hours ago, Baldyman said:
I'm guessing reverting from Merchant's to regular Thirty Bees isn't a straight forward affair.
It shouldn't be a problem.
You just need to
- uninstall ME core updater
- install latest TB core updater from here: https://github.com/thirtybees/coreupdater/releases/tag/1.6.5
- edit /config/settings.inc.php and change _TB_VERSION_ constant from 1.9.2 to 1.1.0
Now, core updater will think your installation is modified thirty bees 1.1.0, and will raise a lot of warnings about modifications. You can ignore these warnings if you didn't made any modifications, and update to latest thirty bees.
-
1
-
Probably some javascript error. Look into your browser console
-
I don't think that there is any new code that broke this functionality, but of course I might be wrong.
When customer is not logged in, there is no specific address thirty bees can use to calculate shipping costs. If that happens, thirty bees will try to calculate shipping costs for currently selected country. In most cases, this is shop default country, set in Localization > Localization. But it can be different, for example if you use some geolocation module, which can resolve customer country (and language)
First of all, check Localization > Localization > Default Country
Don't forget to delete cookies during testing!
a lot of php encryption and blowfish encryption warnings
in Bug Reports
Posted
Yes, that is the problem.
You have (for some reason) set your store to use PHP Encryption, but no encryption key is generated. No idea how this happened.
Because no encryption key exists, thirty bees will raise the first warning: "PHP Encryption can't be used because _PHP_ENCRYPTION_KEY_ constant is not defined."
And fallback to Blowfish encryption. Blowfish encryption is deprecated, and raises the second warning.
The fix is very simple.
That's it. When you change encryption from Blowfish to PHP Encryption, system will generate new encryption key if none exists.