• 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.

FrontPage extensions: creating _vti_bin?

B

brownlb

Guest
I'm moving an existing website to a new server running Plesk 7.5 for Windows, and it's referencing a file in _vti_bin. That directory doesn't exist when I create the site, and it doesn't get created when I publish the site via FP.
I've tried several iterations of creating the physical hosting to include various services, but none of them add vti_bin.
I'm a complete noob when it comes to FrontPage. Should it create that directory when I publish? Or should Plesk create it? Either way, how to I get it to exist and work?

Thanks!
Blair
 
This is strange...FP WebAdmin works, even though it's going to http://[domain]/_vti_bin....
But the _vti_bin directory is nowhere to be found! No other application can locate it, so how is webadmin working?

Also, I used FP2000 to publish the site to the new server. Is there anything special I should do to accomodate an older version of FP?
 
Back
Top