New public_html folder broke symbolic links?

[sduquette]

In early May I setup a user domain using the symbolic link option so I could put both http & https pages in the same directory. All https: forms were functioning properly & data submitted was transmitted securely.

A few days ago I added a new user domain & now none of the secure forms that were working (on my other users domain) - will function anymore. These same forms work fine using http & do transmit the data (unsecurely), but will not work using https now.

I've been reading in this forum where the public_html & symbolic link works fine until a new user domain is added. The adding of the public_html in the user directory did affect other languages & there was a work-around. Is there a work-around for this using FP?

Using Apache 1.3.41 with FP extensions.

FYI - the FP extensions were all functioning perfectly using both http & https before I added a new user & domain (before the public_html DA update).

What can I do to make the symbolic link - link to the https pages the way it used to?

 

[nobaloney]

In one post you wrote that symbolic links break FrontPage Extensions; in this post you ask to enable them.

You've got me so confused that I deleted my response to the other post and I'm not even going to try to respond to this one. Please do not double post. Please do not post confusing double posts .

Front Page Extensions are unfortunately no longer supported by anyone, and Microsoft has rescinded their license for you to use them (as were their right).

While I'm NOT saying they've done anything to Front Page Extensions on your server, or anyone elses server, or that they even could, I think it a bit unusual that Front Page Extensions seem to be failing for many of our clients though they've worked properly before.

Jeff