• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Plesk 12.5 upgrade with MS FrontPage extensions

galaxy

Regular Pleskian
So I'm working through testing of migrating my plesk 12.0 install to 12.5.30.
In the check it mentions I'm missing the "frontpage" apache module.
I have more than a dozen FrontPage sites that need to be migrated.

What do I do to make the migration work (at least for the frontpage portion of the problem...)
 
Well that presents a problem...
I don't mind manually handling the current installations, but I can't lose it altogether...
 
OK, found sources for frontpage extensions, compiled/installed on centos 7. We'll see if it works after migration. Looks good though.

I know that they stated it wasn't supported anymore, but they said they wouldn't remove the capability to use is when I spoke with support about it a year ago.
I don't really care if its in the panel, as long as I can keep the legacy sites alive.

Thanks.

How do I mark thread as resolved?
 
Back
Top