Printable View
I've seen this posted in one other place back in this thread, but not answer. Is there a way to set default settings so that I don't have to set them every time? My export settings are the same every time I run the export, so it would be nice to not have to set them each time.
Great, thanks for providing these. I suspected they were "later in the day" numbers. I will make a few alterations in calculation of the date / time in the next version to see if this can be remedied. I appreciate the feedback!Quote:
Originally Posted by split63
Currently the is no way to "save" your configuration (maybe an option I could consider for future versions) but you can preset options if you know php.Quote:
Originally Posted by stevelucky
To do this you would need to open the file shipping_export.php found in the root of the admin folder. Then scroll to the bottom where the form is generated and add "selected" etc... to the items you want to have preselected. I've done this on a number of installs and it works well.
One quick fix that is not ideal, but better than nothing, would be to provide a separate include file that we could edit. In the file is each of those variables and a simple "0" or "1" next to each variable.Quote:
Originally Posted by econcepts
Users would then edit the file and set the values to one or zero. Then each time Export is used, these default values set the check boxes accordingly.
This would be much easier and safer than going in and editing each corresponding line in the php file. I had gone in an edited the php file, but when I upgraded to v1.3.2. those edits were lost. With the include file approach, new updates would not be a problem
Nice idea there. I'll look at incorporating that into the next release.
nice mod here. I just installed it and I'm getting a 1064 error (error in SQL syntax) when I attempt to export. Any idea what could be causing this. (my server is using PHP 5.2.9)
Quote:
1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND cc.countries_name = o.delivery_country WHERE o.orders_id = ot.orders_id AND' at line 1
in:
[SELECT o.orders_id, customers_email_address, delivery_name, delivery_company, delivery_street_address, delivery_suburb, delivery_city, delivery_postcode, delivery_state, delivery_country, shipping_method, customers_telephone, order_total, op.products_model, products_name, op.products_price, final_price, op.products_quantity, date_purchased, ot.value, orders_products_id, order_tax, o.orders_status, o.payment_method, cc.countries_iso_code_2 FROM (3wuw_orders o LEFT JOIN 3wuw_orders_products op ON o.orders_id = op.orders_id), 3wuw_orders_total ot, 3wuw_countries cc AND cc.countries_name = o.delivery_country WHERE o.orders_id = ot.orders_id AND ot.class = 'ot_shipping' AND downloaded_ship='no' ORDER BY orders_id ASC]
If you were entering information, press the BACK button in your browser and re-check the information you had entered to be sure you left no blank fields.
I had ISO Country Code checked, when I went back and unchecked it , it worked.Quote:
Originally Posted by magnusrf
In the shipping_export.php file is looks like there are plans to enable exporting as an XML file?
This would be great since I have a 3rd Party Fulfillment warehouse that prefers an XML file when I send them my orders. Any idea if and when we could see this functionality?
What version of the module are you using?Quote:
Originally Posted by magnusrf
I'll have to look and see if anything else changed that would have added or dropped something when the ISO codes are used. Anyone else notice this problem on their system?
This is indeed on the drawing board to add. Just haven't got a hard date on it yet. I was working on correcting a number of issues that arose in previous releases to come back to a new "stable" version (which I think from current reports we have now with 1.3.2).Quote:
Originally Posted by magnusrf
The issue with the XML file to a degree is that some fulfillment houses want the XML file in a certain format with records indicated in various forms. This XML file would be a standard type of export that they would have to map to for it to work (so we have a consistent basis for all users.)