chrometweaks.org

Has anyone used www.iPage.com and used Website tonight builder?

Click Here To View All Answers...


First question I got is Has anyone used www.iPage.com and used Website tonight builder? Thanks in advance for any answer. My 2nd question... Hi.

I have had the OrderCheck mod added to my iPage site (running MS2) and appear to be having some issues with it. This is a shame as it is badly needed due to payments being made but no order being created !!.

Firstly it appears that all orders, whether completed normally or not, are being held in the order_check section with a red "potential problem" mark. No orders are actually being created in the normal orders section (and I should have had some by now).

Later I have found that the first 5 have changed to a green status. This may be due to order number 1-5 not being in my orders table which now is up to order number 6000 something..

Also, when trying to move the order I get the following message:-.

1062 - Duplicate entry '2753' for key 1.

Insert into orders_status_history (orders_status_history_id, orders_id, orders_status_id, date_added, customer_notified, comments) values ('2753', '2753', '1', '2004-03-15 18:32:47', '0', '').

[TEP STOP].

Does anyone have a fix for this please?? If so please e-mail me as my shop is live and I really need to get this sorted soon..

Thanks.

Derick.

Derick@mrusb.co.uk..

Comments (68)

Good question... I dunno what is the answer to that question. I'll do some research and get back to you if I find an decent answer. You should email the people at iPage as they probably could help you..

Comment #1

Yes me too with ordercheck mod.

1062 - Duplicate entry.

Seems to be submitting the data twice on checkout confirm..

I'm no expert but does'nt duplicate mean twice.

I think it has something to do with these lines, not matching the database.

In checkout_process.php.

// Added 'orders_id' => $insert_id, to the list below.

$sql_data_array = array(.

'orders_id' => $insert_id,.

'customers_id' => $customer_id,.

'customers_name' =>.

So-on.

Have you found a fix.

Has anyone got this new version of ordercheck to work...

Comment #2

From what I can tell ordercheck never bothers to find the max value of the oder_id in the orders table, so when it puts an order in the holding table it just increments from 0 instead of the amount of orders already processed in orders..

When doing a move the code just dumps the contents of the holding tables row into the orders table order_id and all, which if the order_id aldready exists you get the dup error and you are stuck.

This by the way seem to affect the whole process since all the table in holding orders do not stay in sync with the orders tables, if can produce some very strange results especialy if you have attributes on your products..

I am wondering if it might just be easier to dump the holding information into the orders table and then just add a column that is a flag for success, then just put in the check for that flag in a few tables..

Basicaly changeing the order in which the orders table is populated and then just having order_success update the flag instead of putting in the order data...

Comment #3

The problem I have found with ordercheck is threefold,.

Firstly as stated above the ordercheck record is directly dumped into the orders file which results in the duplicate key problem as the move process does not seem to look up the next available number. The duplicate key message refers to the orders_history part which stores the messages. In itself this is not a big problem..

The second problem is that sometimes the order detail is not created so there is an order but no information on what products have been ordered. This is overcome if you do the move again, as the second time a completely new order number is selected..

The third problem appears to be that it does not handle having more than one item on the order..

I wish I could do php programming but my experience is with basic many years ago. This should be on-error loops and next-number lookup so should not be rocket science but my iPage hosting provider (who does the programming for me) does not like the idea of debugging unfamiliar code and making it work. Unfortunately I can't just write a blank cheque to get this sorted..

Just wish I knew why this was happening in the first place as I've only ever had one call-back failure message from Worldpay...

Comment #4

I got some of the errors fixed on ordercheck 1.3.

One problem is that you need to have no orders allready.

Backup your Mysql.

"not recommended for live shop".

Check mysql and clear out the order logs.

In both orders and holding orders.

"Warning - Do not clear orders_status these entries are used for the shop.

They contain pending,processing so on".

Browse threw.

Holding_orders.

Holding_orders_products so on.

And clear the order entries.

Now they should work together without database errors.

But there are still issues that need fixing with this mod..

Comment #5

Corrections.

This process in not recomended for live shops.

Unless you are an expert at matching data in which case you wouldn't have this problem..

Its a quick fix to sync orders and holding orders together in mysql.

Backup your Mysql (allways backup your database).

Check mysql and clear out the order logs.

In both orders and holding orders.

"Warning - Do not clear orders_status these entries are used for the shop.

They contain pending,processing so on".

Browse threw:.

Holding_orders.

Holding_orders_products so on.

And clear the order entries.

Now try making a test order.

The order should appear in admin/ordercheck.

This mod is in need of much work..

If your at this stage and it works for you, we can solve other issues...

Comment #6

Hi.

I have had the OrderCheck mod added to my iPage site (running MS2) and appear to be having some issues with it. This is a shame as it is badly needed due to payments being made but no order being created !!.

Firstly it appears that all orders, whether completed normally or not, are being held in the order_check section with a red "potential problem" mark. No orders are actually being created in the normal orders section (and I should have had some by now).

Later I have found that the first 5 have changed to a green status. This may be due to order number 1-5 not being in my orders table which now is up to order number 6000 something..

Also, when trying to move the order I get the following message:-.

1062 - Duplicate entry '2753' for key 1.

Insert into orders_status_history (orders_status_history_id, orders_id, orders_status_id, date_added, customer_notified, comments) values ('2753', '2753', '1', '2004-03-15 18:32:47', '0', '').

[TEP STOP].

Does anyone have a fix for this please?? If so please e-mail me as my shop is live and I really need to get this sorted soon..

Thanks.

Derick.

Derick@mrusb.co.uk..

Comment #7

Things are worse than I thought..

Below is the error message I got when I placed an order, and obviously all my customers will be getting the same as well..

This problem will be due to an order number 14 already existing on my system..

Any help gratefully received.

Derick.

Derick@mrusb.co.uk.

1062 - Duplicate entry '14' for key 1.

Insert into orders (orders_id, customers_id, customers_name, customers_company, customers_street_address, customers_suburb, customers_city, customers_postcode, customers_state, customers_country, customers_telephone, customers_email_address, customers_address_format_id, delivery_name, delivery_company, delivery_street_address, delivery_suburb, delivery_city, delivery_postcode, delivery_state, delivery_country, delivery_address_format_id, billing_name, billing_company, billing_street_address, billing_suburb, billing_city, billing_postcode, billing_state, billing_country, billing_address_format_id, payment_method, cc_type, cc_owner, cc_number, cc_expires, date_purchased, orders_status, currency, currency_value) values ('14', '2', 'Derick Theobald', '', etc etc.

[TEP STOP]..

Comment #8


This question was taken from a support group/message board and re-posted here so others can learn from it.