DannetStudio

In PS 1.6, the used cart rule / voucher ID associated to an order is saved on the table order_cart_rule, but in this table is stored only the voucher name, not the voucher code. The code is stored on table cart_rule, so you need to obtain first the cart rule ID associated with the order, and go to the cart_rule table and look for the code asociated with that ID. I've added a column with the voucher code used in admin order list using overrides, that is recommended, so the code changes (actually the way in which it is implemented), with respect to the initial examples of this thread: class AdminOrdersController extends AdminOrdersControllerCore { public function __construct() { parent::__construct(); $this->_join .= ' LEFT JOIN `'._DB_PREFIX_.'order_cart_rule` ocrt ON (ocrt.`id_order` = a.`id_order`)'; $this->_select = 'ocrt.`id_cart_rule` AS `coupon_id`,'.$this->_select; $this->_join .= ' LEFT JOIN `'._DB_PREFIX_.'cart_rule` cr ON (cr.`id_cart_rule` = ocrt.`id_cart_rule`)'; $this->_select = 'cr.`code` AS `voucher_code`,'.$this->_select; $this->fields_list['voucher_code'] = array('title' => 'Voucher Code', 'align' => 'center', 'width' => 65, 'havingFilter' => true ); } } It should be placed on a new file called AdminOrdersControllers.php, in folder /override/controllers/admin Regards, Daniel

Thank you! It fix the issue with dashboard with PHP 7.1

Same problem after upgrading to php 7.1 with PS 1.6.1.11. Uncaught TypeError: window[data_type] is not a function at Object.success (dashboard.js:52) at j (jquery-1.11.0.min.js:2) at Object.fireWith [as resolveWith] (jquery-1.11.0.min.js:2) at x (jquery-1.11.0.min.js:4) at XMLHttpRequest.b (jquery-1.11.0.min.js:4) I've also noted in php error_log a lot of: Illegal string offset in > /classes/Hook.php on line 554

I've purchased this module days ago for second time, the first time was last year but in the last version he has added the "filter by carrier" feature, so I bought it again. I confirm too that the module DONT work, it has many bugs, and definitely its not ready to run with multishop, it just save the data without any id_shop associated, so there is not way to make it run on frontend, at least configuring it from backend. After spending many hours analyzing the code, I have corrected most of the problems, most of them "harcoding" the code and filling the database fields directly, but still it does not fulfill some of its objectives. Anyway, if anyone has any problems you can contact me and I can help to correct the code. I tried to communicate with the seller of the module but he does not respond the tickets, and seeing their activity in this forum, many months have passed since the last time he was connected. Apparently he is no longer working on it, but yes, his website (www.ecommy.com) has the form of payment active

Lo que pasa en ese caso es que el creador es Inglés, vive en Inglaterra. De todas formas teniendo en cuenta el costo de otros modulos y que éste proporciona actualizaciones gratuitas indefinidas, no es tan caro en comparación.

I think the problem is related with multishop / seo urls, In my case, I had no problems installing it on a sigle-shop prestashop, but when multishop is enabled, I never could install it. I get the error "Cannot retrieve test results", because the module cant be confirmed with analytics. I tried with SEO urls enabled and disabled, configured the module for specific shops, all shops, group shops, but not results.

Same here, the unique way I found is to purchase very expensive modules to achieve this very basic feature, As with other really basic things with prestashop...

Hello! Have you been able to solve this? I'm just trying to do the same!

Same problem here in different stores (*.0.9 & *.0.12).

I've a problem too upgrading to *.13: Todos los archivos actualizados. Actualización de bases de datos en curso... Error durante la actualización de la base de datos. Puede que tenga que restaurar la base de datos. Restaurando archivos ... Restoring *.12

The bugs / issues related with Advanced Stock Management and marked as solved in *.12 (http://forge.prestashop.com/browse/PSCSX-2818) is not really fixed.

From what I read reports of similar cases in the bug tracker and other forum posts, prestashop not consider this as a bug, but its part of how they have designed the product packs functionality. It's weird but they devised the products packs stock to be updated manually. I dont think they will correct this for the prestashop current or older versions, but maybe this feature could be included in future PS versions as a configuration option, although mine are just speculations.

I've purchased the module and tested it on a PS 1.6.0.8. It seems to work very well and fix the problem of the automatic packs stock based on the included products real stock. I've tried to simulate all the possible context of working and I didnt found any problems with it, and also it calculates without problems the pack stock when it contains more than a unit of a same product. I think it's bad enough to have to pay for a module to correct something that common sense dictates that it should work natively on the system, but apparently there is no alternative.

Hola @Asfalta, actualmente estoy usando el módulo de oca y funciona bien. El funcionamiento no es tan automatizado como MercadoEnvíos, ya que por el momento se limita a crear una carrier rule por cada operativa que cargues desde OCA (por ej Puerta a Puerta Estandar, Puerta a Puerta Prioritario, Sucursal a Puerta Estandar, SAP Prioritario, etc), y a partir de esto permite a la hora de seleccionar el método de envío, calcular automáticamente, a través de la API de OCA, los costos del envío al cliente, teniendo en cuenta el código postal de origen y de destino ( el del cliente y la dirección de envío seleccionada ), y también el peso y volumen de los elementos del carro de compras. También te permite ingresar el tracking number una vez que está cargado en OCA el pedido de envío o de admisión, para que el cliente pueda ver el estado del envío (por ahora también solo desde la web de OCA). De todas formas el desarrollador está trabajando en la próxima versión, que por lo que me dijo incluye ya la generación del pedido de admisión a OCA E-Pack automática y directamente desde el propio administrador de prestashop, y más adelante también va a incluir la modalidad de envío a sucursales con la posibilidad de selección de sucursal cercana a la dirección del cliente. En cuanto a MercadoPago, yo estoy usando también un módulo creado por el mismo desarrollador que el de OCA E-Pack ( http://addons.prestashop.com/es/pagos-prestashop-modulos/4919-mercadopago-payment.html, cuesta U$55), y funciona muy bien, incluso incorpora la opción de sandbox para realizar pagos de pruebas y te permite definir un % adicional sobre el total del pedido al seleccionar este método de pago. Funciona muy bien, todavía no tuve ningún problema y lo actualiza bastante seguido. Saludos!

I've found another module that seems to do this work. Its more complex and have extra features as calculate the package price based on products contained and options about combinations of included products, in addition to synchronizing the stock. But its really expensive: http://keutche-dev.com/blog/category/modules-documentation/