jnull

How different is this from Live View that Dick mentioned earlier? <{POST_SNAPBACK}> I don't use Dreamweaver as my primary tool... so I could not answer that question for you in comparisoin. SOKKIT basicly creates a PHP enabled web server on your local computer, where you can then place your PHP pages and run as if they were on a web server, per se.

Visit http://www.jimcoaddins.com/addins.aspx where you can get some great web developer tools for FrontPage users that are free, easy to use, and add some great functionality to FrontPage. In particular I use the spam stopper resource.

I use PHP w/ Frontpage on several of my clients sites. To use PHP w/ FrontPage you need to have "front of mind" that PHP is server side, rather than client side. You will not see the results of the PHP code till you put it on a server that has PHP installed. Or you can download SOKKIT (30 day free trial) and place it on your computer, and put your test PHP files in that domain and run them there before uploading them to your server. In a nutshell, you just won't see the results of your PHP in the development side of using FrontPage, only after you have it published to your web server will you see it. All of your PHP code within Frontpage needs to be parsed to PHP, otherwise have <?php and ?> around the PHP code.

Rather than installing apache, etc., you can also download for a 30 day trial, and then purchase for about $20 SOKKIT. This gives you space on your local computer to run PHP code to test prior to uploading to your web server.

Ditto Steve's post ...

You need to go into Frontpage in your editor preferences and set those to open a .php in Frontpage. Dreamweaver will work just like Frontpage... you gotta tell it to specifically open the file.

Yes and no. You can open a php file in Frontpage, but you will only be able to see it in code view if the entire file is PHP code. If the PHP is in and out of standard HTML then you will be able to see some of the html code in design view. Generally, you need to setup Frontpage to open a PHP file in Frontpage by setting your editor preferences, otherwise, it will open in whatever text editor program you have associated to the .php extension. Frontpage 2003 is much more stable in working with php coded files than 2002. 2002 has a great tendency to do what it wants w/ php code. I am not aware of a really good wysiwyg php editor. The nature of php is that it is run at the server, not within the browser itself or on the client -- thus the limitation of having a wysiwyg php solution to develop in -- today.

I haven't tried it... but I don't know of anyway within Frontpage you can do it. But you can do it with Javascript. Search on line for "javascript form validation" and you should see some example, from there, if you know a little bit of javascript, you should be able to smith a validation routine.

Yes, specifics would help, and I concur, you can use FP with PHP. You do need to double-check the PHP as sometimes some PHP code FP thinks is something else. Best thing to do is put your PHP in plain text html not using FrontPage, such as notepad, saving the file as a *.php file. Import into your web and run it to make sure your PHP is working right, before placing it into a FrontPage page or web.

Much appreciation ... hadn't thought about either of those. Was looking only in the backup menu option to do it.

I always attempt to consider PayPal and their shopping cart features before using something that I need to purchase, code or even get an SSL for. Check them out ... think you'll be amazed.

When I've created a full backup. and have it downloaded... how do I delete that from Control Panel so that it is not using up storage space on my server?

Photo Gallery - I use SPGM, as found at: http://spgm.sourceforge.net/, it is absolutely excellent, the fella who wrote it supports, it is free, but I am so impressed with it that I did send him some US dinero. I use this on about six sites now.

What is the URL of the non-working form page?

Another question regarding the cpanel backup relatvie to a FrontPage site. FrontPage allows you to enable chid-webs (subwebs) with different rights for browing and publishing. The rights are such that you require a username/password combination in order for someone to browse the site. Do you know if a restore from a cpanel backup also restores the FrontPage child webs with their original rights settings?

Hi ... I am looking for a way to take a paper form, create it on a web page, and when submitted, have it returned to me as a form. EXAMPLE: The IRS 1040EZ form, I want that exact form on a web page where I can fill in the information, and then click SUBMIT, and I receive that form in an email completely filled out. Any suggestions where to go to get a tool like this?

Ditto from Texas!

I have had wonderful results with: Dell eMachines (now owned by Gateway) Sony WinBook Acer I have had bad results with Compaq I have had mediocre results with HP

Rob's post, Dec 21 2004, 03:24 PM, is the right approach. There is so much bashing of folks because of preferences, dislikes of companies and people or dislikes of companies who are successful, on and on. In another year, or less, it'll all change again anyway. Find what works for you and work with what you found! Thanx Rob, for setting it straight!

Merry Christmas to all as we celebrate the meaning of CHRISTmas!

I waited about a year before upgrading from FP 2002 to 2003. I finally decided to do so because of the split view where you can see the code along with the wysiwyg view at the same time. Because of this feature alone I felt it was worth the extra cost because it saves me substantial time in tweaking sites. If you are only doing your own personal site ... it's probably not worth the money. But if you do many sites with FrontPage, which is my case, I've found it well worth the upgrade.

Check out this link ... it might help: http://www.reducedcomplexity.com/scripts/u..._class/?lang=en

Raul, thank you for your offer. But using "some trick" to make Firefox work is just what I'm trying to avoid. I attempt to code websites to satisfy the 90% of site visitors, thus IE and Netscape, today. If that changes then I would move in that same direction because of the need of my clients to be able to provide access to this factor of web surfers. If it takes a special fix to satisfy one of those browsers in the lower 10%, well... that's a road I just don't feel it's prudent to go down. I'm content to accept that I can't satisfy 100% of all browsers with coding, fixes, tricks or otherwise, and that coding to the 90% is the best solution for the site owners, and for the coder. Thank you again for your offer, but it is one that is best for me to pass on. :rolleye Thumbs Up

Though in the cases I mentioned there is nothing wrong with the code, it is truly the browser, Firefox in this case. One thing I've learned in working with the Internet and computers in general, is that errors do abound, only because these things are created by imperfect people. If people weren't imperfect, than everything we make would always be perfect, even browsers of preference. Thanx for your two-cents, Raul, the dialogue is much appreciated.

I use IE, Netscape 7+ and Firefox, and do prefer to use them in that order. Firefox just didn't render all pages I develop as they were developed. IE and Netscape did.