Hi Jan,

Administrators can manage the newsletter. If you need to delegate this to non admins you can add that role "Newsletter Administrators". You are right that it should be created automatically. I will fix that for the next release.

Thanks,

Joe

Hi An,

I'm not sure I understand. As far as I know I built the Newsletter feature so that it already is site specific. Each site defines its own Newsletters, they are not shared acrosss sites, or at least it is my intention that they are not.

Best,

Joe

Hi An,

I understand now. It would be possible to implement this for "most" features, by using a site specific prefix for the settings in <appSettings related to smtp, kind of like I did for commerce settings as indicated in this article. All the custom mojoportal features use these smtp settings from the appSettings section of Web.config, but built in ASP.NET features use the settings from the system.net/mailsettings section:

<system.net>
<mailSettings>
<smtp from="noreply@yourdomain.com">
<network
host="localhost"
port="25"
password=""
userName=""
/>
</smtp>
</mailSettings>
</system.net>

The only feature I know of where this will be used in mojoportal is the password recovery feature because that uses the built in ASP.NET password recovery control, so maybe its not a problem there.

If you want to implement an SmtpConfig.cs similar to what I did for commerce in Web/Components/CommerceConfig.cs, that would make it possible to hide this complexity of config settings from other places in the code. I could implement this myself in an hour or less I think, but if you want to tackle it that would be great. If not, let me know and I'll see what I can do.

Best,

Joe

Hi An,

I'm not opposed to the idea but it would need to be implemented for all 5 data layers before it could be included in mojoportal. I suggested the config approach because its easier to implement, but I understand what you're getting at, the config approach becomes unwieldy if you are setting up lots of sites. I think it would also be important to encrypt those settings in the db.

The thing for me about the multi sites feature is (at least if using multi sites by hostname), its a very limited solution if you have important sites, they should be separated, because as soon as you need SSL for one of the sites it needs to be separated because only 1 SSL certificate can be bound to port 443 on a given ip address. So I tend to favor the easier config approach because I really don't see it as a great idea to run a bunch of important sites from a singler instalation, though I know some people do it, I don't do that myslef. Maybe in folder based sites I can see it because they all have the same host name and can use the same SSL certificate.

In any case, as I said, I'm not opposed to a db solution, the problem is we can't just do it for one db, it has to be implemented for all of them at once because its a core feature. So its a good bit more work. But maybe if you want to implement the MS SQL version I can get ot the others, but I'm pretty busy with other initiatives.

Best,

Joe

Yeah, the Newsletter feature still needs a few more things. I implemented the Delete button this morning so it will be in the next release of mojoPortal, coming soon.

Best,

Joe