Skip to content

header image support for paypal express #54

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 5 commits into from
Closed

header image support for paypal express #54

wants to merge 5 commits into from

Conversation

pincombe
Copy link

Hi not sure if my approach is correct but would it be ok to add header image support for paypal express? It is used instead of the business name at the top of the page and can really help customers feel secure and understand the current stage in the payment process. A great implementation of it is on Etsy.com

Please let me know if you don't agree but I would really like the ability to set the header image. Its widely used in ecommerce sites  which use PayPal Express an example would be Etsy.com
@amacneil
Copy link
Member

Thanks, this looks good. Before I can commit, can you

  • fix whitespace so the travis build passes
  • add comments to describe what format the headerImage should be (e.g. does it need to be an HTTPS URL?)
  • squash everything into a single commit (then force push to github and it will update the pull request)

@amacneil
Copy link
Member

Also can you add this to the gateway settings, some people might like to set it globally. Thanks!

@pincombe
Copy link
Author

Ok sure :)

Thanks for the feedback. I'm not very experienced with open
source contribution but i'll sort these issues out and send another request
shortly.

On 29 April 2013 13:26, Adrian Macneil notifications@github.com wrote:

Also can you add this to the gateway settings, some people might like to
set it globally. Thanks!


Reply to this email directly or view it on GitHubhttps://github.com//pull/54#issuecomment-17163688
.

@amacneil
Copy link
Member

No problem. You can just push to your github branch and it will update the pull request :)

@pincombe
Copy link
Author

Hi. I messed up my forked repo so started a new one. I think these changes
are much better than the last ones I made anyway :)

On 29 April 2013 13:35, Adrian Macneil notifications@github.com wrote:

No problem. You can just push to your github branch and it will update the
pull request :)


Reply to this email directly or view it on GitHubhttps://github.com//pull/54#issuecomment-17164040
.

@cfreear cfreear mentioned this pull request May 1, 2013
@amacneil amacneil closed this May 2, 2013
barryvdh pushed a commit that referenced this pull request Feb 13, 2016
Ensure that makedoc.sh works with ApiGen 4.1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants