rustindy

bbPress is pretty decently rocking already, but being able to subscribe to a thread would be a nice addition.

I’d thanks you for that, but neither theme is mine ?? I like the other theme too, actually.

The short answer is no – WordPress will not work with SQL Server. However, by installing PHP (similar to ASP) and MySQL (similar to SQL Server), you can indeed run WordPress on an IIS server. Even on Windows, though, it’s better to use Apache.

MySQL 5 *should* be run in strict mode. WP does not comply to the SQL2003 standards, so the solution is not to disable strict mode (standards mode), but to fix WP’s INSERT commands to get rid of the errors they cause.

Drafts do not work with WP2.0 and MySQL 5 strict-mode. I don’t know if they work with MySQL in loose mode.

Ahhhhh k, guess a couple got missed. I’ll do some bitching on #wordpress tonite and try to get it patched. The code fixes for these problems are really easy, and I’m obviously good at bitching ??

Jan, the RC3 release works under MySQL strict mode. I’ve installed it from scratch in Apache 2.0.55 with PHP 5.0.5 and MySQL 5.0.16 in strict mode. The SpamKarma2.1 beta will work under strict mode now as well ??

Jan, the problems with strict mode have been fixed. the 2.0 release should work fine.

Nope. WordPress requires PHP, not ASP. That being said, ASP runs on IIS, and if PHP is installed on IIS as well, then WordPress *will* work. But *only* if PHP is installed. The existence of ASP means nothing either way.

Actually, I much prefer forums like bbPress and Vanilla to ones like phpBB and vBulletin. The only “large-format” forum I don’t completely hate is SMF, to be honest. Everything else looks the same.

MySQL 5 strict mode enforces schema integrity. The problem with WordPress (indeed, most OSS written with MySQL in mind) is that it creates a database schema but then fails to adhere to it. In the past, MySQL only generated warnings when this occurred, but in strict mode it acts more like an enterprise database system and throws errors instead of warnings.

There are three ways to fix this.

First, do not use strict mode. But as smowton noted, it is far better to use strict mode since it enforces good code. There is, unfortunately, a lot of sloppy database code out there.

Second, you can modify the database schema either by editing the WP installer/upgrade file, or directly modifying the database after installing.

Third, and this would be the preferred method I think, you can go through the source and correct the SQL commands that cause the errors.

So that you know, the current betas of WP 2.0 install just fine in strict mode, although commenting is currently broken due to the same issue (bad INSERT syntax in the WP codebase). HOPEFULLY, this will be fixed in the final 2.0 release, especially since there is already a patch on the trac site that fixes commenting in strict mode.

OK, first of all, you uploaded WP into a folder named /wordpress, so the address for installation needs to be https://le-sigh.com/wordpress/wp-admin/install.php. Second, you also need to rename the wp-config-sample.php file to wp-config.php and make sure it’s in that folder as well. If you go to https://le-sigh.com/wordpress/ and see a link to install.php, then it’s fine. Currently, it’s complaining that it can’t find wp-config.php.

Yup, a few themes do that. There’s just an “e” after the post title, and it’s a link to edit the post. Only the logged in admin can see it (or the author of the post, whichever).

Yes, I meant the same thing. The “mysql” and “mysqli” modules can either be loaded as libraries or compiled into PHP. Even PEAR uses them. PHP *has* to have a database module loaded in order to use that database (at least as of v4.0 – MySQL was built-in at that point, as well as ODBC in Windows). WP, doesn’t use PEAR, but the database library it does use is still limited to whatever database modules PHP loads itself. If “mysqli” isn’t loaded by PHP, then PEAR (and WP, in this case) cannot use it’s functions. Actually, I’m not even sure WP can use “mysqli” at all…

Anyhow, what I’m trying to ask is what version of PHP you’re using. If it’s PHP 4.0, then you’ll have problems unless PHP was compiled using the MySQL library included with MySQL 4.1 – the MySQL client library that’s included with PHP 4.0 will not work with MySQL 4.1 and higher, unless MySQL is using the old password fix.

sikittle: WP does not use the “mysql” library, PHP does. WP (indeed, any PHP code) accesses whatever library that PHP has installed (or is compiled with) to connect to databases. So TextPattern will also use the “mysql” library, since that library is specific to the PHP engine itself. Applications get no choice in the matter if they want to connect to MySQL through PHP.

if your host is using PHP 4.0 (or lower) and MySQL 4.1 (or higher), they *must* have a mechanism for letting client applications login, or no PHP code at all would be able to do it, including WordPress, TextPattern, phpBB, phpMyAdmin, etc.