[ic] 4.9.3 "ship status update failed"

[Grant]

>>>I just moved my store from my old server running IC 4.8.5 to a new
>>>server running IC 4.9.3 and now when I try to update the status of an
>>>order via "Ship all lines -> Update the order" I get the following
>>>message in green on the Pending Orders page:
>>>
>>>Orderline 00000150-1 ship status update failed.
>>>
>>>Here is what is in my log file.
>>>
>>>24.103.254.107 nsNTBLSU:24.103.254.107 - [04/January/2003:17:16:09
>>>-0800] daboy /~daboy/cgi-bin/cart.cgi/admin/order Attempt to set slice
>>>of 00000150-1 in read-only table orderline
>>>24.103.254.107 nsNTBLSU:24.103.254.107 - [04/January/2003:17:16:36
>>>-0800] daboy /~daboy/cgi-bin/cart.cgi/admin/order Attempt to set slice
>>>of 00000150-1 in read-only table orderline
>>>24.103.254.107 nsNTBLSU:24.103.254.107 - [04/January/2003:17:16:47
>>>-0800] daboy /~daboy/cgi-bin/cart.cgi/admin/order Attempt to set
>>>orderline::status::00000150-1 in read-only table
>>>24.103.254.107 nsNTBLSU:24.103.254.107 - [04/January/2003:17:16:47
>>>-0800] daboy /~daboy/cgi-bin/cart.cgi/admin/order Unable to send mail
>>>using /usr/lib/sendmail
>>> > Message follows:
>>>
>>>
>>>The status is changed to "shipped" just fine, but no ship_notice email
>>>is sent.
>>>My "transactions" table's order status updates to "shipped" just fine,
>>>but the status for each line item in the "orderline" table remains at
>>>"pending".
>>>
>>>
>>>I have found this exact problem posted by Grant on Nov. 12th but there
>>>was not solution.  Can someone please help?

   I did have that exact same problem.  The problem is with the orderline
table write permission, which doesn't make any sense to me since there is:

[flag type=write tables="orderline transactions"]

right in the order_status.html page.  Does anyone know if this been
corrected since 4.9.3?  It seems like a bug that most people would run into.
What ended up happening with my catalog was WRITE_CONTROL statements were
added to catalogs/ic493/dbconf/default_db/orderline.dbm to make the table
"writable" all the time.  I hope this isn't a security problem.  I would
love to know about a better solution if anyone has one.

- Grant