adtastic

trying to amend or save a new tax rule throws this error and does not save the change: Property TaxRulesGroup->date_add is not valid. have version 1.6.1.1 thought it was supposed to be fixed in this version. any ideas on how I can fix this need to be able to charge tax in an area asap.

yes suppose that would work except it creates the issue of having a gap in between order numbers and somewhere down the line that might be a problem at least with respect to accounting.

yes, aware of this. however the problem is our current invoice number is 27596. Our current last order number is 27587. See the problem? We cannot set a new invoice number to coincide with the next order which would be 27588.

The prestashop invoice number versus order number versus reference id is screwy as hell but even beyond that we are having an issue which we cannot figure out and need to find a way to fix or hack a better solution. prestashop makes an order id which is a bunch of letters. then it also makes an order number which is... numbers. then it ALSO makes an invoice and subsequent invoice number. So, a customer calls us and gives us an invoice number. we cannot look up the order by invoice number. there is no search field to look up an order by invoice number which is the first problem. having the customer dig out and find the bunch of letters of the reference number is cumbersome to them we can look by name but that is slower process. better to be able to simply plug in the invoice number since this is what the customer references. so this is the first problem which needs a solution. Secondly, the invoice number is not the same as the order number. if it was that would solve our biggest problem. We even turned off invoices for a time so we could wait for the order number to catch up and we could change the next invoice number to match the next order number in order for the two to sync up because having them be the same number solves our problem on how we internally track orders outside of prestashop. But after a few weeks they are no longer synched again. DOES ANYONE KNOW WHY THEY WOULD GET OUT OF SYNC? We thought once it might have to do if we delete an order. Or maybe if we cancel an order. But seems this is not the reason. So why once these two are synced after a time they are out of sync again? Personally, we'd like to do away with invoices altogether but we cannot. Because our internal system both for tracking, accounting and otherwise outside of prestashop compels us to need to print out each order. And it prints three pages long but if we print the invoice it is only one page so we are stuck using invoices for our tracking system. But we need the invoice number to be the same as the order number always. How do we accomplish this? personally if the invoice number was the same as the order number all would be fine, period.

anyone have any ideas on this? Really need to be able to cancel orders and seems there is a bug here.

I have 1.6.1.1 and have applied the above fix. still cannot cancel an order. get this error: [PrestaShopException] Property StockAvailable->id_product_attribute is empty at line 909 in file classes/ObjectModel.php 904. } 905. 906. $message = $this->validateField($field, $this->$field); 907. if ($message !== true) { 908. if ($die) { 909. throw new PrestaShopException($message); 910. } 911. return $error_return ? $message : false; 912. } 913. } 914. ObjectModelCore->validateFields - [line 246 - classes/ObjectModel.php] ObjectModelCore->getFields - [line 652 - classes/ObjectModel.php] ObjectModelCore->update - [line 406 - classes/stock/StockAvailable.php] - [1 Arguments] StockAvailableCore->update - [line 128 - Core/Business/Stock/Core_Business_Stock_StockManager.php] Core_Business_Stock_StockManager->updateQuantity - [line 472 - classes/stock/StockAvailable.php] - [4 Arguments] StockAvailableCore::updateQuantity - [line 206 - classes/order/OrderHistory.php] - [4 Arguments] OrderHistoryCore->changeIdOrderState - [line 531 - controllers/admin/AdminOrdersController.php] - [3 Arguments] AdminOrdersControllerCore->postProcess - [line 178 - classes/controller/Controller.php] ControllerCore->run - [line 367 - classes/Dispatcher.php] DispatcherCore->dispatch - [line 58 - admin/index.php]

yes good question but demo mode is off.

This is a brand new installation of 1.6.1.4 and was installed 4/11/2016. In the dashboard from the 11th thru today the 19th it says there have been 2,730 visits. IN reality per the logs there have only been 263 visits. For example today it says there have been 221 visits but in reality again according to actual server logs there have only been 7 visits. Obviously something is very wrong and this will kill any ability to have correct data.

perfect, thanks for the input!

We have select products that are sold via attributes and the quantity is selected via a dropdown box in the attributes. Have a problem where a lot of people try to increase the quantity via the default quantity box in prestashop because they are not computer savvy and it results in a lot of abandoned carts. We need to remove the default quantity box only from these products sold via attributes but not other products. They are in various categories so just isolating one category won't work. I found this link to a thread that purports to offer a solution: https://www.prestashop.com/forums/topic/165599-solved-display-the-quantity-box-for-some-products-only/ but it is a little confusing. Not sure if it is a solution so need some help from someone that understands prestashop coding better than I do. The code it provides is this: Where the attributes are displayed change {foreach from=$groups key=id_attribute_group item=group} to {assign var='attribute_group_exists' value=0} {foreach from=$groups key=id_attribute_group item=group} {if $id_attribute_group == ID_OF_THE_ATTRIBUTE_GROUP} {assign var='attribute_group_exists' value=1} {/if} Where quantity is displayed: {if $attribute_group_exists == 1} <input type="hidden" name="qty" id="quantity_wanted" value="1"/> {else} [PUT HERE THE CURRENT CODE FOR QUANTITY INPUT] {/if} my assumption here is that the code will indeed hide the quantity box if a product has attributes is this correct? And if so I am confused about how to implement it. I know where it goes. The first part seems straightforward. But the second part where it says: {if $id_attribute_group == ID_OF_THE_ATTRIBUTE_GROUP} what is "ID_OF_THE_ATTRIBUTE_GROUP" and where do I find this? Or, is there a better solution to do what I am trying to do?

This does exactly what i need to do in a store however there are multiple categories we need to hide the add quantity box. How would I write this to include multiple category numbers?

prestashop 1.6.1.1 I cannot cancel a customer order. This throws an error. See image. http://oi59.tinypic.com/zoghfs.jpg any ideas how to fix this? In particular all of our stock is "zero" and customer can order even when out of stock. (its all custom made products so we don't actually carry "stock" per se). The invoice says number ordered is one and number available 0 so wonder if that is the issue. If so, need to figure out we can override this.

Thanks Nemo, of course you are correct. Thought I had turned it off and it was still showing but if I turn off the cross selling module it goes away from the order page. Here is the bigger problem however. I'd like to have cross-selling. But the button for the product puts the product straight into the cart. This doesn't work with our store since everything is a customized product and sold therefore by attributes. If they click the item or the image it does put them into the product page but just the button is an "add to cart' button. Any idea how I can hack this module so the button actually goes to the product and doesn't simply put the product in the cart?

it is the default template. Here is a screenshot showing what I am talking about.

No one has an answer to this question? I really need to figure out how to control or remove the products displayed on the cart page either by removing it altogether, changing the link to add it to the cart so it goes directly to the product or removing that link.