All,

I'm setting un a fresh install of DNN 4.5.1 allowing demo portal creation to the users. Everything works fine but the page quota (I've configured a default setting of 5) is not working. I can create a child portal as an anonymous user with no problems but the page quota is not applied. Only when I access as the host user and change the value to a different number it works.

Is it a bug? Anybody else is having this issue?

Thanks in advance.

Oki, done. Issue ID: DNNP-5614

Now, I want to try to fix it because we don't know when it will be fixed. I found out the the problem is caused (at first sight at least) by the "Pages" property of the "PortalSettings" object. In the file "/admin/tabs/ManageTabs.ascx.vb" I found this procedure:

The second line compares the Pages and PageQuota properties. The PageQuota's value is 5 meaning is correct (figured it out in debugging) but the Pages' value is 1 wich is wrong because the total number of pages was six (I created six to ensure it is not responding to the pagequota).

Once I logged in as host and set the PageQuota setting for the portal to 6, the pages property works fine and the comparison works normal showing the warning and disabling the update button.

So, to solve it I need to know where the pages property is modified, and why it is correct once the host updates/changes the pagequota setting.

Any help would be much appreciated.

Private Sub CheckQuota()
      If PortalSettings.Pages < PortalSettings.PageQuota Or UserInfo.IsSuperUser Or PortalSettings.PageQuota = 0 Then
          cmdUpdate.Enabled = True
      Else
          cmdUpdate.Enabled = False
          DotNetNuke.UI.Skins.Skin.AddModuleMessage(Me, Localization.GetString("ExceededQuota", Me.LocalResourceFile),Skins.Controls.ModuleMessage.ModuleMessageType.YellowWarning)
      End If
End Sub