Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

datakick

Administrators
  • Content Count

    1,571
  • Joined

  • Last visited

  • Days Won

    151

datakick last won the day on July 9

datakick had the most liked content!

Community Reputation

1,134 Excellent

About datakick

Information

Recent Profile Visitors

3,835 profile views
  1. New versions 1.2.2 (free) and 2.2.2 (premium) has just been released: fixed PHP 7.4 deprecation warnings fixed database tables charset -- it's not possible to use smileys in review content fixed microdata in js code -- rich metadata were emitted only in .tpl templates. Now they are also in DOM nodes created by javascript
  2. Core does not include any fonts Niara includes only Raleway font. To get rid of it, remove this line from header.tpl Modules can include their own fonts as well
  3. I'm sorry, I don't really understand. How what could happen? Does email sent from your store contains link with action=efivfj instead of action=review? If that's the case, then there needs to be some module / override / modification that modifies this during mail send.
  4. Do you have Data Mining for Statistics module installed, and enabled? Thirtybees core does no collect these information by default, it's the responsibility of this module
  5. action=efivfj in the url is definitely not correct.
  6. I don't agree. Cloudflare does not cache dynamic content (php, tpl output), it only caches static content (images, js, css, fonts). That means you only need to clear cloudflare cache when you edit js/css files. And if you enable CCC, you don't need to worry about this as well.
  7. Unfortunately that's not true. For example, there is always recalculation of $newShippingCostTaxExcl = (float) $amountTaxIncl/(1+($newCarrier->getTaxesRate($deliveryAddress)/100)); which means that current tax rate will be used to figure out shipping cost tax excl
  8. I did look at your commits briefly, and I have some questions / comments: even when Recalculate shipping is false, there is some recalculation performed. For example, newShippingCostTaxExcl will be updated according to current carrier settings tax settings. That shouldn't happen -- in fact, I would not call the new updateShipping at all in this situation when shipping is modified, then existing invoice would be updated. At least in my country this is very serious issue -- invoices send to customers must be immutable, and all changes should be done by new (corrective) invoice only There is an issue with carrier selection -- if carrier was modified since the order was created, it will have different id_carrier (but the same id_reference). The original id_carrier will not be part of rendered carrier list, and therefore will not be pre-selected
  9. That would be a question for developer of said module
  10. Thanks @wakabayashi for this initiative. It will have to be thoroughly tested before it is integrated to the core, obviously. But hopefully there won't be any showstoppers. One thing that would be nice to implement together with this functionality would be an audit log, so merchants could see why, when, and by whom was the order modified
  11. Then update to 1.1.x -- bleeding edge. It's possible your issue is already fixed.
  12. What version are you running on? What theme? This can be both core and theme related.
×
×
  • Create New...