Hello,
For the site I am developing I had the need to automatically:
 - Add module on page creation
 - Publish certain module on page creation

The modules to be published/added is the same on every page. Just thought I'd share the solution in case someone else needs to do it later on (since you guys have helped me so much).

In admin/PageSettions.aspx.cs. Function SavePageData, after:

bool saved = pageSettings.Save();
pageId = pageSettings.PageId;

I added the following code:

int timeOffset = 2;
DateTime beginDate = DateTime.Parse("2008-06-15 04:00:01").AddHours(-timeOffset);
string end = "";
DateTime endDate = end.Length > 0 ? DateTime.Parse(end).AddHours(-timeOffset) : DateTime.MinValue;

// Publish module
Module.Publish(
pageSettings.PageGuid,
new Guid( "773a46d2-ba3d-4e24-9b72-c5735528ce74"),
17,
pageId,
"leftpane",
0,
beginDate,
endDate);

// Add html module
int moduleDefID = 1;
ModuleDefinition moduleDefinition = new ModuleDefinition(1);

Module m = new Module();
m.SiteId = siteSettings.SiteId;
m.SiteGuid = siteSettings.SiteGuid;
m.ModuleDefId = moduleDefID;
m.FeatureGuid = moduleDefinition.FeatureGuid;
m.Icon = moduleDefinition.Icon;
m.CacheTime = moduleDefinition.DefaultCacheTime;
m.PageId = pageId;
m.ModuleTitle = "Sidansvarig: ";
m.PaneName = "altcontent1";
m.AuthorizedEditRoles = "Admins";
m.CreatedByUserId = SiteUtils.GetCurrentSiteUser().UserId;
m.Save();

int moduleDefID2 = 1;
ModuleDefinition moduleDefinition2 = new ModuleDefinition(1);

Module m2 = new Module();
m2.SiteId = siteSettings.SiteId;
m2.SiteGuid = siteSettings.SiteGuid;
m2.ModuleDefId = moduleDefID2;
m2.FeatureGuid = moduleDefinition2.FeatureGuid;
m2.Icon = moduleDefinition2.Icon;
m2.CacheTime = moduleDefinition2.DefaultCacheTime;
m2.PageId = pageId;
m2.ModuleTitle = "Sidinnehåll";
m2.PaneName = "contentpane";
m2.AuthorizedEditRoles = "Admins";
m2.CreatedByUserId = SiteUtils.GetCurrentSiteUser().UserId;
m2.Save();
 

It's a quite ugly hack, and static too (since module IDs and all that is hard coded (which I don't recommend really)). But it works for my problem on this specific site. If someone need to do something similar to that in the future they can always get inspiration from this code (while I don't recommend you using it straight away).

Regards,

Niklas

You are absolutely right, core changes are usually bad. Probably here as well. The main problem in this project is that it's more focused on time then the perfect solution. I'll try to remake it, but I am not sure if we will have the time.

True. I will give it some thought. Future updates will most likely be handled by us, but it would still be nice to be able to upgrade without breaking things. That way if we need to do a quick update in the future we can do so.