if you instanciate a portal controller, it needs to be populated - or you need to use environment values instead.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

A scheduled task does not have a current HttpContext on which the PortalSettings object (including PortalID) is passed during a normal user request. You will need to include either the PortalID (or ModuleID or TabID from which PortalID can be determined) as part of your data (in a custom database table etc) on which the scheduled task will be operating. Depending on what work you are performing during the execution of the scheduled task you may actually need to construct your own mock HttpContext and create your own PortalSettings instance that is added to this HttpContext's Items collection - not a trivial task.

Try a Google search on "DotNetNuke scheduled task PortalSettings" and you should be able to find some discussion (particularly from Bruce Chapman) on this issue.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner