mrmmills

Sorry about that. I was so irritated I let my emotions get the best of me. Any plugin that has to have access to other subdirectories within the WordPress site – hasn’t worked. Hello Dolly works fine but it doesnt make any calls to code in other directories.

I have now installed WordPress in both Apache 2.2.4 and IIS 6.0 and in both instance WordPress seems to work fine. But in both instances the plugins I tried (that have to have access to code in other directories) fails.

It almost sounds like a “DocumentRoot” problem but in each virtual website I did define the Document root in the virtual-hosts.conf file.

The default website for the local server uses this:
DocumentRoot “D:/Program Files/Apache Software Foundation/Apache2.2/htdocs”

The virtual sites use this:
DocumentRoot “D:/Websites/www.<sitename>.org”

My httpd.conf file also has:
DocumentRoot “D:/Program Files/Apache Software Foundation/Apache2.2/htdocs”

I am really at a loss, that is why I’m going to uninstall PHP5 and try PHP4. Time will tell I guess.

OK I **SUCCESSFULLY** installed:
WordPress 2.1.2
PHP 5.2.1
MySQL 5.0.37
on a Windows 2003 platform
(once in IIS 6.0 and a 2nd install in APACHE 2.2.4

However although WordPress appears to run fine I can’t get plugins to work properly.

I BELIEVE IT IS AN ISSUE WITH PHP5 VS PHP4 INCOMPATIBILITIES (because the plugins do work on a seperate PHP4 server fine).

Well its back to the drawing board, time to uninstall APACHE\IIS, MYSQL, PHP5, TOMCAT, and PHPMyAdmin and then install PHP4 to test my theory…. ??

Oops I forgot to mention. If your running Windows, then the Apache service tends to start before the Tomcat service – which is a big no-no. Stop both Apache and Tomcat, then start Tomcat first, then start Apache, then go to https://locahost:8080 and see if it comes up.

I haven’t learned how to tell Windows to treat Apache as a dependent service of Tomcat yet. I’m sure there is a doc on the web some where that will walk me through that…..

Here is the best tutorial I’ve found for Tomcat on WordPress. https://apacheguide.org/jsp.php

The guide above is very comprehensive and includes how to install PHP, JSP, Ruby on Rails, MySQL, PHPMyAdmin, and Tomcat to work with WordPress.

I hope that helps you. By the way, I’ve installed WordPress (in a W2k3 environment) on both Apache and IIS but in both cases I can’t get plugins to work – any of them. You got any pointers? email me at [email protected]

Nope – it looks like no one helps people with Plugin problems… I’ve installed WordPress on IIS and on Apache (both on Windows 2K3) successfully and can’t get Plugins to work properly. Without the functionality of Plugins, I can’t use WordPress. This is getting very frustrating. Email me if there is something I need to do to enable plugin functionality – Thanks
[email protected]

OK – now I’m really confused. I’ve successfully installed WordPress on Apache and I still can’t get any plugs to work. Maybe it wasn’t an IIS issue? Now I will look at other commonalities, so the commonalities between an IIS install and an Apache Install are what? I’m guessing I need to review the PHP.ini and httpd.conf file? I don’t think the MySQL install would have anything to do with a plugin problem. PHPMyAdmin and MySQL Administrator both work fine. Tomcat works fine. Several Virtual sites are configured and they come up fine. What else should I be looking for? How do you test why plugins won’t work?

The above server has:
W2k3 server SP2
IIS 6
MySQL 5.0.37
PHP 5.2.1
WordPress 2.1.2

Tried plugins:
dd-formmailer https://www.dagondesign.com
ccform

My ISAPI filter problem – How I fixed it – Remaining Security Questions:

I had followed the following site word for word:
https://www.juryriggin.com/2006/11/07/fixing-permalinks-when-using-wordpress-windows-2003-iis-60 but WordPress ISAPI filter was creating many Application log errors 2268 and 2214

So I then (most hazardly and without web security in mind) added the WordPress users “site_name_Anon” and “site_name_Admin” to the IIS_WPG user Group (it is creatd by W2k3 by default) and I also gave the user IIS_WPG “read” and “execute” permissions to the WordPressPlugin.dll file.

** My Permalinks and ISAPI WordPress Filter now work !! **

The question I have now is: What security holes have I created?

******************************
Why I did what I did:

I had gone to the following site to troubleshoot my ISAPI WordPress Filter problem.

https://blogs.msdn.com/david.wang/archive/2005/06/21/HOWTO-Diagnose-and-Fix-Common-ISAPI-Filter-Installation-Failures.aspx?CommentPosted=true#commentmessage

It educated me and I learned that my error was :
Data: 05 00 00 00 -Win32 error 5 – NET HELPMSG 5 returns “Access is denied.”

The article then mentions:

“For IIS6 in worker process isolation mode, the process identity is configurable and is at least a member of the IIS_WPG group” (see more on the link)

That’s when I got the idea to add the WordPress users “site_name_Anon” and “site_name_Admin” to the IIS_WPG user Group (it is creatd by W2k3 by default) and I also gave the user IIS_WPG “read” and “execute” permissions on the WordPressPlugin.dll file.

My ISAPI filter (Permalink) problem – How I fixed it – Remaining Security Questions:

I had followed the following site word for word:
https://www.juryriggin.com/2006/11/07/fixing-permalinks-when-using-wordpress-windows-2003-iis-60

but WordPress ISAPI filter was creating many Application log errors 2268 and 2214

So I then (most hazardly and without web security in mind) added the WordPress users “site_name_Anon” and “site_name_Admin” to the IIS_WPG user Group (it is creatd by W2k3 by default) and I also gave the user IIS_WPG “read” and “execute” permissions to the WordPressPlugin.dll file. **My Permalinks and ISAPI WordPress Filter now work**

The question I have now is: What security holes have I created?

******************************
Why I did what I did:

I had gone to the following site to troubleshoot my ISAPI WordPress Filter problem.

https://blogs.msdn.com/david.wang/archive/2005/06/21/HOWTO-Diagnose-and-Fix-Common-ISAPI-Filter-Installation-Failures.aspx?CommentPosted=true#commentmessage

It educated me and I learned that my error was :
Data: 05 00 00 00 -Win32 error 5 – NET HELPMSG 5 returns “Access is denied.”

The article then mentions:

“For IIS6 in worker process isolation mode, the process identity is configurable and is at least a member of the IIS_WPG group” (see more on the link)

That’s when I got the idea to add the WordPress users “site_name_Anon” and “site_name_Admin” to the IIS_WPG user Group (it is creatd by W2k3 by default) and I also gave the user IIS_WPG “read” and “execute” permissions on the WordPressPlugin.dll file.