Jump to content
thirty bees forum

datakick

Administrators
  • Posts

    2,896
  • Joined

  • Last visited

  • Days Won

    434

Everything posted by datakick

  1. The fact that the module does not work is a pretty red flag. There is something fishy there. If I were you I would try to figure out what it was, otherwise it will come back to haunt you later.
  2. No, it works for all orders. If it does not work for you, then there is probably some permissions issue
  3. If you want to send brand new email, then follow these steps: ftp to your site go to mails directory in your theme/language, for example /themes/niara/mails/en create <email_name>.txt and <email_name>.html files (or copy existing email templates and save them under new name) edit email templates, and insert appropriate {placeholder} into it -- these will be replaced with the actual data go to consequences module, and you will see this new email template available for use. If you select it, you will need to map all {placeholders} from the template
  4. You can also use my Consequences module to achieve this
  5. You have Indian language enabled in your store, don't you? The stats module contains a bug that only reproduce for this language, because its iso code is 'in'... and that is reserved sql keyword.
  6. Advanced parameters > Performance > Debug mode
  7. Is the rule marked as executed recently, or does it say it was never executed? If it was never executed, try to remove/adjust your condition, and test again
  8. This is indeed bug in product.js file, function updateDiscountTable. Change it from: function updateDiscountTable(newPrice) { $('#quantityDiscount').find('tbody tr').each(function() { var type = $(this).data('discount-type'); var discount = $(this).data('discount'); var quantity = $(this).data('discount-quantity'); var discountedPrice; var discountUpTo; if (type == 'percentage') { discountedPrice = newPrice * (1 - discount / 100); discountUpTo = newPrice * (discount / 100) * quantity; } else if (type == 'amount') { discountedPrice = newPrice - discount; discountUpTo = discount * quantity; } if (displayDiscountPrice != 0 && discountedPrice != 0) { $(this).attr('data-real-discount-value', formatCurrency(discountedPrice * currencyRate, currencyFormat, currencySign, currencyBlank)); $(this).children('td').eq(1).text(formatCurrency(discountedPrice * currencyRate, currencyFormat, currencySign, currencyBlank)); } $(this).children('td').eq(2).text(upToTxt + ' ' + formatCurrency(discountUpTo * currencyRate, currencyFormat, currencySign, currencyBlank)); // $(this).attr('data-real-discount-value', formatCurrency(discountedPrice * currencyRate, currencyFormat, currencySign, currencyBlank)); }); } to function updateDiscountTable(newPrice) { $('#quantityDiscount').find('tbody tr').each(function() { var type = $(this).data('discount-type'); var discount = $(this).data('discount'); var quantity = $(this).data('discount-quantity'); var discountedPrice; var discountUpTo; if (type == 'percentage') { discountedPrice = newPrice * (1 - discount / 100); discountUpTo = newPrice * (discount / 100) * quantity; } else if (type == 'amount') { discountedPrice = newPrice - discount; discountUpTo = discount * quantity; } if (displayDiscountPrice != 0 && discountedPrice != 0) { $(this).children('td').eq(1).text(formatCurrency(discountedPrice, currencyFormat, currencySign, currencyBlank)); } $(this).attr('data-real-discount-value', formatCurrency(discountedPrice, currencyFormat, currencySign, currencyBlank)); $(this).children('td').eq(2).text(upToTxt + ' ' + formatCurrency(discountUpTo, currencyFormat, currencySign, currencyBlank)); }); } In community theme / niara this was fixed by commit https://github.com/thirtybees/niara/commit/e70102d1816aa1af03c2d8ff2b9d446146aa3ff9
  9. Does browsing on your site feel sluggish to you? I don't think so - on mobile your site loads reasonably fast. I'm quite sure you are not loosing any customers due to the loading time. I would just ignore this arbitrary number. There are better things to do instead of chasing SEO metrics.
  10. Hi, it's not possible to do that via CMS content. You can, however, include hook displayRevwsReviewList into your smarty template. Something like this: {hook h='displayRevwsReviewList' allowPaging=true order='date' pageSize=3 } This hook can take following parameters: displayReply - display shop replies or not. Allowed values: true | false. Default true displayCriteria - controls how to display criteria breakdown. Allowed values: inline | side | false. Default value is the one set up in your settings reviewStyle - controls review style. Allowed values: item | item-with-product. Default value item order - how to order reviews in list. Allowed values: date | usefulness | author | product | title | content | grade | id. Default is date orderDir - order in descending or ascending - Allowed values: desc | asc. Default value desc pageSize - how many reviews should be displayed on one page. Default 5 reviews allowPaging - controls if paging is allowed or not. Default value true product - display reviews for specific product only customer - display reviews submitted by specific customer guest - display reviews submitted by specific anonymous visitor category - display reviews for products from with specific category categoryTree - display reviews for products from with specific category and all its subcategories manufacturer - display reviews for products from specific manufacturer Looks like it's not possible to filter reviews to display store reviews only. I'll add this functionality to the next version of the module. If you need this functionality urgently, send me a PM, I'll tell how you can modify the module to support this
  11. Try to upload js/product.js from community or niara theme to panda to see if it fixes the problem. Back up the original file, of course
  12. This will most likely be override issue. Install standard thirtybees overridecheck module and it will show you more information
  13. I've re-tested with your numbers and it works fine for me. I guess this is either theme issue, or you are using old thirtybees version.
  14. data inconsistency in database. You can download my consistency check module, that might help you fix it
  15. I can't reproduce this issue. Could you please provide some screenshots, both from the admin and frontend? Note that this might be theme issue
  16. The module might appeared to work on ps16, but only because you probably run on lower version of php. But the problem was always there. New php versions are just more strict and complain louder. Anyway, this is not critical issue. The code still works, php just complains. You can disable debug mode and it will be 'fixed'. Alternatively, you can search for all occurrences of $currency->sign % 2 in this module *.tpl files, and replace them with $currency->sign
  17. I've seen this one. This module have some very strange code in its templates. For example: {if $currency->sign % 2}...{/if} The modulo (%) operator returns the remainder after division operation. If the 'sign' variable contained integer number, it would be ok. The result would always be either 0 or 1. However, the 'sign' variable in currency object does not contains number, it contains currency symbol. Such as € or $. Now, I'm not mathematician, but I guess expressions like € % 2 are not really valid. Thus the error code. Contact the module developer and ask them to fix it.
  18. also check position of 'displayPaymentEU' hook
  19. ps_carrier table has nothing to do with your issue
  20. This module is not compatible with new versions of *Smarty*, and in extension with thirtybees 1.1.0. You need to ask its developer for help.
  21. The reason is clear - database table ps_module_carrier is missing. You need to recreate it, and then associate your payment modules with carriers. CREATE TABLE `ps_module_carrier` ( `id_module` int(11) unsigned NOT NULL, `id_shop` int(11) unsigned NOT NULL DEFAULT '1', `id_reference` int(11) NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci; I wonder how you managed to delete this table in the first place. Also -- if possible, update to 1.1.x. Core updater would detect this critical issue and fixed it automatically for you during update.
  22. what do you mean "validate" ?
  23. Well, it's both bug in the module and compatibility issue. After order is created, mollie updates its price to include fee: $order->total_paid_tax_excl = $orderFeeNumber->plus( new Number((string) $order->total_paid_tax_excl)); $order->total_paid_tax_incl = $orderFeeNumber->plus( new Number((string) $order->total_paid_tax_incl)); The result of this operation is not a number, but object of type \PrestaShop\Decimal\Number When $order is saved, thirtybees calls standard php function round: round($value, _TB_PRICE_DATABASE_PRECISION_); Because the $value is object and not the number, this function return 1. Don't ask me why, it just does. PHP. In prestashop 1.6 there was different code: (float) str_replace(',', '.', $value); Because str_replace expects $value to be string, it calls $value->__toString() internally, which results in converting object to string. And thats the reason why the module works on prestashop. Pure luck. The fix should be done on both sides, I guess. In module, the lines should be replaced with $order->total_paid_tax_excl = (string) $orderFeeNumber->plus( new Number((string) $order->total_paid_tax_excl)); $order->total_paid_tax_incl = (string) $orderFeeNumber->plus( new Number((string) $order->total_paid_tax_incl)); Note the cast to string. This cast to string is enough to fix the issue. I have created a pull request for this change: https://github.com/mollie/PrestaShop/pull/232 Thirtybees core should be modified as well. Method ObjectModel::formatValue should check value and perform conversion if input it's not number or string
  24. look into server error logs look into thirtybees logs in /logs directory also, what curl version do you have?
×
×
  • Create New...