RE: [PHP-DB] Renaming .htm pages to .php
At 01:42 AM 8/4/2003 -0400, Dennis Cole wrote: Also, You would be best off changing only the one you thing you might need to use PHP later with, changing Apache to phase all .htm pages can get really slow is a insect comes about. I'll probably use server side includes for footers and other elements on all pages, so I might go ahead and change all the extensions to .php. But you're referring to Plan B - leaving the .htm extensions and just modifying Apache to treat them as .php extensions, right? -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Renaming .htm pages to .php
At 05:58 PM 8/3/2003 -0600, David Smith wrote: This doesn't have much to do with PHP and databases, but here's a thought: You can leave them all .htm and have apache treat .htm files as .php files. Just check out httpd.conf for configuration. If your box is sufficiently zippy, you will see now slow down by running pure html files through PHP. So if I understand you correctly, I can turn a page into a .php page through one of two methods: 1. Change the extension to .php 2. Instruct Apache to treat .htm extensions as .php extensions. That sounds really interesting. Would that create any problems with pages that I never use .php functions on? Or if I have websites on my computer that don't use php? Thanks. -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Renaming all pages to .php
At 02:19 PM 6/20/2003 +0200, Thorsten Körner wrote: This will run, and I think almost without problems. But IMHO it makes no sense. And I don't know, if all the searchengines out there will be able or willing to read *.php files (google works fine). Are you saying that some search engines might not register pages with php extensions? That would be a MAJOR problem. You should know that renaming all that files is not all, you have to do. you have also to change every single link in your pages, that points to your pages. I don't know how large your project is, but it can be much work, and if you do not add lines of PHP-Code to that pages, you can save much time by not doing so. Hm... it would be nice if I could use a search and replace function, but that would be tricky. If I replaced every instance of .htm with .php, then that would also change links to other websites. For example... a href=htttp://www.50states.com/history.htm would become a href=http://www.50states.com/history.php; I wonder if there's an advanced search and replace technique that would target only internal links on my website. On the other hand, I am doing an extensive overhaul that will require recoding on every single page, so maybe I could just manually change the links as well. Thanks for the tips. The comment about the search engines is especially interesting (or alarming). I'll have to give this some more thought if .php links might affect my site's visibility in search engines. Do you know if the same applies to .asp and ColdFusion? BTW. It is not a good idea to start a new thread by replying to an old one. I wasn't aware that I did. -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DB] Renaming all pages to .php
I joined this list a few weeks ago because I wanted to learn about php. Unfortunately, I still haven't found time to study it in any depth. Thus, my question might be a bit amateurish, but it's fairly urgent, so I'd appreciate any feedback anyone cares to offer. I'm working on a new website that I need to get online by the end of this month. I had wanted to do some stuff with php on it, but there's no way I can learn php and apply it before the July 1 deadline. No problem - I'll just add the php later. The catch is that my pages will be registered in search engines with URLs ending in .htm, something I'll have to address when I switch to php. Then I saw a discussion on another forum about a guy who was planning on changing all the .htm extensions on his webpages to .php, whether those pages use php or not. The general consensus was that that the pages would work just fine even without php, and they'd be all set up if and when he got around to adding php. I'd like to get some feedback from this forum. Do you agree that a page without php functions or server side includes can be put online with either a .htm or .php function? If I never add a php function to a page with a .php extension, could that cause some kind of problems? Also, I'm thinking of naming all my pages index and sticking them inside folders. That way, visitors can reach a page by typing in www.geobop.com/birds/ , whether the full URL is www.geobop.com/birds/index.htm or www.geobop.com/birds/index.php Is this a good plan, or do you see any problems? Thanks! -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
Re: [PHP-DB] Renaming all pages to .php
At 09:16 PM 6/19/2003 -0500, Joshua Stein wrote: it won't cause any problems. you'll have the very small overhead of having to run every static page through php's parser, but if you're going to have php in these pages in the future it doesn't really matter. Also, I'm thinking of naming all my pages index and sticking them inside folders. again, no problems. just make sure your web server is setup to search for index.php as a directory index page. I don't know exactly what you mean, but I just renamed one of my pages (using Dreamweaver) with a .php extension, previewed it in Mozilla, and it worked fine. This is the address displayed in the browser: file:///C:/sites/geosymbols/birds.php However, when I pasted the URL into Internet Explorer. So I linked to the page from page X, previewed page X in IE and clicked the link and was taken to C:\sites\geosymbols\waldman.php That's weird. I never even realized my two browsers displayed localhost links differently - file:///c versus C:, and forward slashes versus back slashes. But I assume that means my server is set up properly. As long as I can preview my pages, I can't complain! * * * * * * * * * * Doug Thompson: You or your company better get busy and hire a competent programmer to complete your project in the alloted time; or you might consider posting to a list of a more general nature and see if anyone there wants to do your work for no pay. So you're saying I should get php installed and running on my pages before I change the extensions? I wouldn't ask anyone to my work for no pay; I have more than 300 pages on my site, and it's a fairly complex project. * * * * * * * * * * Mike Brum: You can easily add the .php extension to any .htm(l) page that you have with no worries as long as you have PHP installed and configured properly. The only problem is that page load will be SLIGHTLY slower since PHP will search all .php pages for PHP code to evaluate. Upon finding none, it will simply return the HTML to the requester. But note that this is a tiny bit longer than your web server just serving the page without passing it through PHP. Naming all files index.XXX will be a good idea. Though realize that some people might link directly to the file itself (which can sometimes become visible with different browsers and different activities). But none-the-less, it will work for most users if they do decide to bookmark the folder. Alright, it sounds like a go. Thanks for all the tips. -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
[PHP-DB] New Member
Hi, this is my first post on this list. I've never used PHP, but I'm interested in exploring it, along with MySQL and Apache server software. Very briefly, my main focus is on designing webpages. I've been unemployed for several months and have been using my extra time to learn new computer skills, primarily Dreamweaver and Cascading Style Sheets. I'm working with Windows XP, but I'd like to get away from Windows eventually. I got Linux installed on my computer a couple months ago, but I haven't found time to learn it yet. Then I apparently forgot part of my password, so I'm locked out! So I'm going to stick with the Windows platform for now. I started downloading MySQL just today, when one of your members recommended I join this list. He also recommended Apache, so I checked it out and discovered that you can download pre-configured packages of PHP, MySQL and Apache at http://www.hotscripts.com/PHP/Software_and_Servers/Installation_Kits/ So here are my first questions: 1. Which package should I download - the first one (Firepages phpdev)? 2. Since this is all new to me, I don't want to do anything that will somehow screw up my other software. I don't really understand servers and would like to ask if installing Apache will give me two servers, or will it replace IIS? I just want to make sure I can continue previewing my webpages and was concerned that I might somehow screw things up if I install Apache wrong. Eventually, it would probably be nice to have Apache software up and running on a Linux platform and use IIS on the Microsoft platform when necessary. Finally, here's an example of my immediate goal, which I understand would involve MySQL and PHP: http://www.geobop.com/marini/2.htm I want to create really nice, interactive tables featuring information on the world's nations and animals. I posted the questions on this page to a Dreamweaver group, but they indicate where I'm headed. Thanks! -- PHP Database Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
