Edit Orders v4.0 Support Thread

[DivaVocals]

From the INSTALLATION section of the Readme.



followed shortly by




In upgrading to Edit Orders 4.1 from Edit Orders 4.04, and with SuperOrders 4.0.5 already installed, I understand that the two (2) orders.php in 2_Modified_Core_Files are not to be uploaded.

Also that admin\includes\functions\extra_functions\common_orders_functions.php is identical to that in EO 4.04, both essentially blank files and deprecated, so it makes no real difference whether the EO 4.1 version of this file is uploaded or not.

However, it is not clear from the instructions whether the EO 4.04 edit_orders_uninstall.sql file needs to be run, and all or any EO 4.04 files need to be removed, prior to uploading the EO 4.1 fileset.

Clarity appreciated.

ps if EO 4.1 is about to revised, the Readme could do with less hype and clearer instructions.

Not sure what you mean by "hype", but the current readme included information based on several things

1. Community suggestions/contributions to the readme
2. Frequently asked questions in the support thread

Inclusion of these elements in the readme have lead to fewer issues except in cases when the install instructions aren't followed.. Call it hype if you like, but it stopped most questions around these two areas of concern (the install SQL files). that said if you have more specific ideas for further improvements they are welcome.. (as they were before.. hence the current readme and it's contents)

[lhungil]

... However, it is not clear from the instructions whether the EO 4.04 edit_orders_uninstall.sql file needs to be run, and all or any EO 4.04 files need to be removed, prior to uploading the EO 4.1 fileset. ...

From the README under "Installation" tab: DO NOT RUN THE UNINSTALL SQL when upgrading!!!!!!.
Step 5 of the "Installation" tab addresses what needs to be done when "upgrading" from earlier versions (mostly 3.x/4.x).


These still hold true for EO 4.1 even though the readme may in some places still reference the "current version" as Edit Orders 4.0. I'm thinking about removing all version number references (other then the title at the top and the credits page) - as I feel they are confusing - and not needed. Thoughts?

if EO 4.1 is about to revised, the Readme could do with less hype and clearer instructions.

Any constructive contribution to the readme (and related files) is welcome! I would not expect a new public release for at least a month - possibly longer... So definitely some time for people to contribute with specific changes :)

[DivaVocals]

From the README under "Installation" tab: DO NOT RUN THE UNINSTALL SQL when upgrading!!!!!!.
Step 5 of the "Installation" tab addresses what needs to be done when "upgrading" from earlier versions (mostly 3.x/4.x).

with regards to the uninstall SQL the readme text is as follows:

DO NOT RUN THE UNINSTALL SQL when upgrading..

Let me repeat..

DO NOT RUN THE UNINSTALL SQL when upgrading!!!!!!
DO NOT RUN OLDER VERSIONS OF THE INSTALL/UPGRADE SQL FILES when installing/upgrading!!!!!! Doing so will cause issues with your Edit Orders v4.0 install.

May seem like "hype" but it was a FREQUENT issue that came up after the introduction of the auto-installer, and the community members who contributed suggestions to the readme contents felt it was important to highlight this.. Given some of the support question being fielded I agreed and included the suggested edits..

Sometimes some level of "hype" is needed to make sure something is communicated clearly to all levels of users.. Given that the inclusion of this text reduced the number of questions in this area, and the intent behind it's inclusion, it appears to have had the desired effect..

These still hold true for EO 4.1 even though the readme may in some places still reference the "current version" as Edit Orders 4.0. I'm thinking about removing all version number references (other then the title at the top and the credits page) - as I feel they are confusing - and not needed. Thoughts?

Agree.. some of this version specific text was included because of the transformation from prior versions of Edit Orders (v1.x-3.x) and wanting to make sure that end users understood that this was indeed a very different version of Edit Orders.. They've probably outlived their usefulness..

Any constructive contribution to the readme (and related files) is welcome! I would not expect a new public release for at least a month - possibly longer... So definitely some time for people to contribute with specific changes :)

**nods in agreement**

[lhungil]

... When editing my order if it has an attribute option i cannot select one ...

Not sure what exactly you are asking / stating... Here is a screen shot from a clean ZC 1.5.1 + EO 4.1 installation showing an order with attributes. You will note there are selectable dropdown options, checkboxes, and editable text fields. After making any needed changes to the attributes and clicking "update" the changes are saved (and the order updated).

Attachment 12504

I am using
zen-cart-v1.5.1
ceon_uri_mapping_4.4.1_for_zc
stock_by_attribute
Most of this work i have done by myself and not an experience programmer but knowledgeable :)
edit_orders_4.1

Please read the first page of the readme... In particular make note of the "Potential Future Enhancements" and "Known Issues".

[dw08gm]

From the README under "Installation" tab: DO NOT RUN THE UNINSTALL SQL when upgrading!!!!!!.
Step 5 of the "Installation" tab addresses what needs to be done when "upgrading" from earlier versions (mostly 3.x/4.x).


These still hold true for EO 4.1 even though the readme may in some places still reference the "current version" as Edit Orders 4.0. I'm thinking about removing all version number references (other then the title at the top and the credits page) - as I feel they are confusing - and not needed. Thoughts?


Any constructive contribution to the readme (and related files) is welcome! I would not expect a new public release for at least a month - possibly longer... So definitely some time for people to contribute with specific changes :)

Because in the readme the upgrade only refers to EO 4.0.3, not EO 4.0.4, it was unclear to me whether upgrading from EO 4.0.4 to EO 4.1 could be considered a "vanilla" install. And "upgrading from a previous Super Orders install" left me wondering.

FWIW Hype is what I expect from salespeople. Clear and concise is what I expect from installation instructions.

Happy to help in tidying the readme, although I only have the next two weeks to do so.

[DivaVocals]

Because in the readme the upgrade only refers to EO 4.0.3, not EO 4.0.4, it was unclear to me whether upgrading from EO 4.0.4 to EO 4.1 could be considered a "vanilla" install. And "upgrading from a previous Super Orders install" left me wondering.

Right.. just typos and leftovers from previous versions of the readme.. The "upgrading from a previous Super Orders install" text is leftover from the v3.0 changes.. I expect it will all be cleaned up in the next release.. I trust you are all straight now though.. right??

FWIW Hype is what I expect from salespeople. Clear and concise is what I expect from installation instructions.

Happy to help in tidying the readme, although I only have the next two weeks to do so.

Right.. respectfully I don't agree.. I don't see any part of the readme as "hype".. I see it as relaying an important change to the Edit Orders makeup which generated a TON of "where is the install SQL" questions.. The "hype" sorta squashed those questions.. It was a suggestion of a community member, and given that it stopped stopped some of the most frequently asked questions from being asked, then I'd say the "hype" was effective especially for novice shopowners (for whom these instructions were largely crafted to cover)..

That said, if you can provide constructive/explicit suggestions for the readme, then just as the suggestions of other community members are reflected in the current readme, then perhaps some of your suggestions could also be included..

[gromit1977]

Thank you for your reply i have attached some screen shots for you
when adding an item you can see that step three does not allow me to select option



once saved the attribute change to - :



i have fixed the pricing error from an earlier post #106

[lhungil]

Thank you for your reply i have attached some screen shots for you
when adding an item you can see that step three does not allow me to select option

You will want to check your debug / error logs to make sure no errors are being generated by the code on your site. If there are any errors you will want to address them first (I did see one missing language key - do not remember which one and your site is down for maintenance now).

The cause could be a large number of things. Thoughts off the top of my head: something not quite right with the installation / merging of EO 4.1 + "Stock by Attributes" into your Zen Cart installation, corrupted / Not correctly imported attributes and / or product options, the product option type does not allow selection (such as file, readonly, and custom types), or a compatibility issue with "Stock by Attributes" (as mentioned in the readme).

If you end up adding the needed code to allow the correct handling of various aspects of "Stock by Attributes", please post the code changes :)

[Gadgit]

I seem to have found another problem with attributes, I've searched the thread but can't see anyone else has noticed it.

If I have an order with two different products, which both have the same set of attributes available, but none selected (for example with checkboxes) and then check one box on the first product but leave all on the second product unchecked. When I then save the order, it checks the boxes for that attribute for all subsequent items in the order. It's not just the way it's displayed, it's actually modified the order itself.

I'm now looking in to it to see if I can see what's going on - does anyone have any ideas?

[Gadgit]

Sorry - I realise I didn't really provide much information about my set up.

Zen Cart 1.5.1 (Upgraded over time from 1.2.0 or something)
Edit Orders 4.1 (Installed successfully)
PHP 5.3.21

Other mods:
VAT-mod (doesn't affect Edit Order files)


Initial investigation shows that the attribute form fields seem to overwrite each other (for example if one uses just text fields). I am thinking that an extra layer to the Attributes form element array needs to be added which either corresponds to the order product id or the order row number.