Edit Orders v4.0 Support Thread

[dw08gm]

From the INSTALLATION section of the Readme.

AUTO INSTALLER!! No more external SQL files needed to install/upgrade Edit Orders.. Yep that's right.. The Edit Orders install/upgrade is easier than ever!!! Whether you are upgrading from a previous Super Orders install or doing a vanilla Edit Orders install, the newauto installer has got you covered. Please note: Uninstall is not automated. So to uninstall you will still need to use an external SQL file.

followed shortly by

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.

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.

[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**

[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..