Edit Orders v3.0 for ZC 1.3.9 [Support Thread]

[xcooling]

yeah im busy recoding/upgrading edit_orders to 3.5

Are you having the following issue:
after you edit the order, the tax values get changed / overwritten ?

when you VIEW the order, it is correct, once u edit the order (edit orders), the tax values change and become incorrect. (when you VIEW the order after editing it)

[kalastaja]

Yes, a priori the order is ok, but after update taxes are duplicated.

[xcooling]

perfect, as i said earlier, easy fix.

using table orders_products instead of table orders_total will NOT fix the problem

BTW: every-time you use edit_orders v3.0 it corrupts your orders total table by overwriting the values.

Wont be an issue in 3.5

[kalastaja]

Ok, this is called "support" forum. Smirking is not as good as real advice...

I do so hope you have some sort of time estimate for 3.5!

[DivaVocals]

Ok, this is called "support" forum. Smirking is not as good as real advice...

I do so hope you have some sort of time estimate for 3.5!

Like all FREE Zen modules, these are labors of love and done when the contributor's free time permits.. So the best time estimate you can get is this: It's in development right now, and you will see an announcement about when it's ready posted here soon..

[kalastaja]

But of course.... But where do you fit in Diva, somehow xcooling would have been the proper commentator!?

The only reason for asking is to establish if oneself has to do it, or whether I'm prepared to wait!

[xcooling]

technically 3.0 is her module.
I run very large zen cart stores, and thus have rewritten most of the modules for my own use.

Edit order was one of them. I offered to merge my edit_orders with diva's edit orders and add some features

Right now, I am testing 3.5 in a production environment. Once i have all the bugs nailed, ill release it to diva to test.

When she is happy, It will then be ready for the public.

What ive completed to far (a few things not mentioned)

// Add: Verify edit orders module options to prevent errors and issues. 
// Add: GOB Package Trackers (unlimited carriers), which is much better than TY Trackers. *You can use None, TY or GOB trackers with this module*
// Add: multiple update buttons, due to requests from clients
// Add: product language support
// Add: product weights
// Add: order total weights
// Add: initial calculate shipping costs
// Add: edit and view product links
// Edit: minor template/style changes
// Edit: tweak input sizes, tweak icon/image placements
// Add: alternating row colors and mouse over highlighting of active row
// Edit: indent and neaten source code
// Edit: Rename SO_SWITCH -> EDIT_ORDERS_SO_SWITCH (prevent duplicate defines, default: false)
// Add: EDIT_ORDERS_MULTI_SUBMIT_SWITCH (allow multiple submit buttons, default: false)
// Add: EDIT_ORDERS_LAYOUT (specify the alignment of the edit order page, default: left)
// Remove: Double Nested Tables
// Add: Prevent double form submissions. *most users are impatient and will submit more than once*
// Edit: Merge 'update_order' code blocks (None,TY, GOB). *Smaller, more consistent code (~1100 redundant lines)*
// Edit: cast all id's to integer values (int), *$oID = zen_db_scrub_in($_GET['oID']); -> $oID = (int)($_GET['oID']);*
// Edit: cast all amount/tax values to floats
// Edit: zen_db_input(stripslashes($string)) -> zen_db_scrub_in($string) *safer, more accurate*
// Fix: Sanitize Product: id, name, model, qty, tax, final_price
// Add: Only update customer info items that have been changed. *safer, less database writes*
// Add: Only update product info items that have been changed.
// Add: Only update totals that have been changed.
// Fix: Prevent Nuking address information with NULLS.
// Fix: Display a message if no updates are performed.
// Fix: Correctly quote all SQL statements
// Add: Prevent working with nulls. *better be safe than sorry*
// Fix: Update Notifications

[kalastaja]

Ok! Sounds like it's worth waiting for...

[DivaVocals]

But of course.... But where do you fit in Diva, somehow xcooling would have been the proper commentator!?

The only reason for asking is to establish if oneself has to do it, or whether I'm prepared to wait!

My comment was a general comment with regards to modules/time lines and such which I would have posted regardless of my involvement with the upcoming release (which xcooling has explained).. I think it's important to make sure it's clear that those who develop modules have to be given a little latitude since these are volunteer efforts.. xcooling is a busy person and his OUTSTANDING effort on this next release is being done on his time. So I am willing to wait patiently until he passes it off to me for testing as I realize he has paying customers to attend to first..

[DivaVocals]

and while on this same topic I am going to respectfully ask the community to be patient while development and testing is taking place..

To be clear: I will not be not be sending out any "pre-launch" versions of Edit Orders to anyone once xcooling has passed his code over to me for testing.. In my experience this only leads to confusion post release.. Most importantly I no longer send out "pre-launch" versions because most people seem only to want an "advanced" copy of the module and will not properly test and provide feedback (which is the only reason to do a "pre-release" version).

We have beta testers already who have proven themselves WILLING to properly test for us before releasing and so we will not need anymore volunteers in this regard. Also once testing is complete and the new version is submitted to the downloads section, I will be making sure that the admins are given the proper amount of time to approve modules before deciding if it is warranted to temporarily host the new fileset (making the new version available to the public during the admin review and approval process)..