As it is, the page that covers installing using cpanel is not linked: http://codex.wordpress.org/cPanel_X This page - does it also need modifying for when IIS information is ready ? and when I've done a xampp guide ? So do we need a page that has the overview then links to the different ways ? I'm not sure and I don't quite know where to edit. --Podz 05:58, 16 Dec 2004 (GMT)
Hey, I think the "deleting files" thing was only added once... by me. Sorry.
--NuclearMoose 06:51, 1 Aug 2004 (UTC): I was thinking that the installation page should be just that; troubleshooting suggestions should go on a separate page or pages as necessary. There is no sense in combining two topics on one page.
Well, there's been discussion of this on the mailing list... the consensus seemed to be that given the TOC features in mediawiki it made sense to combine things like this into one page... so installation and troubleshooting installation problems (not to mention other issues) could conceivably be one page with sections....
--NuclearMoose 10:22, 1 Aug 2004 (UTC): I don't disagree that the tool has great capabilities for doing TOCs, but if you look at any kind of guide, let's say instructions for setting up a home theatre, the installation is separate from troubleshooting, just as setting the clock and other menu options is separate as well. It makes no sense to be on the forums and tell someone to go to the install page to find an answer to an error message. That said, I'm open to be convinced otherwise! :)
--ChrisL 01:25, 2 Aug 2004 (UTC): Depends on what you look at. My MP3 software guide, which happens to be next to me has installation instructions followed by troubleshooting information (specific to installation) and a glossary. You wouldn't point someone to "the install page" in any case-- since Media Wiki is kind enough to have a good TOC and section anchors, you point them to the troubleshooting section of the install guide (which seems to me a logical place to look for solutions to problems with installing :) In my opinion, anywhere that one has a link, it should be carefully considered whether or not there is really a need for a separate page or if it is really a section of the same material. In this case, the other fruitful approach would be to have a stand-alone troubleshooting guide and link from the installation guide to the relevant section. What I would hate to see is an unneeded multiplicity of pages
--skippy 02:44, 2 Aug 2004 (UTC): I concur with ChrisL: installation-specific troubleshooting should be on the installation page. Then, a seperate "Troubleshooting" page can consist of links to troublshooting-specific sections on topical pages.
--NuclearMoose 03:46, 2 Aug 2004 (UTC) Well, I'm not convinced. The strength of the TOC is PRECISELY why things should be separated out. Having pages of links is wrong, too. Why have a TOC to send them to a Troubleshooting section which has a link to the Installation section? That makes no sense at all. What of the people who don't experience troubles during installation? They may feel the need to skim the whole page to look for something that they think they might miss, hidden in the rest of the page. The pages should be lean and mean, and totally specific, otherwise you wind up with issues of "degrees of content." Do you also put the database troubleshooting in the installation section? But, majority rules. If you want to combine topics, then so be it.
--NuclearMoose 05:05, 2 Aug 2004 (UTC): Just reading some MediaWiki docs, and it seems that the "standard" way of adding comments is to do the sig/timestamp FIRST then add your comment. Seems like a good idea to adopt these good wiki habits.
--ChrisL 06:42, 3 Aug 2004 (UTC): I'm not married to anything, but I will note that being "lean and mean, and totally specific" is a goal I agree with, and not one limited to any single kind of organization. Every style becomes a combination of topics in some way. As I read it, you want all troubleshooting instructions to be in the same place, combining many different kinds of troubleshooting. Whereas I like the idea of having specific kinds of troubleshooting immediately available while performing that activity (with the side benefit that one can print that section and hopefully have everything they need). But I can see it either way. Is there some method of automated inclusio available in this wiki software? I.e. would it be possible to include a few top issues in a short troubleshooting section, addressing the most common topic specific items and then direct them to the relevant section of a stand-alone troubleshooting section (without incurring too much maintenance overhead)?
skippy 20:04, 3 Aug 2004 (UTC): I think perhaps we're speaking past one another. The auto-generated TOCs are done on a per-page basis, and only when there are four or more sub-sections defined. If there are no sub-sections to the Installation page, then there's no TOC on that page. Here's how I see it:
Does that make sense? Given the variety (and potential compelexity) of troubleshooting tips, I think there's specific value to keeping them with their subject matter.
--NuclearMoose 00:01, 26 Aug 2004 (UTC) We now have Italian and French versions of the instructions. However, both sets are on external sites. Would it not be prudent to have these efforts at least mirrored on the wiki itself? If those sites ever go bye-bye, then we have a dead link and we will have to wait for someone else to create a new set of instructions.
--TigerDE2 11:43, 26 Aug 2004 (MESZ) The German translation is underway. However, we have choosen to have our own Wiki: http://Doku.WordPress.de
Sorry for not knowing about MediaWikis features (using signature etc.) but since we decided to move there I thought I'd never need it and stopped reading this wikis docs... :)
--NuclearMoose 11:55, 26 Aug 2004 (UTC) Christian, that site looks very good. I'll add the link here to the localization section. I'd just like to point out, too, that in the interest of branding a product, you should stick to the blue (#003399) and black for the WordPress logo. :)
--TigerDE2 14:08, 28 Aug 2004 (MESZ) Well, Olaf (who is responsible) and myself had a talk with Matt some time ago- That was the point when we decided to use green instead of blue. I do of course recognize that it might be better to have the same colour everywhere (because of branding, as you say), but since WP.de isn't an official page, we decided to reflect this fact in the choice of colours. Olaf is, however, currently redesigning, in order to have the same layout on all sections of WP.de. So, if you insist on blue, you might want to contact him during the next few days. (An English post at the "Forum" on WordPress.de will do. :)
My mistake, folks. I didn't see the second version of the 5 Minute Installation, nor did I see Matt's Installing page. I guess this is part of the learning curve; I dunno.
Sorry for this mess. I'm stepping back a bit I think to see where this all goes. Craig.
User Dbabbage 15:10, 13 Feb 2005 (GMT) Removed duplication of the same information within the Common Problems section.
User Westi 8:55, 24 Feb 2005 (GMT) Should we link to / incoperate the content of some support forum posts to do with installation issues - this one Install on Linux System - is particularly nasty where it all works when no wp-config.php exists but completely dies afterwards! I suspect that there are other gems like this too. (This particular gem came up on #wordpress today - looks like this time it was a mysql version issue php built against 4.0.17, 3.23.x installed on the machine!)
"Under Databases, select your WordPress username from the User dropdown, then select your WordPress database from the Db dropdown. Make sure All is checked under Privileges, then click Add User to Db." The original version of this tutorial had those last 5 words AND a screenshot under a sub-heading called "The Really Important Bit". Can this please be restored - it makes for forum linking so much easier. It was so named for a reason too. --Podz 13:21, 10 Apr 2005 (UTC)
I just got one of these, and I don't know how to be any more specific here, but maybe someone else does
<?php
// ** MySQL settings ** //
define('ice9_wpress', 'wordpress'); // The name of the database
define('ice9_wpress', 'username'); // Your MySQL username
..etc.
Robert Deaton 06:27, 29 Jun 2005 (UTC)
I get this message from the "install.php" command:
wp-config.php file. I need this before we can get started. Need more help? We got it. You can create a wp-config.php file through a web interface, but this doesn't work for all server setups. The safest way is to manually create the file."); require_once('../wp-config.php'); require_once('./upgrade-functions.php'); $guessurl = str_replace('/wp-admin/install.php?step=2', , 'http://' . $_SERVER['HTTP_HOST'] . dirname($_SERVER['PHP_SELF']) ); if (isset($_GET['step'])) $step = $_GET['step']; else $step = 0; header( 'Content-Type: text/html; charset=utf-8' ); ?>
Then, after the WordPress logo I get:
hide_errors(); $installed = $wpdb->get_results("SELECT * FROM $wpdb->users"); if ($installed) die(__('Already Installed You appear to have already installed WordPress. To reinstall please clear your old database tables first.
') . ); $wpdb->show_errors(); switch($step) { case 0: ?>
ReadMe documentation at your leisure.'), '../readme.html'); ?>
Two entry boxes follow. Then there's a BIG button with the inscription:
<? php_e('continue to second step »'); ?>
I think I must not be connecting to the database correctly through the phpMyAdmin, but my version seems to be a lot different (version 2.6.1-pl2) than the instructions.
Then there is a WHOLE lot of stuff starting with:
ERROR: please type your e-mail address")); } else if (!is_email($admin_email)) { die (__("ERROR: the e-mail address isn't correct")); } ?> query("UPDATE $wpdb->options SET option_value = '$weblog_title' WHERE option_name = 'blogname'"); $wpdb->query("UPDATE $wpdb->options SET option_value = '$admin_email' WHERE option_name = 'admin_email'"); // Now drop in some default links $wpdb->query("INSERT INTO $wpdb->linkcategories ....
First of all, the WordPress Codex is not the place to get specific help with problems. That is reserved for the Support Forums. It is only to provide documentation and resources to help you, not individual help.
Second, it seems there is a problem with your site's ability to use PHP. Check with your server or post a note on the forums for more specific help. Thanks.
And when you get familiar with how WordPress works and you want to give back to the WordPress Community by donating your time and energies to helping us provide more useful documentation here, we'll be here ready and waiting. Thank you. Lorelle 23:39, 2 Jul 2005 (UTC)
I’ve put up a Step-by-Step video tutorial about the installation of WordPress on Windows Server 2008. Besides covering the installation of MySQL and PHP (with FastCGI) on W2k8 server (details which are conveniently skipped by most instructions) it gives you a guaranteed approach to have a working WordPress.
The process of installing WordPress on Windows Server 2008 has a hidden problem – even the videos on microsoft.com, which breeze through the demonstration of a WordPress as an example of a PHP installation on IIS 7 are wrong. If you follow them you will not get a working WordPress installation (well, it works locally on the server but not on the remote clients).
I’ve been able to reproduce the problem with WordPress version 2.5.1 and 2.6. Here is what I am talking about.
The name by which the WordPress server is resolved during the initial configuration through a web browser is used from there on for all internal WordPress links. Hence, if you configure WordPress on the server all internal links are like “http://localhost/wordpress/xmlrpc.php”. Of course, they won’t work on clients on the WEB. The opposite is also true – if you connect from an external client, the public FQDN is used, which is fine for the internet users, but you will not be able to open WordPress on the server itself.
If anyone is looking for HTML templates for making your website. Then visit this site https://themexriver.com/best-responsive-html-templates/
Dean