Hi,

One of my clients hosting contracts ended. I set the expiration date in the host settings, and effectively on the experation date none of the websites webpages are accessible. There is a message:

The hosting contract for [domain name] expired on 31-jul-2011. Please contact [ mail address] for further information.

I wanted to customize this message, but now it seems that their is no possibility to log in to the website anymore.

My question: how can I, as a Superuser, edit the website?

Thanks for your advice,

Anthony

If you can log into another portal on that installation, you can use the language editor to edit that message for every portal. Will that work for you?

Hi Joseph,

I'm affraid this doesn't help me much. Not the fact that I can't edit the 'hosting contract expired' message is the problem, but the fact that I'm not abled to log in at all, even not as a Superuser. All links are redirected to the 'host contract expired' page, even the link to the login page.

Thanks for your help,

Anthony

Is there only one portal in this installation, or are there several. If there are several, you should be able to log into one of the other (not expired) portals and then get the the Host, Portals page.

If there is only one, then your best bet would be to get into the database using SQL Server Management Studio and editing the (I think) portalsettings table to alter the expiration date.

Alternatively, you could locate the .resx file that contains that text and edit it outside of DotNetNuke. Look for:

\App_GlobalResources\SharedResources.resx

According to my knowledge there is only one portal. In the meantime my customer asked me to extend the hosting, so I'll have to delete the expiration date via sql server. Not a good implementation of the expired functionality if you ask me. A user with a host account should always be able to log into the portal, expired or not.

Thanks for the help,

Anthony

This is my short list of "must dos."

0. ALWAYS MAKE A BACKUP before working on a site.
1. Have access to the file directory
2. Have SQL Server Management Studio access to the database
3. Have an alternate superuser account that isn't shared with anyone -- for those times that you MUST be able to get in.
4. Have a second portal to be used ONLY for host access to everything.

Normally, #4 is satisfied by reserving Portal 0 for the host. Then, create another portal for the actual site.

Ok, thanks for the tips. In the meantime I have changed the expiration date in the portals table of the database. Also had to 'touch' the web.config file to reflect the changes.

greetings,

Anthony