we have a problem with our magento shop before going live. We do not exaclty know when did this one happen. We want to offer digital goods (pictures) as download links from external host.
Everything worked fine - we did not test the checkout for a month.
Now we have a problem, if customer buys a digital good, his download link for his picture does not work. It is empty. The hashkey in the DB seems ok. In Backend the purchase is being triggered. We suppose the connection between the hashkey and the external url is wrong.
We did 2 things since that but already applied a rollback. We installed SSL sertificate and a delete old orders extension. Can one of these things cause our problem?
Thank you a lot for any hint.
Best regards
Dimitri Petrik
Related
I've posted this question on magento.stackexchange.com but got no response due to lower traffic there than here... So here it is...
I'm working on a website for a client and right before publishing the
website, I noticed that all the products went out of stock itself. So
I put them all back in stock and everything looked fine, but when I
checked back after a few hours all the products were back out of
stock.
I tried a few times to re-enter the stock quantities, re-index and
clear the cache, but I'm still having this weird issue - everything
looks fine until like 2-3 hours later everything goes out of stock.
Any suggestion what could be causing this issue?
Thanks in advance!
PS. I didn't share the code because I would have to share the code of the entire website...
Any suggestion what could be causing this issue?
Any imaginable 3rd party application or module that has access to cataloginventory model or its tables in database.
Suggestion how to debug this:
put this snippet into inventory observer
app/code/core/Mage/CatalogInventory/Model/Observer.php
somewhere at the begin of saveInventoryData method. (Or create local module and observe a save event)
Mage::log(Varien_Debug::backtrace(true, true), null, 'inventory.log');
after you reproduce the behaviour just check the log file under <doc root>/var/log/inventory.log
I am setting up a megento shop but while testing I get the following error when paying by card using ebizmarts Sage Pay module:
Payment has failed, please reload checkout page and try again. Your card has not been charged.
Does anyone know the solution to this problem?
Regards,
Daniel
There is a support forum for the free plugin here http://ebizmarts.com/forums and if you are using the PRO module, you can just use the contact form here http://ebizmarts.com/contact-us
Also, the problem you mention is described on the Wiki here http://wiki.ebizmarts.com/sage-pay-common-problems
FIXED
From what I can see and for whatever reason, Magento was loading the "info.phtml" file from the theme/default/checkout/onepage/review folder, rather than the one in the sagepaysuite folder.
I copied in the above code to the relevant position to the default info.html file, and it's working now.
The staging server was loading the sagepaysuite/checkout/review/info.phtml file correctly, hence it was working.
Every order placed from the frontend of our Magento store logs a "Wrong order ID" exception even though all orders seem to be going through with no problems. Orders also seem to take a lot longer to complete than they should. If I place an order from the admin, it's virtually instantaneous and does not log any errors. What's different between frontend and backend orders? Why are these errors being logged every time even though no error really occurred? Any suggestions?
Thanks!
Per the change log for Magento 1.7.0.0 (which came out in April), they think they've fixed the problem:
Fixed: “Wrong order ID” exception in PayPal Express module under heavy load
Can anyone confirm that upgrading to Magento 1.7 does indeed fix the problem? Every time I've looked at it, it does seem to be a PayPal Express issue (our payments normally go through PayPal Pro and that doesn't seem to have errors).
So... we finally found a permanent solution to this for Magento 1.6. And we can confirm that this has been fixed in Magento 1.7.
Full explanation and code here:
Magento Paypal IPN Wrong Order ID – SOLVED
We had this same exception in Magento 1.6.1 showing up in exception.log. The problem for us was that the Order Number and Invoice Numbers were out of sync.
For some reason, when using PayPal Express, it causes the order to not be fully processed and logs the exception: “Wrong Order ID”. The worst part was that it was erratic… sometimes it would fail, other times it was fine.
THE SOLUTION:
http://www.magentocommerce.com/magento-connect/fooman-sameorderinvoicenumber.html
Thanks for a great extension from Fooman! Just install their “SameOrderInvoiceNumber” extension, remember to enable it in “Configuration | Sales | Order Numbers” and you’re all set!
Solved the problem for us on Magento 1.6.1… don’t mess with core code!
Ok... So my other solution didn't soIve the problem for us either. Spoke too soon. Although this helped it didn't get rid of the error completely.
We did however find a definite clear link between server load and this IPN error. Detailed analysis here:
http://www.bigdune.net/geek-blog/magento/60-magento-paypal-ipn-wrong-order-id.html
Sorry, but it doesn't seem like there's a quick "code fix" for this one.. not that we could find yet.
I have a problem with debugging a thing (not a real error) in Magento (CE 1.4.1.1).
For a payment module I've adapted, some additional payment fee is incorporated and is showing up on selection of the particular payment method. Works fine, no problems.
A client has the OneStepCheckout plugin installed. Inside it, the payment method works fine too (small problem: payment fee is showing up after the grand total, but that's not the issue, just for completeness of my question).
So, everything is working fine, even with some other payment modules installed. That is, working fine on dev and test! On the live server however, the extra fee does not show up! I've locally installed the other plugins that are installed on the live server as well, to see if there are any conflicts among them. None whatsoever. The Extension Conflict extension does not indicate any class overwriting problems either. Of course, I've cleared the cache. Several times.
So my question is a rather general one:
How to proceed?
What can I do and how to actually see what's going on and NOT break the live environment ? As far as I know, there is no staging server (there is a test server, but also there no error...), so I'm bound to the live environment.
Is there a common practice to handle these kind of issues? (And if so, what is it?)
I know of the MAGE_IS_DEVELOPER_MODE, system log, exception log etc, but since on dev everything works fine, I seem to not be able to really debug a bug which does not show up... can I safely switch on the logging on a live site by the way?
Thank you all in advance!
Regards,
Tom
You can create your own log to see what is happening in Magento
Mage::log($datayouwanttosee, null, 'yourlogfile.log');
This will not break anything but will show you anything you want from that file. Once you load the page 'yourlogfile.log' will be in Magento's /var/log directory with the other log files.
Also make sure to turn your logging off when you are done otherwise the log could consume a lot of disk space.
You have better results if you contact OneStepCheckout support directly with this issue. Also verify that you ar using the latest version of OneStepCheckout
Totals however have sort ordering and this is available in Magento admin under system > configuration > sales > sales > Checkout Totals Sort Order
I have installed full release Magento on localhost from http://www.magentocommerce.com/download. Before doing installation I have created a database and import Magento sample database (downloaded from Magento site).
After that continue installation process. When I checked fronted its shows Best Selling Products when I clicked any of the product it gives error given below:
Whoops, our bad...
The page you requested was not found, and we have a fine guess why.
* If you typed the URL directly, please make sure the spelling is correct.
* If you clicked on a link to get here, the link is outdated.
What can you do?
Have no fear, help is near! There are many ways you can get back on track with Magento Demo Store.
* Go back to the previous page.
* Use the search bar at the top of the page to search for your products.
* Follow these links to get you back on track!
Store Home
My Account
I am new to Magento.
I've experienced this too. In the admin go to System > Index Management and rebuild the various catalog indexes, especially the URL rewrites.
This is because the sample data doesn't have it's paths stored to begin with, it needs to be calculated, and the Best Selling Products section doesn't read the actual paths in use, instead it is a Static CMS Block with it's HREFs fixed. This will probably never occur for products you enter yourself so it's nothing to worry about.
I had the same problem in Wamp. I had my folder named Magento, renaming it to magento, fixed the problem. (Lower case)
I had a similar issue, I was transferring Magento from a Unix server to a Windows server. My issue was to do with links looking like this (not working)
http://www.magentoshop.com.au/shop/product01.html
instead of
http://www.magentoshop.com.au/shop/index.php/product01.html
Haven't worked out how to fix all links yet, but just adding it tells me where the issue lies. Hope it helps someone else.