Super Orders v3.0 Support Thread (for ZC v1.3.9)

[gob33]

I have a question:
Why having separated Super Orders and Edit Orders in v3.0 ?

This double the maintenance for updating the code and can introduce errors.
SO 1.3.9 by softwareguy incorporated edit_orders.php if i remember.
(I found also the define switch of EO not the same in SO)

[DivaVocals]

I have a question:
Why having separated Super Orders and Edit Orders in v3.0 ?

This double the maintenance for updating the code and can introduce errors.

Don't know where you got the impression that these modules were separated when in fact Edit Orders and Super Orders have ALWAYS been two separate modules.. (Please feel free to download both and read through the changelogs for BOTH modules if you still believe otherwise.)

SO 1.3.9 by softwareguy incorporated edit_orders.php if i remember.

You are mistaken.. SO v1.3.9 only added changes to bring to mod up to date with Zen Cart v1.3.9. Again, Edit Orders and Super Orders have ALWAYS been separate modules. What you may have mistaken as an integration of these apps was actually OLD original Super Orders code which added some very rudimentary order editing features to Super Orders.. This code never worked well and it was removed in v3.0..

In v3.0, we also decided to add the ability for users to easily integrate Super Orders with the Edit Orders module as it was something that folks were FREQUENTLY asking about. We felt that Edit Orders had BETTER order editing features and we decided NOT to re-invent the wheel by patching the rudimentary order editing that was part of older versions of Super Orders.

Updated to 1.3.9. No other changes.
Author: That Software Guy
Version: 1.3.9
Zen Cart™ Version: v1.3.9
Update added on Jul 05 2010
PHP 5.3 Compatible?: Yes
Download Now!
File size: 204775 bytes

(I found also the define switch of EO not the same in SO)

Not sure I understand this statement..

[gob33]

What you may have mistaken as an integration of these apps was actually OLD original Super Orders code which added some very rudimentary order editing features to Super Orders.. This code never worked well and it was removed in v3.0..

I see. Thats what i was talking.
I was thinking to integrate the code of Edit Orders 3.03 in Super Orders 3.0. EO consists mainly of edit_orders.php so could be integrated directly without complication to understand for the new users.

[DivaVocals]

I see. Thats what i was talking.
I was thinking to integrate the code of Edit Orders 3.03 in Super Orders 3.0. EO consists mainly of edit_orders.php so could be integrated directly without complication to understand for the new users.

Perhaps, but we decided to not re-invent the wheel. Edit Orders worked and had a good track record..

What WAS difficult for new users to understand was how to link these two modules (Edit Orders/Super Orders). Hence the number of questions surrounding that topic. It was EASY enough to provide links between the two modules.. It's not complicated at all for new users to understand.. Install Edit Orders, install Super orders turn on the buttons that links one to the other.. Simple..

[gob33]

File: admin\super_report_await_pay.php
Line 132: Missing a <?php

    </table></td>
  </tr>
<?
  if ($report_type) {
?>
  <tr>
    <td valign="top"><table border="0" width="100%" cellspacing="0" cellpadding="2">
      <tr class="dataTableHeadingRow">

[brushwoodnursery]

I apologize in advance for not taking the time to search the forum for this problem but it is fairly urgent. been working happily with Super Orders for a while. Just bumped our server from PHP4 to PHP5.2.17. There were a few minor hiccups but the site is back up. Today, my shipper needs to do some status updates but Batch Status Update brings up an error:
Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 35 bytes) in /home/xxxxxx/public_html/shop/includes/classes/db/mysql/query_factory.php on line 411

Batch Form Print does the same, Super Orders is working fine.

Any help would be greatly appreciated!

[brushwoodnursery]

OK, got it. The problem was the default memory limit when we upgraded the PHP. My host has it resolved. Nothing to do with this fine add-on.

[Kezza]

No worries.. The corrected file will be included in the next release (still working on the updated readme..)

have you had a chance to get to the update?

[carlvt88]

I had a recent problem and while it was due to my own bone-headedness, I wonder if a safeguard could be put in place.

In batch_status_update, I cleared the 'notify customer' checkbox, then clicked 'Check All' and 'update status'. Unfortunately, when I clicked 'Check All', it reset my prior settings so I ended up sending a bunch of emails to people with a default status.

I *was* able to use query builder to help me send apologies to the affected people though

Suggestion 1: Don't reset the 'notify customer' box, or make the default 'unchecked'. I did this by changing line 311 in super_batch_status.php:

	echo zen_draw_checkbox_field('notify', 'on', false); echo ' ' . ENTRY_NOTIFY_CUSTOMER

I'll probably go through and do this in other places too.

Suggestion 2: Offer a confirmation box when sending more than N emails.

Great package - thanks for your help

[DivaVocals]

Thanks for the tip/suggestion..

Still reviewing the files you sent.. Been a little busy with the new day job and some pretty big client projects..

Will see if I can carve out time for this and all the other things on my "to-do" list..

I had a recent problem and while it was due to my own bone-headedness, I wonder if a safeguard could be put in place.

In batch_status_update, I cleared the 'notify customer' checkbox, then clicked 'Check All' and 'update status'. Unfortunately, when I clicked 'Check All', it reset my prior settings so I ended up sending a bunch of emails to people with a default status.

I *was* able to use query builder to help me send apologies to the affected people though

Suggestion 1: Don't reset the 'notify customer' box, or make the default 'unchecked'. I did this by changing line 311 in super_batch_status.php:

    echo zen_draw_checkbox_field('notify', 'on', false); echo ' ' . ENTRY_NOTIFY_CUSTOMER

I'll probably go through and do this in other places too.

Suggestion 2: Offer a confirmation box when sending more than N emails.

Great package - thanks for your help