Publishing to a FTP server does not need the FP SE,
But opening a live web and working on it in FP client does need the FP SE
| Doesn't the FP publishing tool require the server extensions?
|
| I take your point about .htaccess, however its use - or the way it is used -
| does limit my ability to perform a perfectly legitamate (and commonly
| performed) server-side task.
|
| I found that, when the URL filter was added to .htaccess, I couldn't
| "Publish to web" nor open the website in FP from the server - a feature that
| I specifically wanted to use.
|
| I'm not concerned about losing integrated FP runtime features as the site
| uses PHP anyway, but the ability to publish only changes up and down, to
| synchronise links for easy updates and amendments and to edit the live site
| within front page and publish back to home.
|
| Is there a solution?
|
| | > FYI
| > FP does not use .htaccess
| > Only the FP SE use .htaccess
| > (because that's what controls access permissions on Unix servers)
| > If you don't use the FP SE, FP won't touch .htaccess
| > - use Pearl or PHP for the run time "features" you lose from the FP SE
| >
| > And the implementation of the FP SE is done by RTR
| > - so you may find more help w/ your issue at
| >
http://www.rtr.com/fpsupport/index.asp
| >
| > FP2003 FTP control is significantly improved
| > Try it online at
| >
http://www.runaware.com/microsoft/frontpage2003/
| >
| > _____________________________________________
| > SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
| > "Warning - Using the F1 Key will not break anything!" (-;
| > To find the best Newsgroup for FrontPage support see:
| >
http://www.net-sites.com/sitebuilder/newsgroups.asp
| > _____________________________________________
| >
| >
| | > | Hey Ron,
| > |
| > | Had no problem editing it for other functionality and have placed all
| new
| > | content after the FP rules, it's when the rewrite rule is inserted that
| > | things go pear-shaped. Since last night a friend has done some further
| > | research. He read other people have exactly the same problem: inserting
| a
| > | rewrite rule into .htaccess on a FrontPage site causes trouble, but we
| > | cannot find a solution - either an alternative rewrite method or a cure.
| > |
| > | What I - and others - don't understand is WHY ON EARTH FP uses the file
| name
| > | .htaccess. From what I can see the file's functionality doesn't require
| this
| > | specific name - using an essential and commonly-required Apache file
| name
| > | such as .htaccess simply serves to hinder more advanced server-side
| control.
| > | If FP is to be considered a serious developers tool to compete with the
| > | likes of Dreamweaver, surely issues like this only serve to undermine
| that
| > | drive?
| > |
| > | Sorry to say that I'm fast losing patience with FP - I know that rants
| are
| > | common and this is not abusive: I have used FP happily for several
| years,
| > | however as my skills improve and I want more advanced functionality, so
| I
| > | find FP more of a hindrance than a benefit. I know others have pointed
| out
| > | that 2003 is much cleaner, but I heard this when upgrading to 2k and XP
| and
| > | still my code is bloated.
| > |
| > | Does 2003 still use .htaccess to control publishing, for instance? If
| yes,
| > | WHY???
| > |
| > | By the way Ron, your help with that table thing has proved invaluable as
| FP
| > | insists on inserting border-collapse:collapse over and over again. I've
| been
| > | into Tables>Insert Table>Style and find border:collapse:collapse
| permanently
| > | under "description" and cannot see where to remove the option
(
| > |
| > | Sorry, rant over - if anyone can provide a solution to this problem it
| will
| > | be gratefully received!
| > |
| > |
| > | | > | > I have successfully edited the .htaccess file (despite dire warnings
| from
| > | my
| > | > host).
| > | >
| > | > How did you edit the file? FTP download - edit - FTP upload?
| > | > If using FTP the file MUST be moved as an ASCII (text) file, FTP
| programs
| > | > will usually move these files as binaries, which will corrupt them on
| Unix
| > | > servers.
| > | >
| > | > HTH
| > | > --
| > | > Ron
| > | >
| > | > Reply only to group - all emails will be deleted unread.
| > | >
| > | >
| > | > | > | > > Can anyone help with an irritating problem.
| > | > >
| > | > > When I enable FP extensions for a domain on a server, a file called
| > | > > .htaccess is created which, as I understand it, is essential for FP
| > | > > functionality.
| > | > >
| > | > > I wish to insert an Apache rewrite rule which I know to be good:
| > | > >
| > | > > RewriteEngine on
| > | > > RewriteRule programmes/progtemp2/([0-9]+)
| programmes/progtemp2.php?p=$1
| > | > >
| > | > > This is inserted immediately below the FP generated code.
| > | > >
| > | > > However when this is added, FP extensions fail to work and I cannot
| open
| > | > the
| > | > > site in FP nor publish to it using FP.
| > | > >
| > | > > Why is this and how can I ensure that modifications to this file can
| be
| > | > made
| > | > > without upsetting FP?
| > | > >
| > | > > Thanks.
| > | > >
| > | > >
| > | >
| > | >
| > |
| > |
| >
| >
|
|
