If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I've compared the MIVA and the Amazon entries and they match. So what could be the problem? Could it be the WestHost server?
Please try to place and order @ www.netropolus.com and see if you can get past the Shipment screen. If it doesn't work please let me know the next steps
I know you said it worked pre PR7 but can you double check the configuration in your module and compare it to the info at Amazon's Seller Central. That error typically means that the configuration is not correct.
Jim,
I've compared the entries and they match as before in pre-Wombat.
Pls. try to place and order at www.netropolus.com and see if you can get past the shipping screen. If not, pls. let me know as to how to proceed. Could it be the WestHost server? Thanks.
We are experiencing this same issue, but additionally we're seeing time-outs everywhere on our site and in MIVA admin, not just in the checkout. How could this be an Auth.Net issue if it's crashing the product pages on our site?
We usually create a batch, then export it as a flat file, attached to an email to ourselves. It's worked flawlessly on older sites but we created a new store using Wombat and now it is not working. My IT staff here thinks the MIME headers are broken and the email server is dropping the corrupt components, hence no attachment as the file is being generated on the server.
I've compared the entries and they match as before in pre-Wombat.
Pls. try to place and order at www.netropolus.com and see if you can get past the shipping screen. If not, pls. let me know as to how to proceed. Could it be the WestHost server? Thanks.
Jim, Any news of what the problem is with Amazon Checkout in Wombat?
Q: Would it be possible for you to create a database of MIVA sites that have Wombat installed? I think access to those would be a great resource to us, your MIVA customers.
Jim, Any news of what the problem is with Amazon Checkout in Wombat?
Thanks, John
John,
This is the first store I have heard of that had Amazon break like that just from updating to Production Release 7. Have you run all the updates post PR7?
There is always a first-time. My updates are up to data (updated to PR7, then ran the updates to that.)
The point is that it is NOT working, so I really need your help in gettting to the bottom of this. My site is running on a WestHost server, which had a history for having MIVA problems after updating to new releases.
Since the MIVA Amazon values are the same as those of those in my Amazon account, the problem could possibly boil down to server issues.
As a first step, please try to place an order from my site, www.netropolus.com and see if you can get past the Amazon Shipment screen.
There is always a first-time. My updates are up to data (updated to PR7, then ran the updates to that.)
The point is that it is NOT working, so I really need your help in gettting to the bottom of this. My site is running on a WestHost server, which had a history for having MIVA problems after updating to new releases.
Since the MIVA Amazon values are the same as those of those in my Amazon account, the problem could possibly boil down to server issues.
As a first step, please try to place an order from my site, www.netropolus.com and see if you can get past the Amazon Shipment screen.
Thanks,
John
Yes, there is a first time for everything. My point was the update itself did not break it. I'll need to take a closer look. Please email [email protected] and once you get the auto reply with the ticket number please fill out our escalation form.
If you change your store code and log in after having set a custom home page instead of the default, you get a fatal error reflecting the previous store code.
If you change your store code and log in after having set a custom home page instead of the default, you get a fatal error reflecting the previous store code.
We confirmed this bug and the fix will be included in a future bug release.
Comment