• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

CentOS 5, PSA 8.2 & Frontpage ... oh my!

M

madcat

Guest
Hello. We have Plesk 8.2 setup on a CentOS 5. I am hoping it is possible to convince it to support Frontpage. Upon searching this forum, I have come across a few threads suggesting that all we need to do is install the RPM for Frontpage from Plesk 8.0. The latest CentOS that Plesk 8.0 supports is 4.2. When I install that RPM on CentOS 5 and restart Apache, I get this message:

httpd: Syntax error on line 206 of /etc/httpd/conf/httpd.conf: Cannot load /usr/lib/httpd/modules/mod_frontpage.so into server: /usr/lib/httpd/modules/mod_frontpage.so: undefined symbol: apr_filename_of_pathname

Anybody know what I need to do to get it to work? Is there a CentOS 5 compatible RPM? Would any system changes make it work. I have tried running 'ldconfig -v' but no luck with that.

Thanks.
 
I believe mod_frontpage is incompatible with apache 2.2.3 which is the version that comes with CentOS 5 and Plesk 8.2.
I have not had luck getting it to work. If anyone else has a solution please chime in.
 
Moving on from Frontpage is the solution. No longer supported by Microsoft as of 2006 and produced junk code anyway. Might be time to redesign the site in Dreamweaver.
 
Back
Top