P&G - Order Processing + Manual Entry v_0.5

[mugitty]

I know that this mod is a bear to set up and still needs some tweaks here and there, but it really has some neat features. I've managed to get it working pretty much to an acceptable level with one exception that I can't figure out, so I'm hoping that someone else who is using it has found the solution already. In the status and email section of the admin interface:

When you update the status with "Notify Customer" checked (1), it automatically sends an email to the customer, advising them of the status of their order. This is really neat, because it will also place a checkmark (2) to let you know that the customer was notified of that particular status change.

 

Trouble is, when you use this feature, the mail goes but, instead of the order status particulars, you get this:

Farmers Exchange

------------------------------------------------------

Order Number: 7

Detailed Invoice: https://secure14.vosn.net/~farmex/catalog/a....php?order_id=7

Date Ordered: Monday 23 December, 2002

 

EMAIL_TEXT_STATUS_UPDATE

You can send email with the email function (3), but it doesn't give you the visual record like number (2) and it is in a different format that doesn't show the comments you may have added.

 

If anyone has gotten this up and running correctly, I would really appreciate (select one or more): advice, pointers, direction, code changes, a drink

 

Thanks :!:

[Guest]

I have the exact same error with ver. 0.4

 

I didn't want to "upgrade" to 0.5 unless I had a compelling reason; seeing that this is not fixed, I assume it's a core issue with the contribution and I'm not sure what to do about it. :?

 

I am going to do more testing this week to see if I can nail down the cause/fix.

 

:D Bailey

[Guest]

mugitty, I have a question for you...

 

See if you can replicate the error under the same circumstances, I've had it happen two different ways now.

 

1. Place test order

2. Pretend to process it. :) When I change the order from Pending -> Processing, the e-mail is fine.

3. I followed these steps for processing the shipping...

:: a. I entered the UPS tracking information and clicked update

:: b. I changed the order status from Processing -> Shipped. An e-mail was sent out, and it had this (realize I haven't configured my secure server on the cart yet):

Country Bear

------------------------------------------------------

Order Number: 5

Detailed Invoice: /shop/account_history_info.php?order_id=5

Date Ordered: Sunday 02 February, 2003

 

EMAIL_TEXT_STATUS_UPDATE

:: c. then I clicked the e-mail update box, and in this case, the e-mail sent was a-ok:

Dear Abby Test

 

Thank you again for your order with us at Country Bear.

 

Your order has been updated to the following status.

 

Please reply to this email if you have any questions. Please mention the Order Number

 

------------------------------------------------------

Order Number: 5

Detailed Invoice: /shop/account_history_info.php?order_id=5

Date Ordered: Sunday 02 February, 2003

 

------------------------------------------------------

Shipping Status: Shipped

 

Shipping Information:

 

Shipping Method: UPS

Tracking Number: 1ZY88xxxx39199XXXX

Planned Shipping Date:2003-02-03

Track your Order on the Shipper Web Site:

http://wwwapps.ups.com/etracking/tracking....88xxxx39199xxxx

 

 

 

Thank you again for choosing Country Bear for

your gift & collector needs!

 

Warm regards,

 

Country Bear

 

http://www.country-bear.com

(I made changes to the tracking number in the quote to protect the 'real' # I cut & pasted for my test)

 

So in this case, for me the e-mail was fine.

 

However I was playing around with an "old" order and the "error" e-mail was sent out by clicking the button, under other circumstances.

 

Obviously I would prefer to get rid of the error completely, but also if I can figure out a work-around (steps a - b - c in practice) so that my customers never receive it that would be okay I guess.

 

Anyway I am just trying to iron out under which conditions it is sending the error... I was wondering if their contrib is missing a part that we need to paste in somewhere.

 

:D Bailey

[Guest]

OH YEAH!

 

And it's related to this, I had forgotten :) the question is, where do we snatch what we need?

 

Login to your Admin. Go to Shipping > Templates Admin

 

Do you get this too?

Template Status Admin - [Read Template Status Admin Process before updating. CLICK Here]

 

 

1146 - Table 'cbear_osc2.spg_template_status' doesn't exist

 

select count(*) as total from spg_template_status p

 

[TEP STOP]

When I click there, the window that pops up is empty. For you too???

 

So when we created tables as instructed, obviously Table 'cbear_osc2.spg_template_status' was missing from the .sql file we were provided. OK, yeah, I just ran a search for spg_template_status and couldn't find it in the file:

# phpMyAdmin MySQL-Dump

# version 2.2.6

# http://phpwizard.net/phpMyAdmin/

# http://www.phpmyadmin.net/ (download page)

#

# Generation Time: Dec 15, 2002 at 05:42 PM

# Server version: 3.23.49

# PHP Version: 4.2.3

# --------------------------------------------------------

 

#

# Table structure for table `popup_help`

#

 

DROP TABLE IF EXISTS popup_help;

CREATE TABLE popup_help (

help_id int(11) NOT NULL auto_increment,

help_number int(11) NOT NULL default '0',

help_class varchar(25) NOT NULL default '',

help_module varchar(25) NOT NULL default '',

help_file_name varchar(50) NOT NULL default '',

help_title varchar(45) NOT NULL default '',

help_text longtext NOT NULL,

help_version varchar(12) NOT NULL default '',

status tinyint(1) NOT NULL default '0',

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

UNIQUE KEY help_number (help_number),

KEY help_id (help_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `popup_help`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_auction_type`

#

 

DROP TABLE IF EXISTS spg_auction_type;

CREATE TABLE spg_auction_type (

auction_type_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

auction_type_date_added datetime default NULL,

auction_type_last_modified datetime default NULL,

auction_type_name varchar(35) default NULL,

auction_type_title varchar(35) default NULL,

auction_type_class int(1) NOT NULL default '0',

auction_type_url varchar(100) NOT NULL default '',

auction_type_url_tracking varchar(100) NOT NULL default '',

auction_user_id varchar(40) NOT NULL default '',

status int(1) default '1',

auction_type_comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (auction_type_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_auction_type`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_authorise`

#

 

DROP TABLE IF EXISTS spg_authorise;

CREATE TABLE spg_authorise (

authorise_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

authorise_date_added datetime default NULL,

authorise_last_modified datetime default NULL,

authorise_name varchar(35) default NULL,

authorise_title varchar(35) default NULL,

status int(1) default '1',

authorise_comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (authorise_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_authorise`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_carriers`

#

 

DROP TABLE IF EXISTS spg_carriers;

CREATE TABLE spg_carriers (

carriers_id int(11) NOT NULL auto_increment,

carriers_phone varchar(25) NOT NULL default '0',

carriers_date_added datetime default NULL,

carriers_last_modified datetime default NULL,

carriers_name varchar(35) default NULL,

carriers_url varchar(100) default NULL,

carriers_track_url varchar(100) NOT NULL default '',

status int(1) default '1',

carriers_comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

products_id int(11) NOT NULL default '0',

PRIMARY KEY (carriers_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_carriers`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_contacts_email`

#

 

DROP TABLE IF EXISTS spg_contacts_email;

CREATE TABLE spg_contacts_email (

contact_email_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

contact_email_date_added datetime default NULL,

contact_email_last_modified datetime default NULL,

contact_info_name varchar(35) default NULL,

contact_info_title varchar(35) default NULL,

contact_info_value varchar(45) NOT NULL default '',

email_subject varchar(65) NOT NULL default '0',

status_update longtext NOT NULL,

auction_merchant varchar(65) NOT NULL default '',

auction_subject varchar(65) NOT NULL default '',

history_info varchar(100) NOT NULL default '',

auction_access longtext NOT NULL,

status_auc_update longtext NOT NULL,

auction_note longtext NOT NULL,

status int(1) default '1',

signature longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

sales_note longtext NOT NULL,

PRIMARY KEY (contact_email_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_contacts_email`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_contacts_info`

#

 

DROP TABLE IF EXISTS spg_contacts_info;

CREATE TABLE spg_contacts_info (

contact_info_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

contact_info_date_added datetime default NULL,

contact_info_last_modified datetime default NULL,

contact_info_name varchar(35) default NULL,

contact_info_title varchar(35) default NULL,

contact_info_value varchar(45) NOT NULL default '',

company_name varchar(45) NOT NULL default '0',

company_address varchar(50) NOT NULL default '',

company_city varchar(40) NOT NULL default '',

company_zip varchar(15) NOT NULL default '',

company_state varchar(15) NOT NULL default '',

company_phone varchar(25) NOT NULL default '',

company_fax varchar(25) default NULL,

company_url varchar(80) NOT NULL default '',

company_email varchar(35) NOT NULL default '',

company_doc_title varchar(25) NOT NULL default '',

status int(1) default '1',

thank_note longtext NOT NULL,

special_note longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (contact_info_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_contacts_info`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_man_info`

#

 

DROP TABLE IF EXISTS spg_man_info;

CREATE TABLE spg_man_info (

spg_man_info_id int(11) NOT NULL auto_increment,

spg_man_name varchar(25) NOT NULL default '',

status int(1) NOT NULL default '0',

manual_date_added datetime NOT NULL default '0000-00-00 00:00:00',

manual_last_modified datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

spg_man_key varchar(24) NOT NULL default '0',

spg_defined varchar(10) NOT NULL default '',

spg_man_key2 varchar(24) NOT NULL default '0',

spg_man_key3 varchar(35) NOT NULL default '',

PRIMARY KEY (spg_man_info_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_man_info`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_order_status`

#

 

DROP TABLE IF EXISTS spg_order_status;

CREATE TABLE spg_order_status (

order_status_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

order_status_date_added datetime default NULL,

order_status_last_modified datetime default NULL,

order_status_name varchar(35) default NULL,

order_status_title varchar(35) default NULL,

order_status_class int(1) NOT NULL default '0',

order_type_url varchar(100) NOT NULL default '',

status int(1) default '1',

comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (order_status_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_order_status`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_order_type`

#

 

DROP TABLE IF EXISTS spg_order_type;

CREATE TABLE spg_order_type (

order_type_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

order_type_date_added datetime default NULL,

order_type_last_modified datetime default NULL,

order_type_name varchar(35) default NULL,

order_type_title varchar(35) default NULL,

order_type_class int(1) NOT NULL default '0',

order_type_url varchar(100) NOT NULL default '',

status int(1) default '1',

comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (order_type_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_order_type`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_orders_shipping`

#

 

DROP TABLE IF EXISTS spg_orders_shipping;

CREATE TABLE spg_orders_shipping (

orders_id int(6) NOT NULL default '0',

orders_shipping_tracking_no varchar(40) NOT NULL default '',

orders_shipping_date_shipped date NOT NULL default '0000-00-00',

orders_shipping_carrier varchar(11) NOT NULL default '0',

orders_shipping_auction_comment longtext NOT NULL,

orders_shipping_comment_customer text NOT NULL,

orders_shipping_updated datetime NOT NULL default '0000-00-00 00:00:00',

orders_shipping_status varchar(10) NOT NULL default '',

orders_shipping_weight int(10) NOT NULL default '0',

order_type varchar(11) NOT NULL default '0',

auction_type varchar(11) NOT NULL default '0',

auction_no varchar(50) NOT NULL default '',

auction_end_date date NOT NULL default '0000-00-00',

payment_type varchar(11) NOT NULL default '0',

payment_ref varchar(25) NOT NULL default '',

payment_date date NOT NULL default '0000-00-00',

email_sent datetime NOT NULL default '0000-00-00 00:00:00',

comments_clie longtext NOT NULL,

comments_serv longtext NOT NULL,

comment_pay longtext NOT NULL,

comment_auction longtext NOT NULL,

comments_inte longtext NOT NULL,

creation_date datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (orders_id),

UNIQUE KEY orders_id_2 (orders_id),

KEY orders_id (orders_id),

KEY orders_shipping_carrier (orders_shipping_carrier)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_orders_shipping`

#

 

# --------------------------------------------------------

 

#

# Table structure for table `spg_payment_type`

#

 

DROP TABLE IF EXISTS spg_payment_type;

CREATE TABLE spg_payment_type (

payment_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

payment_date_added datetime default NULL,

payment_last_modified datetime default NULL,

payment_name varchar(35) default NULL,

payment_title varchar(35) default NULL,

status int(1) default '1',

comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

PRIMARY KEY (payment_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_payment_type`

#

 

<snip>

# --------------------------------------------------------

 

#

# Table structure for table `spg_products_shipping`

#

 

DROP TABLE IF EXISTS spg_products_shipping;

CREATE TABLE spg_products_shipping (

spg_products_id int(11) NOT NULL auto_increment,

orders_id int(11) NOT NULL default '0',

products_id int(11) default '0',

qty_shp int(11) default '0',

products_quantity int(11) default NULL,

qty_back int(11) NOT NULL default '0',

orders_products_id int(11) NOT NULL default '0',

PRIMARY KEY (spg_products_id),

KEY orders_id (orders_id),

KEY products_id (products_id),

KEY orders_products_id (orders_products_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_products_shipping`

#

Soooooooooooooooo... ?

 

Instead of hitting "Submit" I decided, on a lark, to look one last place before posting this reply... the upgrade sql file. This is the first time I've had the self-control to wait before throwing up a reply. LOL!!! :D :D

 

I found the answer. They forgot to stick this in the original SQL file.

This is going to kill the formatting of this thread, I'm sorry, but I wanted to post the solution

for the next hapless sap wandering around the forums at 4:30 a.m. like me. :)

#

# Table structure for table `spg_template_status`

#

 

DROP TABLE IF EXISTS spg_template_status;

CREATE TABLE spg_template_status (

template_status_id int(11) NOT NULL auto_increment,

products_id int(11) NOT NULL default '0',

template_status_date_added datetime default NULL,

template_status_last_modified datetime default NULL,

template_status_name varchar(40) default NULL,

template_status_title varchar(35) default NULL,

template_status_class int(1) NOT NULL default '0',

template_type_url varchar(100) NOT NULL default '',

status int(1) default '1',

comments longtext NOT NULL,

expires_date datetime NOT NULL default '0000-00-00 00:00:00',

date_status_change datetime NOT NULL default '0000-00-00 00:00:00',

template_order tinyint(2) NOT NULL default '0',

PRIMARY KEY (template_status_id)

) TYPE=MyISAM;

 

#

# Dumping data for table `spg_template_status`

#

 

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (1, 0, '2002-12-24 16:46:47', '2002-12-24 16:46:47', 'Admin - Invoice - Payment Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 1);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (2, 0, '2002-12-24 16:47:47', '2002-12-24 16:47:47', 'Admin - Invoice - Order Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 2);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (3, 0, '2002-12-24 16:48:31', '2002-12-24 16:48:31', 'Admin - Invoice - Shipping Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 3);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (17, 0, '2002-12-24 18:48:47', '2002-12-24 18:48:47', 'Catalog - Invoice - Payment Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 17);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (5, 0, '2002-12-24 16:50:16', '2002-12-24 16:50:16', 'Admin - Packing List - Order Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 9);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (6, 0, '2002-12-24 16:51:37', '2002-12-24 16:51:37', 'Admin - Packing List - Payment Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 8);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (8, 0, '2002-12-24 17:15:59', '2002-12-24 17:15:59', 'Admin - Invoice - Thank you Note Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 6);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (7, 0, '2002-12-24 16:56:31', '2002-12-24 16:56:31', 'Admin - Invoice - Comments Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 5);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (9, 0, '2002-12-24 17:19:12', '2002-12-24 17:19:12', 'Admin - Invoice - Special Note Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 7);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (10, 0, '2002-12-24 18:04:05', '2002-12-24 18:04:05', 'Admin - Packing List - Shipping Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 10);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (16, 0, '2002-12-24 18:46:13', '2002-12-24 18:46:13', 'Catalog - History info - Order Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 16);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (12, 0, '2002-12-24 18:06:48', '2002-12-24 18:06:48', 'Admin - Packing List - Comments Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 12);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (13, 0, '2002-12-24 18:07:42', '2002-12-24 18:07:42', 'Admin - Packing List - Thank you Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 13);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (14, 0, '2002-12-24 18:16:33', '2002-12-24 18:16:33', 'Catalog - History info - Payment Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 14);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (15, 0, '2002-12-24 18:25:57', '2002-12-24 18:25:57', 'Catalog - History info - Shipping Block', '', 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 15);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (18, 0, '2002-12-24 18:50:20', '2002-12-24 18:50:20', 'Catalog - Invoice - Shipping Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 18);

INSERT INTO spg_template_status (template_status_id, products_id, template_status_date_added, template_status_last_modified, template_status_name, template_status_title, template_status_class, template_type_url, status, comments, expires_date, date_status_change, template_order) VALUES (19, 0, '2002-12-24 18:51:57', '2002-12-24 18:51:57', 'Catalog - Invoice - Order Block', NULL, 1, '', 1, '', '0000-00-00 00:00:00', '0000-00-00 00:00:00', 19);

 

Toss that in and I believe we'll be happy campers. However I am going to wait until I have some sleep under my belt, so I don't cause total meltdown on accident. :oops: LOL

 

:D Bailey

[Guest]

Well, I got problem #2 fixed, but it's not related to #1.

 

My issue is exactly the same as yours.

 

LMK if you figure it out, I'll keep working on it from here too. ;)

 

:D Bailey

[mugitty]

Bailey, you Night Owl!

 

You're right, #1 and #2 are separate issues.

 

As you indicated in your example, when you update status with 'Notify Customer' checked, the resulting email has the error in it and when you use the email button, it sends a nicely formatted, complete email as per your example.

 

As far as I can tell, this is consistent (at least with my current configuration). The problem is that 1)the 'Customer Notified' indicator is not changed to a green checkmark when you use the email function and 2)any comments that you may have added in the comments section above are not included in the mail sent with the email function.

 

At some point in the distant past, I had received update emails that looked like this:

Farmers Exchange

------------------------------------------------------

Order Number: 12

Detailed Invoice: https://secure14.vosn.net/~farmex/catalog/a...php?order_id=12

Date Ordered: Friday 10 January, 2003

 

The comments for your order are

 

Yout order should ship before the day is over

 

 

 

Your order has been updated to the following status.

 

New status: Processing

 

Please reply to this email if you have any questions.

 

but I think they were from the stock installation before I added this contribution. This is what I'm thinking the message ought to look like when the status is updated and 'Notify Customer' is checked.

 

I am NOT a code genie, but I will take a look and see if I can find why the EMAIL_TEXT_STATUS_UPDATE is not being replaced with the appropriate text.

 

I'll let you know if I find anything :?

[TB]

What are the advancements of 0.5 of 0.4?

I can only find 0.4 in the contiributions... does anyone know where I can get 0.5?

 

Cheers,

Tony

[mugitty]

Tony;

 

v0.5 is here

http://www.oscommerce.com/community/contri...ions,585/page,6

 

Beware, if you are updating from v0.4, there is an sql update file that supposedly has all of the table updates that are needed. In my case, I found that there were still some additional tables in the main sql file that were added (and I thought that I had installed v0.4 just as it had been presented). So, if you start getting some not founds in parts of the admin interface, take a look there for them. (Sorry, I don't remember which ones they were)

[mugitty]

Finally got rid of the $%@#!& "EMAIL_TEXT_STATUS_UPDATE" that was showing up in customer emails instead of something that made sense. (I can't believe that I didn't find this the FIRST time I went looking for a cause :oops: )

 

in admin/includes/languages/english/spg_shipping.php, the define for this string is missing. Add:

define('EMAIL_TEXT_STATUS_UPDATE', 'Your order has been updated to the following status.' . "nn" . 'New status: %s' . "nn" . 'Please reply to this email if you have any questions.' . "n");

and, of course, amend it to read any way you want.

 

This will send a fairly simple straightforward email to the customer advising them of the change in their order's status as long as you check 'Notify Customer' before you click to update status.

 

For a complete update with shipping method, tracking number, etc., the 'Email tracking & Shipping Info" button in the following section seems to serve the purpose.

[Guest]

YOU ROCK!!!!!

 

*hands beer to mugitty*

 

:D

[mugitty]

mugitty wipes beer foam from his face and, in his best Elvis impersonation (which ain't very good), says

 

Thanyooverymuch

[Guest]

Actually

 

this email update was designed to send only the tracking number aznd allo other shipping infos.

 

we never use the intermediate notification (thus we unclick the box: notify customer)

 

 

we do not send an email everytime we change the order status. we only send an email through the email button when package is shipped and we have all info entered.

 

if client wants to see intermediate changes to status he can always login.

 

 

 

but if some people wanted to send an email eveytime the status is changed we will modify the code to have this correct.

 

however be careful not to change 50 emails to a client just to tell him nothing.

 

what a client really want to know ais when order is shipped the tracking number and carrier info ((we think)

but we can do modification

[Guest]

v 0.7 order processing module posted

 

http://www.oscommerce.com/community/contributions,955

 

 

As always send us an email if there is a problem during installation.

HOWEVER do NOT just send us an email to say it does not work !

Give us some clues: OS used, platform used, error message as it appears on screen.

 

 

READ VERY CAREFULLY before upgrading to v0.7.

---------------------------------------------

 

 

v0.7 introduces new tables and process. make sure this process

is what you want to do in your store.

 

 

1. v0.7 of the shipping processing module allows to update very easily price, cost, shipping cost in the order once it is placed

through the admin module.

 

you can now change item cost, price after the order is placed and shipping cost as well.

 

Very useful if you run auctions and final cost is not the one used in your catalog.

you can now very rapdidly enter external orders with the manual entry module in the catalog

and once order is created , modify cost, price, shipping cost to reflect acutal auction or phone order.

 

 

------------------------------------- **** -------------------

at present we do not feel comfortable updating directly the order as placed by a client in the order tables.

 

the core application being still in development by OSC developers. We chose a safe alternative to

record the changes in the order.

 

in other words we record changes in order cost, price, shipping cost in the shipping module tables

and not in the core orders tables.

 

It means that you have a full audit trail between the order originally placed by the client in the core module

and you can view the changes you made during the order processing ONLY in our module.

 

To that extent, if you change order item price, cost, shipping cost , all changes will be recorded in our module

but the original order will stay unchanged in the order tables.

 

it can bring some discrepancies between the 2 modules but it is voluntary. this is why we adapted some existing reports to

reflect all changes made in the shipping processing module.

 

one of the reason to keep the 2 separate is that if for example a client place and order and pays by credit card, a specific

amount will be charged to his credit card.

for any reason if you need to change the order before shipping and our module was updating directly the original order amount ,

you would have a card payment for a certain amount and an order showing another amount.

 

A correct accounting process needs to be implemented in order to keep track of changes but nor erase the transactions.

 

We think the core developers will have to put in place a similar process when they tackle the order processing.(if they plan a module)

but we did not want to modify the core order tables as we do not know what will be the changes made by core developers in cureent months.

 

From our side, we want to keep the transactions intacts.

 

 

However store manager needs to be aware of possible discrepancies between the order module and shipping processing module

if he needs to change order amounts. he will then need to view our reports to have correct amounts.

 

 

 

2. Country table status:

 

-> added a status field in the country table: allows to slect which countries will appear

in the create_account.php. it allows the store manage to limit geograhically who can

order from your catalog. in other words , if you do not want clients located in zimbabwe

to order in your catalog, just set status flag to inactvie in new country admin screen

and this way only preselect countries will appear in drop down box during order process.

 

 

 

3. Reports: we modified 2 very good reports created by other contributors:

 

sales tax report

sales report

 

we only modified a little the scripts in order to run on our shipping tables instead of the core orders tables.

however all the credit goes to the original contributors . we only used their very good scripts in order to run

with our shipping processing module.

[sloughwi]

The 'attributes status' flag is not working, and a few constants are still not defined. I needed to define admin_login.php in the /catalog/includes/languages/english.php. It was only defined in the admin english.php (that very well may have been my own installation error, however).

Also, I have noticed a bug in the last few versions (.7 included). When you first view a pending order, the shipping varable does not grab the product information because $shipping = new shipping($oID) is called before the order information is copied from the default OSCommerce tables into the SPG tables. You can see all the shipping information, but there are no products displayed. As soon as you re-fresh the screen the products appear. Simply moving the line

$shipping = new shipping($oID);

after the if-then statement that follows it. This solves the problem.

 

Other then those things .7 is working nicely. Great mod. :D

[LeeH]

Has anyone encountered this error on SPG v.08? It happens when I try to update an order status from spg_shipping. I think the problem is at line #79 with the orders_status_history_id field which isn't in my spg_order_status table. Don't know whether to manually add the field or take it out of the update query. I've added all the new fixes & sql updates available from the Palms site.

 

1136 - Column count doesn't match value count at row 1

 

insert into orders_status_history (orders_status_history_id , orders_id, orders_status_id , date_added, customer_notified, comments) values ('', '3', '3', '2', now(), '0', '')

 

Thanls much

 

Lee

[edpierre]

Can someone send me by mail the revised version or indicate me where else I can download it, as the 64.255.9.69/oscdownload link is not working

 

 

E Pierre

[email protected]

[updmike]

I dont know if anyone has tried to install .8 or not but I have it reasonable working on my site.

 

The problem occuring for me is that if a customer orders 2 products each with a different attribute the spg_shipping.php and the invoice,reciept pages are pulling up an extra order item in the list although in the spg_shipping table it is listed correctly.

 

ie.

 

Customers orders

 

1 x Item1

-attribute: blue

1 X Item1

-attribute: black

1 x Item2

-attribute:Purple

 

the invoice, shipping page and reciept shows

 

1 x Item1

-attribute: blue

1 x Item1

-attribute: blue

1 X Item1

-attribute: black

1 X Item1

-attribute: black

1 x Item2

-attribute:Purple

 

 

and the shipping table is only showing the 3 items correctly

 

I dont know what to do here, i have been all through the code, does anyone have a fix for this or know of another shipping module that will handle and display Qty Shipped in the reciept I could try?

 

I am willing to try a new contribution all together, this one really has been so full of problems..

 

thanks for any advice/help..

 

Mikey

Edited January 21, 2004 by updmike

[hitman0042]

I installed http://addons.oscommerce.com/info/585 That add on which enables you to create manual orders. I also have the feature edit orders, which is requires for the proper functionality of the create an order add on.

 

It was working perfect for me untill i get this error now.

 

Quote

1146 - Table 'betterte_bto.eorder_text' doesn't exist

 

SELECT * FROM eorder_text where eorder_text_id = '1' and language_id = '1'

 

[TEP STOP]

 

 

Problem is, when i make an order, then click to submit WITH the tick box "New order confirmation:" ticked, i get that error. Otherwise unticked, its fine. But i really need to customer to be notified.

 

How can i fix this??

 

Ive tryed restoring, ive tryed reinstall the add ons. Still no luck?