Skip to content
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

Make imageURL configureable in backend #1

Open
23tux opened this issue Feb 21, 2013 · 2 comments
Open

Make imageURL configureable in backend #1

23tux opened this issue Feb 21, 2013 · 2 comments

Comments

@23tux
Copy link

23tux commented Feb 21, 2013

Hi,

I just found your repo, and it's really cool. But I'm missing (some) features, like configuring the imageURL in the backend. Or is there any other way to configure the url?

@clemens
Copy link
Owner

clemens commented Feb 21, 2013

Thanks for the positive feedback. :)

When writing this, I needed it for a project so I've extracted it as an extension but I've only implemented what was needed for the project – imageURL wasn't one of these things.

I'm not sure where I want to go with further settings – some might be suitable for the admin preferences but others probably aren't (e.g. you might want to use the asset pipeline for your imageURL). Until I've figured that out, the easiest way for you would be to just override the view file and customize it according to your needs. This can be done the same way as with all other Spree extensions and Spree itself by just placing a file with the same name in the same path – in this case app/views/spree/checkout/wirecard_qpay_payment_page.html.erb (or html.haml if you want to use HAML). You can start by copying the contents of the original file and adapting whatever you need.

I'll keep this issue open in case I make my mind up regarding what configuration goes where.

@23tux
Copy link
Author

23tux commented Feb 21, 2013

cool, I'll have a look at it, thx!

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

No branches or pull requests

2 participants