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

Move Email Settings onto Content Node #1

Closed
warrenbuckley opened this issue Aug 2, 2013 · 3 comments
Closed

Move Email Settings onto Content Node #1

warrenbuckley opened this issue Aug 2, 2013 · 3 comments
Assignees
Milestone

Comments

@warrenbuckley
Copy link
Owner

Rather than the email settings be hard coded in the email helper class or even be in the smtp section of the web.config allow user to define directly on homenode as some kind of global setting for all emails perhaps?

@ghost ghost assigned warrenbuckley Aug 2, 2013
@justinspradlin
Copy link

I think storing them as a new tab on the home page document type would be a good idea. That way if you ran multiple home page nodes with different domain names, you could have different settings for each "site". However, the helper would need to know which "site" it was running on to determine the smtp settings. That way the contact form from site1.com/contact would use the site1.com specific settings while site2.com/contact would use the site2.com node's settings.

@warrenbuckley
Copy link
Owner Author

This has been resolved with latest commit.

@justinspradlin this would be something you would have to extend yourself at this current time when you have the source code downloaded so you can tweak it to your own needs.

@justinspradlin
Copy link

That sounds great to me! Thanks!

On Tue, Aug 6, 2013 at 11:07 AM, Warren Buckley notifications@github.comwrote:

This has been resolved with latest commit.

@justinspradlin https://github.com/justinspradlin this would be
something you would have to extend yourself at this current time when you
have the source code downloaded so you can tweak it to your own needs.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-22190561
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants