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.
Related
We have magento CE 1.9 which we are trying to get some analytics on and I have seen many posts on the internet about setting up paypal with magento. I believe we have everything setup correctly for paypal standard checkout except for the return URL.
Some of the sources I found on the internet say to use
http://www.storename.com/checkout/onepage/success/
Where others say to use
http://www.storename.com/paypal/standard/success/
which one is actually correct?
An order finally reached analytics via:
http://www.storename.com/paypal/standard/success/
Other orders were completed but did not reach alalytics, I can only speculate on the reason for this. One possible cause I have read about, is premature closing of the browser window. This could prevent our sites success page from loading the analytics javascript.
I recently started to have the following error when trying to proceed a paypal payment on my magento store:
Cannot retrieve payment method instance.
I have read about it on various websites, and it seems to happened when you create/modify a payment method. However, in my case, it really started happening with no reason at all, as I have not made any changes to my website recently.
I have tried to manually force paypal_standard as method in the sales_flat_order_payment and sales_flat_quote_payment tables, but it did not work.
Paypal express checkout doesn't work anymore neither.
Does anyone have an idea of how to reinstall/reset or something the paypal payment module?
Or to further debug the issue?
(I am not a programmer so I would need quite detailed information)
For anyone having this issue, I have solved it by deleting the /app/code/core folder and replacing it with a vanilla magento one. Most likely the paypal payement system module got corrupted for no reason and replacing it with vanilla version solved the problem.
I am trying to figure out why the tinyMCE WYSIWYG editor in the CMS module of Magento will not upload images. I can create/delete folders but any file will simply not get uploaded, and there seems to be no message as to why the file is not successfully written on the server.
Anyone may have an idea why?
** Update **
I'm using Magento 1.6.2. I have tried to track down the problem and it seems that the controller never gets executed. I have added a line to log the arguments in the uploadAction() action (in Mage_Adminhtml_Cms_Wysiwyg_ImagesController) and nothing gets logged.
This is project inherited from someone else, and was modified to some extend, but nothing seems to point out that this part of Magento would have been touched in anyway by the modifications.
** EDIT**
The project associated with this question has been dropped and I no longer can provide an answer to this question. If anyone can confirm a working answer (as this problem was apparantly common with Magento), I will gladly mark that answer as "accepted".
Otherwise, I will flag this question for removal for the aformentioned reasons.
Thank you.
Other than solutions provided here, it may occur when you use a CDN (or a different domain) for your javascript and media files in admin panel. If you use CDN, use it for your website(s) scope and use your own domain for default scope. It will make your website(s) media and javascript files to be loaded from CDN, and backend's media and javascript files to be loaded from your own domain. This will solve your problem.
There are some known issues with flash image uploader on Magento. Unfortunately when it falls, it falls silently. Here are some cases when smth can break it:
if you try to use it with secured connection using open ssl certificate
if you're using it on server with apache authentication
on some Magento versions with prototype 1.7
I think the latter is your best bet. Maybe you should try to apply the patch from here: http://www.magentocommerce.com/boards/viewthread/4348/P45/#t327010
In my case it was a cross domain problem, and one quite hard to find if you ask me...
What was puzzling me was that the uploader for product images was working like a charm but the one in the CMS section was failing completely silently. We are serving the skin folder from an Amazon S3 bucket, and the flash uploader lives under that folder.
Interestingly enough, our version of Magento (1.7.0.2) is using two different methods to calculate the path to the SWF file, depending whether you are under CMS or Product update.
The CMS file (app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml) is using the following method to embed the Flash Uploader:
<?php echo $this->getSkinUrl('media/uploader.swf') ?>
While the Product image uploader is using:
<?php echo $this->getUploaderUrl('media/uploader.swf') ?>
In our case, the first one resolves to the AWS S3 url, obviously in a separate domain, while the second one will still reference the local domain's url.
So yeah, the quick, dirty fix would be to replace getSkinUrl for getUploaderUrl in app/design/adminhtml/default/default/template/cms/browser/content/uploader.phtml. Alternatively you can extend the core to load a different template in which you would have replaced that method.
I hope this helps somebody... I wish I had found something like this five days ago when I first stumbled upon the issue :-)
Are you using flash uploader with https? If so, is your secure address in differente domain (usually used in shareds ssl)?
I got some trouble with this. I solved by installing a flash uploader disabler plugin.
You can download the plugin with this downloader key:
http://connect20.magentocommerce.com/community/Dull_Uploader
I hope it helps.
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