NetTalk Central

Author Topic: Multi site host maintenance message  (Read 933 times)

TimR

  • Newbie
  • *
  • Posts: 33
    • View Profile
Multi site host maintenance message
« on: December 23, 2025, 05:30:50 PM »
I would like to be able to have a message warning users that maintenance (updates) will be performed at a certain date/time. I have it working for a single site using <!-- Net:f:update.htm -->It is just a banner that displays in the header, when maintenance is pending.

I would like to be able move this file to my c:\host\web directory instead of the c:\host\site\web directory so I only have to change it in one place, instead of each website web folder.  I tried setting it to <!-- Net:f:c:\host\web\update.htm --> but that didn't work. Can I do this?

rjolda

  • Sr. Member
  • ****
  • Posts: 431
    • View Profile
    • Email
Re: Multi site host maintenance message
« Reply #1 on: January 07, 2026, 05:17:06 PM »
HI Tim,
I don't know much about multisite hosts but I think that each site gets compiled as a dll and my understanding is that the "host" will always be available even when one site's dll is down for maintenance. Therefore, I would think that you would want to notify only the site to get the update and not have it as a general message. 
How are you going to deal with updates?  How are you going to handle users that are already logged into your site when you want to do maintenance?
Ron

TimR

  • Newbie
  • *
  • Posts: 33
    • View Profile
Re: Multi site host maintenance message
« Reply #2 on: January 08, 2026, 03:42:39 PM »
You are correct, however, I have multiple sites for different clients, using the same dlls, but with different web folders (for customization), I'm trying to avoid having to update a bunch of different files saying when "maintenance" is going to happen and just update one file instead. I could write a script to update/un update, but then I'd have to make sure new clients get added to this script, I have enough points of failure, don't need to add more if I can avoid it. Updates are generally pretty quick and at odd hours, to avoid users. I've also had the rare time where I would like to update asap, but I don't have a good mechanism to prevent users logging in or encourage them to give me 5 minutes for the update.