Date: Sat, 13 Apr 2002 18:23:12 -0400 (EDT) From: jim <jim@jwweeks.com> To: G D McKee <freebsd@gdmckee.com> Cc: Joe & Fhe Barbish <barbish@a1poweruser.com>, FBSDQ <questions@FreeBSD.ORG> Subject: Re: Apache/1.3.23 PHP/4.1.2 FrontPage/5.0D Message-ID: <Pine.BSF.4.21.0204131817430.1070-100000@veager.jwweeks.com> In-Reply-To: <00a501c1e32c$a9319670$c800a8c0@p1000>
next in thread | previous in thread | raw e-mail | index | archive | help
My problem wasn't in compiling the ports, and I have similar out put as what you have below. My installation even works (to the point of creating subwebs through FrontPage Explorer), and that's where it ends. Have you tried logging in to a frontpage enabled site and creating a subweb? Regards, -- Jim Weeks On Sat, 13 Apr 2002, G D McKee wrote: > Hi > > I have got the three ports compiled fine on my machine and with php4 in as > well. > > Here is the proof!! > > [Sat Apr 13 15:24:50 2002] [notice] Apache/1.3.23 (Unix) mod_ssl/2.8.7 > OpenSSL/0 .9.6a FrontPage/5.0.2.2623 PHP/4.1.2 configured -- resuming normal > operations > [Sat Apr 13 15:24:50 2002] [notice] suEXEC mechanism enabled (wrapper: > /usr/local/sbin/suexec) > > It is rather tricky and I had to use apxs to compile in the FrontPage > extensions. The main problem is file permissions. Once I got so far > FrontPage generates a log file called /var/log/httpd-fpexec.log. This makes > life a bit easier. One other thing - after a failed login from FrontPage - > you need to restart FrontPage before it will properly try again to access > the server. fpexec is also installed in the wrong place be default - you > need to copy it in to /usr/local/apachebin and set the permissions to 4550. > > I also have a very vague set of instruction I made out in Word as I went. > > It took me a few months of trying one and off!! Trust this help!! > > Gordon > > ----- Original Message ----- > From: "Joe & Fhe Barbish" <barbish@a1poweruser.com> > To: "jim" <jim@jwweeks.com> > Cc: "FBSDQ" <questions@FreeBSD.ORG> > Sent: Monday, March 11, 2002 2:28 PM > Subject: RE: Apache/1.3.23 PHP/4.1.2 FrontPage/5.0D > > > > I was at your position in January and after spending 3 weeks writing > emails > > to the maintainers of mod_frontpage and frontpage about how since > > mod_frontpage was changed in January that the two ports no longer worked > > together and not getting any kind of reply from then I gave up on the > > apache13 + mod_frontpage + frontpage combination, removing them from my > > system and started over with apache13-fp. This one installed and works for > > me. It has just one simple conf error. Two files are defined in the > > httpd.conf file but not allocated and cause apache not to start. > > /usr/local/etc/apache/mine.types > > /usr/local/etc/apache/magic > > Those files are really installed as part of the port, but they have the > word > > default appended to the end of the files name. Edit httpd.conf and about > 3/4 > > of the way into httpd.conf you will find these files. Edit there names to > > mine.types.default & magic.default and restart apache13-fp and it will > work. > > You can tell if the frontpage extensions are active by doing ps ax , you > > will see httpd -DMOD_FP. > > > > The bottom line is mod_frontpage is broken and the only way to get it > fixed > > is to email the maintainer and write a FBSD Problem Report. The more > people > > who complain the better, so jump in and do your part. > > > > Scot W. Hetzel [hetzels@westbend.net] maintainer for frontpage port > > Martin Blapp [mb@imp.ch] maintainer for mod_frontpage port > > http://www.freebsd.org/send-pr.html submit problem report > > > > > > Good luck > > > > > > > > > > > > -----Original Message----- > > From: jim [mailto:jim@jwweeks.com] > > Sent: Monday, March 11, 2002 3:07 AM > > To: Joe & Fhe Barbish > > Cc: freebsd-isp@freebsd.org > > Subject: RE: Apache/1.3.23 PHP/4.1.2 FrontPage/5.0D > > > > Thanks Joe, > > > > I had in fact missed the "FrontPageAdminEnable" directive, I thought it > was > > only necessary when enabling http administration. This did allow me to > > create sub-webs, however the Explorer errors out during the final > > update. I'm not sure where to go from here since no errors are written to > > the server logs. This is the error FrontPage explorer displays: > > > > An unexpected Web Extender error occurred on the server. Authors -please > > contact the webmaster for this server's site. WebMasters - please see the > > server's logs for more details. > > > > Without seeing something in the way of errors from the server itself, I'm > > not sure how to proceed. > > > > -- > > Jim Weeks > > > > > > On Sun, 10 Mar 2002, Joe & Fhe Barbish wrote: > > > > > #/usr/local/sbin/apachectl start This is apache13 port > > > > > > /usr/local/etc/rc.d/apache.sh start This is apache13-fp port > > > > > > > > > Here is the contents of a email I responded to some one else's request > for > > > help date 2/14/202. > > > > > > > > > Yep you just got bit by the FBSD min standards. Don't they just suck. > Here > > > is a update I submitted to the maintainer of the mod_frontpage 2 weeks > ago > > > and have not received any response. If this works for you then let > martin > > > the port maintainer know. > > > > > > Martin > > > How about changing pkg-message to this > > > > > > > > > **************************************************************************** > > > ******** > > > > > > mod_frontpage is now a APXS installation wrapper for frontpage on > > Apache13. > > > This port is to be installed after the apache13 port is installed. > > > One of the language specific xx-frontpage ports must be installed to > > > complete the apache/frontpage environment. See FreeBSD web site for > > details. > > > > > > http://www.freebsd.org/cgi/ports.cgi?query=frontpage&stype=all&release=4.5-R > > > ELEASE%2Fi386 > > > The English version of the port does not adhere to the above naming > > > convention, > > > use port named frontpage for the English version. > > > > > > After apache13 & mod_frontpage & frontpage install is completed you must > > > check your > > > /usr/local/etc/apache/httpd.conf file and make the following manual > > changes. > > > > > > The ResourceConfig and AccessConfig are commented out. Replace them with > > > > > > ResourceConfig /dev/null > > > AccessConfig /dev/null > > > > > > > > > You'll also need to change AllowOverride None to AllowOverride all > > > Under <Directory "/usr/local/www/data"> or add > > > > > > AllowOverride AuthConfig Limit Indexes Options > > > > > > There are new key words to turn on/off the frontpage extensions and the > > > frontpage administration web site for apache web site defined in > > httpd.conf. > > > > > > FrontPageEnable activates the basic frontpage extensions which enables > the > > > Microsoft windows frontpage client to publish website content to the > > > apache/frontpage server. > > > > > > FrontPageAdminEnable activates the frontpage web site administration > pages > > > which allows the fpadmin person to use a set of predefined admin pages > to > > > add, delete, and change the frontpage declaratives in the httpf.conf > file > > > from a browser. > > > > > > Any combination of the key words can be used in the httpd.conf file > > > to refine the control of any web site defined in the httpf.conf file. > > > > > > FrontPageEnable # Enable Frontpage Extensions ms/fp > client > > publish > > > FrontPageDisable # Disable Frontpage Extensions ms/fp client > > publish > > > FrontPageAdminEnable # Enable Frontpage Extensions Admin web site > > > FrontPageAdminDisable # Disable Frontpage Extensions Admin web site > > > > > > You should add FrontPageEnable & FrontPageAdminEnable each on a separate > > > line > > > right after the dso modules list in the httpd.conf file as part of the > > your > > > initial changes. > > > > > > If no key word options are present in the httpd.conf file the default of > > > FrontPageDisable and FrontPageAdminDisable is used resulting in a > working > > > Apache environment where the complete frontpage environment is disabled. > > > > > > After you have made these changes, you'll have to execute: > > > > > > /usr/local/frontpage/version5.0/fp_install.sh to build the base > > > apache/frontpage web site and assign the frontpage administrators ID/PW. > > > You can also run this to add virtual hosts to the apache/frontpage > system. > > > > > > You must use /usr/local/etc/rc.d/apache.sh script to manually start > or > > > stop > > > the apache/frontpage server. FBSD boot will start apache ok as it uses > > this > > > script. > > > > > > /usr/local/etc/rc.d/apache.sh start > > > /usr/local/etc/rc.d/apache.sh stop > > > > > > See /var/log/httpd-error.log for error messages. > > > > > > 2/15/2002 This has been tested on FBSD 4.4 & 4.5. This will not work on > > > apache2. > > > > > > **************************************************************************** > > > ******** > > > > > > > > > -----Original Message----- > > > From: owner-freebsd-questions@FreeBSD.ORG > > > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of G D McKee > > > Sent: Sunday, February 24, 2002 12:09 PM > > > To: Freebsd-Questions@Freebsd. Org (E-mail) > > > Subject: FrontPage 2020 Port Problems!! > > > > > > Hi > > > > > > I have got the apache13-modssl port compiled and install and working - > > then > > > I installed mod_php4 and it is fine. The I want FrontPage 2002 server > > > extensions so I have installed the mod_FrontPage port and the FrontPage > > > port. > > > > > > When I HUP httpd I get the following: > > > > > > [Sun Feb 24 10:10:56 2002] [notice] Apache/1.3.23 (Unix) mod_ssl/2.8.6 > > > OpenSSL/0.9.6a FrontPage/5.0.2.2623 PHP/4.1.1 configured -- resuming > > normal > > > operations > > > [Sun Feb 24 10:10:56 2002] [notice] Accept mutex: flock (Default: flock) > > > > > > So from this I figures I was pretty close to getting it to work. > > > > > > Then I went through the /usr/local/FrontPage/version5.0/fp_install.sh > and > > > configured the default web server and a virtual server. FrontPage on > the > > > other hand will not pick up and files from the web server and just error > > > saying The folder may be located in an unavailable location, protected > > with > > > a password, or the filename contains a / or\. > > > > > > I have a look at the server logs for a server with 2000 extensions on it > > and > > > the web server gets the same request. The line look as follow - on the > > 2000 > > > server: > > > > > > 192.168.0.1 - - [24/Feb/2002:10:16:52 +0000] "OPTIONS / HTTP/1.0" 200 - > > "-" > > > "Microsoft Data Access Internet Publishing Provider Protocol Discovery" > > > 192.168.0.1 - - [24/Feb/2002:10:16:52 +0000] "GET /_vti_inf.html > HTTP/1.0" > > > 200 1716 "-" "Mozilla/2.0 (compatible; MS FrontPage 5.0)" > > > 192.168.0.1 - - [24/Feb/2002:10:16:53 +0000] "POST > > > /_vti_bin/shtml.exe/_vti_rpc HTTP/1.0" 200 228 "-" "MSFrontPage/5.0" > > > 192.168.0.1 - - [24/Feb/2002:10:16:53 +0000] "POST > > > /_vti_bin/_vti_aut/author.exe HTTP/1.0" 401 471 "-" "MSFrontPage/5.0" > > > > > > > > > and on the 2002 server that doesn't work: > > > > > > 192.168.0.1 - - [24/Feb/2002:10:12:47 +0000] "GET /_vti_inf.html > HTTP/1.0" > > > 200 1754 "-" "Mozilla/2.0 (compatible; MS FrontPage 5.0)" > > > 192.168.0.1 - - [24/Feb/2002:10:12:47 +0000] "POST > > > /_vti_bin/shtml.exe/_vti_rpc HTTP/1.0" 200 139 "-" "MSFrontPage/5.0" > > > 192.168.0.1 - - [24/Feb/2002:10:12:47 +0000] "OPTIONS / HTTP/1.0" 200 - > > "-" > > > "Microsoft Data Access Internet Publishing Provider Protocol Discovery" > > > > > > > > > I have had a look on both servers and neither server has any of these > > > author.exe or shtml.exe files in the places the logs say. There is no > > info > > > in the error log either. > > > > > > I also read I needed the following lines in the httpd.conf file > > > > > > #FrontPageEnable On # Enable FrontPage Extensions > > > #FrontPageDisable # Disable FrontPage Extensions > > > #FrontPageAdminEnable On # Enable FrontPage Extensions fpadmcgi.exe > > > #FrontPageAdminDisable # Disable FrontPage Extensions fpadmcgi.exe > > > > > > but ever time I use them, apache comes up with syntax errors. > > > > > > Does anyone have any ideas? > > > > > > Thanks in advance > > > > > > Gordon > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > -----Original Message----- > > > From: jim [mailto:jim@jwweeks.com] > > > Sent: Sunday, March 10, 2002 5:53 PM > > > To: Joe & Fhe Barbish > > > Cc: freebsd-isp@freebsd.org > > > Subject: RE: Apache/1.3.23 PHP/4.1.2 FrontPage/5.0D > > > > > > Thanks Joe, > > > > > > This is probably correct, but I am confused. Does the apache-fp port > > > install a different /usr/local/sbin/apachectl? I don't see any thing in > > > there for starting frontpage. I actually made apache13-modssl, > mod_php4, > > > mod_frontpage, then installed fp50.freebsd.tar.Z. I poked around and > > > didn't find apache-fp.sh any where. I guess I could make apache-fp just > > to > > > get a copy and check out apachectl. > > > > > > -- > > > Jim Weeks > > > > > > > > > On Sun, 10 Mar 2002, Joe & Fhe Barbish wrote: > > > > > > > Sounds like you are using the wrong script to start apache. Do not use > > the > > > > apache script use the apache-fp script and every thing will fall into > > > place > > > > and work like you want. If you started with apache13-fp port and added > > you > > > > other software, then you have it all. If you did apache13 port you > have > > to > > > > do 2 other ports to get frontpage installed. Apache13 + mod_frontpage > + > > > > frontpage. > > > > > > > > -----Original Message----- > > > > From: owner-freebsd-isp@FreeBSD.ORG > > > [mailto:owner-freebsd-isp@FreeBSD.ORG]On > > > > Behalf Of jim > > > > Sent: Sunday, March 10, 2002 9:47 AM > > > > To: freebsd-isp@freebsd.org > > > > Subject: Apache/1.3.23 PHP/4.1.2 FrontPage/5.0D > > > > > > > > Greetings, > > > > > > > > This is the first time I have tried building apache and adding the > > > > FrontPage module from ports. Everything seems to have gone well, and > I > > am > > > > able to connect and publish to virtual webs with no problem. The > > problems > > > > begin when trying to create subwebs through FrontPage Explorer. This > > > > effort ends in an error that the server doesn't support the Post > > > > method. I have looked through the archives and search engines to no > > > > avail. I have "AllowOverride All" set in httpd.conf, and the > .htaccess > > > > files are identical to the ones used when frontpage was used as a DSO. > > I > > > > know I must be missing something simple. Any point in the right > > > > direction would be appreciated. > > > > > > > > Regards, > > > > > > > > -- > > > > Jim Weeks > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-isp" in the body of the message > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0204131817430.1070-100000>