so I am trying to set up django-oscar-paypal with django-oscar. So, everything works fine, the paypal express checkout page shows correctly, then it redirects back to the store and when i click the place order button, it redirects to an empty basket, with no transaction being recorded in the dashboard, except for the express dashboard, which shows success. My guess is there is a session loss, or I need to edit the checkout view somehow for it to post the request, but i can't find anywhere on how to do that, and copying the one from the sandbox isn't helpful. If anybody managed to make it work I would be very grateful for help.
Related
An order confirmation email is sent for canceled/failed payments
User reach to the payment gateway, when reached to the cart after selecting final and reach to the payment page and user cancel the order but a successful email sent to the user did somebody face this issue before my open cart version 3.0
didn`t check the code yet, please tell me,
2) My website home page icons change into some encrypted boxes whenever some body visit my website first time later on user go in and visit some other pages and revisit the website home page, icons looks fine ,i refer so many links, even try to make changes in .htaccess file as well but nothing works,is there any way that i can fix it,i am providing my website site link,if you want because this issue never comes on local server,enter image description here,enter image description here
First thing that comes to mind is the order states options (system -> settings -> options). What state do the orders get when a payment is cancelled? Is the state unchecked for the 'order ready' states in the options?
This mainly depends on payment extension. Payment extension is responsible of setting correct order_status_id depending from 'error', 'failed', 'not completed' methods.
Sometimes, payment module has incorrect return callback links.
Again, check payment module methods.
Im trying to configure django-stripe-payments to work properly. I'm using the following along with it:
pinax-project-account(https://github.com/pinax/pinax-project-account)
bootstrap-ajax (https://github.com/eldarion/bootstrap-ajax)
The trouble is that django-stripe-payments is not showing me my information in the template, such as my payment history or if my subscription is active even though it is.
Stripe is indeed picking up the payments and customer creations.
Has anyone got it working who can offer me some advice?
I understand this question is vague, I just don't know where the problem is.
Image of the the problem
You need to setup webhooks:
In Stripe dashboard go to Your Account and then Webhooks
Add a URL to a publicly reachable URL that is where you are testing (if running local dev runserver, I have found localtunnel to be immensely useful)
Now when you make purchases you should see the data show up within seconds.
django-stripe-payments is designed around processing events data sent from webhooks.
I am working with our web developer to integrate Facebook Likes (with comments) onto our website. However, he is having problems because FB doesn't work very well with sites where a log in is required. Currently when you click on the 'like' button the 'like' turns into 'confirm'. You then have to click on 'confirm' and another box appears showing how the like will appear on your FB page saying 'Click Like to post this to your profile' with the option of 'like' or cancel. If you click on 'like' then it allows the comment box to pop up then you can add a comment and post to FB.
There are currently too many clicks for this to work. Does anyone have any advice? Would it be better to just use straight likes with the number perhaps or is this a common problem with website that require a login. We just want users to be able to click once, add their comment and post it to FB.
Any help would be really apprecaited. If it is technical that is fine as I will pass replies onto my developer.
Many thanks
This will generally happen for URLs and sites that are new to the Facebook scraper. It is a security measure to prevent like-jacking that some sites have done in the past. You should ensure that you test your site fully with the Debug tool and after some confirmed 'likes', that step will be automatically removed and future users will just have to click like once.
Where you are gating content behind a login, I would additionally recommend that you show different HTML (including OG tags) for anything detected with the Facebook scraper User Agent (see When does Facebook scrape my page? on the Like Button FAQ) so that, for example, the OG tags for a product detail page are picked up correctly even though the scraper is technically not logged in.
I've added a facebook Like button to a few of my web site pages. All of them work except for the home page and I can't figure out why?
It is almost impossible to answer this question without seeing some sample code of your "home page".
Check your page with https://developers.facebook.com/tools/debug
If the response code isn't 200 or your meta tags don't appear properly or whatever else, at least you'll know where to look. Keep in mind that when you click like, Facebook makes a request to your page. Make sure you let Facebook do that (don't block/Redirect the Facebook crawler).
Edit: Sometimes, simply adding your URL and testing on the link above solves the problem. This is if you had a problem with the site when you first added it and meanwhile Facebook cached it as problematic. Debugging it will clear the Facebook cache for that URL.
I am in the process of implementing Google Checkout in an e-store. Once customers click the 'Google Checkout' button, my project requires that they are able to navigate back to the e-store to possibly edit the cart. Customers should be able to click the 'back' button, type in the URL to my cart page, or click the 'edit' link from Google.
At the same time, I need to clear the cart and provide customers with a blank slate as soon as they click the confirmation button on Google's side. I am already listening for a new-order-notification from Google, but this does not always arrive quickly enough to prevent customers from returning to the e-store and scratching theirs heads as to why their carts still show the items they just purchased.
Have any Google Checkout implementors come up with a novel solution to this problem? Any ideas are appreciated!
I've done this using 2 different approaches, neither properly fulfils your requirement of handling the back button AND clearing the basket if they complete the order, but they've worked for me in practice without any complaints.
First approach: clear the basket and provide way of reconstructing it via query string in the "EditCartUrl" Google Checkout request parameter. Then, when the customer clicks the edit basket button their basket is reconstructed. The back button, however, does not work in this situation.
Second approach: don't clear the basket, but (optionally) make it read-only before redirecting to Google Checkout. We do this so that the basket record cannot be changed while they are within Google Checkout. If they then click back, or edit cart, a NEW basket is created on our site (cloned from the original) each time. This provides support for the back button, but will only provide the customer with a cleared basket if the order has gone through and we have processed the request before they return to the site.
Making the basket read-only is optional - we do it so we can preserve the basket record to match the resulting order from Google Checkout. If you don't require this, it's as simple as not clearing the basket.
The second approach has done me fine for the last few years without any complaints from customers. I'd rather the customer be able to click the back button than worry too much about them seeing the basket not empty itself after checking out using Google.