fixed it. thank you so much for your help.
downloaded trial version - when I look there is no 3.70 version in zip. that is the nopCommerce version I am running
two days ago, the connector suddenly stopped reading tracking numbers from shipping easy. new orders are added to SE ok, but when I ship, the tracking numbers aren't read back like they used to.
ShippingEasy has a feature to allow me to combine orders into a single shipment. In nopCommerce, the customer placed two separate orders, but I can combine them into a single shipment in ShippingEasy.
When the tracking number is copied back from ShippingEasy to nopCommerce - only one order gets the tracking number updated. The other order does not.
Is there a way for you to catch this scenario from ShippingEasy and update all orders associated with the shipment?
Problem: Sometimes a customer places an order, but enters the wrong address. Either they had a typo or (more commonly) they entered an address that does not accept deliveries from a certain carrier. For example - they enter a PO BOX but the package is being shipped via UPS. When this happens, I contact them and get a corrected address and update the order in nopCommerce. The problem is - this does not update ShippingEasy.com. Even if I use the manual tab you have added to the order page to "send order to ShippingEasy" - it will not update because it sees the order already exists.
Solution: The ideal solution would be to automatically send an update to ShippingEasy anytime an order edit is saved. But as an easy fix - even just having the "Send Order To ShippingEasy" manual option update an existing order on ShippingEasy would be helpful.
OK - I installed the update.
Previously, when I received the error, the task would take some time before throwing the error. Maybe 30 seconds or even a minute.
Now - when I click Run Task Now - it is instantaneous. At first I thought that it was failing right away. But I look at the log file and it appears to be working. The entries in the log file are from today's date so I know they are new entries.
So I think it may be working now. I will monitor it for the next few days to see if it is updating delivery status as it should.
Yes - I still receive the error when I try to manually run the plugin in from the schedule task page.
We're sorry, an internal error occurred.
Our supporting staff has been notified of this error and will address the issue shortly.
We apologize for the inconvenience.
Please try clicking your browsers 'back' button or try reloading the home page.
If you continue to receive this message, please try again in a little while.
Thank you for your patience.
There are no errors in the nopCommerce log.
I left debug mode on for your plugin. I have sent it to you in an email. I have looked at it and do not see any errors.
Of course, reality has just altered itself to work against me. As is often the case.
For the past 2 days I have been able to generate this error at will. As soon as I set up a debug environment to capture data for you - the error goes away. Now, even if I enable "All Stores", I no longer receive the error.
However - I do have a log file that I captured yesterday that I can send to you. When I was still getting the error. I will send this to you and hope that it can shed some light on this problem.
No errors in the log
Plugin installed without error
I can view, make changes and save changes on the plugin configuration screen.
One thing I can think of that might be unusual about my configuration is that I am running multi-store. Originally I configured the plugin for a single store. Just to test it. It appeared to be working. After a few weeks, I decided to activate it for all stores - so I added all the configuration data to the "All Stores" configuration screen.
That is when I decided to run it manually to allow it to detect deliveries from other stores that it had not been detecting before.
Now I have tried enabling my stores one at a time - and the error goes away until I select one specific store. Enabling the plugin for this store causes the error. Disabling it makes the error go away.
Is there something in the store configuration that I can be checking that could cause this?