Administrator
- Join Date:
- Sep 2009
- Location:
- Stuart, FL
- Posts:
- 14,067
- Plugin Contributions:
- 56
Edit Orders v4.0 Support Thread
@Prabu, thanks for the information. I'll post back once I've got this replicated!
Views: 346,056
Administrator
@Prabu, thanks for the information. I'll post back once I've got this replicated!
New Zenner
lat9:
@Prabu, thanks for the information. I'll post back once I've got this replicated!
Hi
Many thanks. Please provide some instructions to fix this issue.
Administrator
Prabu, please let me know your direct email address via PM (Private Message) so that I can send you an update to verify.
Administrator
The issue to which @Prabu refers will be seen on any site that uses multiple options with the same sort order when defining its products' attributes. I should have a correction available on GitHub within the next few days.
Administrator
lat9:
The issue to which @Prabu refers will be seen on any site that uses multiple options with the same sort order when defining its products' attributes. I should have a correction available on GitHub within the next few days.
... and the update is now available.
Note that there still might be some display differences in the ordering of the options/values from the initial order. See this Zen Cart posting for details.
Administrator
I've just submitted EO v4.2.3 to the plugins for review and will post back when it's available for download.
This version corrects the difference in attribute sorting between EO and the storefront (issue #49 in the plugin's GitHub repository).
Please check the readme; there's an additional edit required (up to ZC v1.5.5e anyway) to /includes/modules/attributes.php to make this work!
New Zenner
lat9:
I've just submitted EO v4.2.3 to the plugins for review and will post back when it's available for download.
This version corrects the difference in attribute sorting between EO and the storefront (issue #49 in the plugin's GitHub repository).
Please check the readme; there's an additional edit required to /includes/modules/attributes.php to make this work!
Hi
Thanks for the update. Now i've made some changes in YOUR_ADMIN/includes/classes/attributes.php using changes(Like upgraded version to 4.2.2) you did. But still no luck.
Same issues continues. Still option name and values were changed sort order after edit. Please see this small video http://recordit.co/W6RUrn8wjl
Please advice.
Administrator
Prabu:
Hi
Thanks for the update. Now i've made some changes in YOUR_ADMIN/includes/classes/attributes.php using changes(Like upgraded version to 4.2.2) you did. But still no luck.
Same issues continues. Still option name and values were changed sort order after edit. Please see this small video http://recordit.co/W6RUrn8wjl
Please advice.
Did you also make the changes on the storefront? They're described in the readme under the Interaction with Other Modules tab; you need to make similar edits to your storefront /includes/modules/YOUR_TEMPLATE/attributes.php.
I realize now that I should have highlighted that within the change history.
New Zenner
lat9:
Did you also make the changes on the storefront? They're described in the readme under the Interaction with Other Modules tab; you need to make similar edits to your storefront /includes/modules/YOUR_TEMPLATE/attributes.php.
I realize now that I should have highlighted that within the change history.
Hi
Sorry I've not applied same changes in /includes/modules/YOUR_TEMPLATE/attributes.php file. But i can't find the changes of this file in github and readme file of the module. Could you please provide this /includes/modules/YOUR_TEMPLATE/attributes.php file alone?
Administrator
lat9:
... and the update is now available.
Note that there still might be some display differences in the ordering of the options/values from the initial order. See this Zen Cart posting for details.
Prabu:
Hi
Sorry I've not applied same changes in /includes/modules/YOUR_TEMPLATE/attributes.php file. But i can't find the changes of this file in github and readme file of the module. Could you please provide this /includes/modules/YOUR_TEMPLATE/attributes.php file alone?
The file's changes are not on GitHub, since EO supports multiple Zen Cart versions. The link in the first post I've quoted identifies the changes necessary to your template-override of the storefront attributes.php processing.
As mentioned before, that change is documented in the EO readme under the Interactions with Other Modules tab.
Administrator
lat9:
I've just submitted EO v4.2.3 to the plugins for review and will post back when it's available for download.
This version corrects the difference in attribute sorting between EO and the storefront (issue #49 in the plugin's GitHub repository).
Please check the readme; there's an additional edit required (up to ZC v1.5.5e anyway) to /includes/modules/attributes.php to make this work!
v4.2.3 is now available for download: https://www.zen-cart.com/downloads.php?do=file&id=1513
zennedOut
hi,
when i look at ZC 1.5.5, it is supposedly compatible with php7.1.
has anyone tested the latest version of this module with php7.1?
the non-numeric arithmetic notices are now being reported in php7.1. see:
http://php.net/manual/en/migration71.other-changes.php
i'm curious before i consider upgrading various implementations of this module.
thanks.
Administrator
carlwhat:
hi,
when i look at ZC 1.5.5, it is supposedly compatible with php7.1.has anyone tested the latest version of this module with php7.1?
the non-numeric arithmetic notices are now being reported in php7.1. see:
http://php.net/manual/en/migration71.other-changes.php
i'm curious before i consider upgrading various implementations of this module.
thanks.
I haven't (yet) validated on PHP 7.1; I'll get to that next week and get any updates required posted to the plugin's GitHub repo.
Administrator
This is a bug that might be too difficult to fix; I don't know, but I thought I'd report it anyhow so that at least people were aware of it.
If you have added fields to the orders_products table (as, for example, the dropship module does), edit orders will lose those fields. On an edit - even an edit as small as changing the order status - edit orders deletes and re-adds the orders_products table records. Since it is unaware that these additional fields exist, they are added back with their default values.
Administrator
swguy:
This is a bug that might be too difficult to fix; I don't know, but I thought I'd report it anyhow so that at least people were aware of it.
If you have added fields to the orders_products table (as, for example, the dropship module does), edit orders will lose those fields. On an edit - even an edit as small as changing the order status - edit orders deletes and re-adds the orders_products table records. Since it is unaware that these additional fields exist, they are added back with their default values.
It's not a bug ... it's a feechur!:P
Seriously, though, that's how the current versions of EO work. I've been working over the past couple of releases to migrate the separate extra_functions file into a class-based structure which, in turn, will lead to a new major version of EO that reuses any orders_products table entries, if possible.
Administrator
Thanks Cindy. This is great news.
New Zenner
I'm using Zen Cart v1.5.1 and Edit Orders 4.1.4.
I get the following error in my log files:
PHP Warning: Invalid argument supplied for foreach() in my admin directory/includes/classes/mock_cart.php on line 151
I searched this thread but was unable to find any information. I can't seem to pin down when it's actually ocurring.
Just wondering if anyone has any tips for me to investigate. Thanks!
Administrator
Perhaps the order was missing products? That's the line where the class iterates over the products in the order.
New Zenner
lat9:
Perhaps the order was missing products? That's the line where the class iterates over the products in the order.
Thanks I'll go back and ensure I have products in the cart as that is likely what happened. Really appreciate the speedy reply!
Administrator
Suggestion on admin/includes/classes/editOrders.php
instead of
$ot_tax_class = constant ($ot_tax_class_name);
use
$ot_tax_class = null;
if (defined($ot_tax_class_name)) {
$ot_tax_class = constant ($ot_tax_class_name);
}
to prevent a PHP Warning in case the tax class doesn't exist.
Fields marked required must be completed.
Tell staff why this post should be reviewed.