WPspider

+1

Also interested in a multisite implementation.

In my experience there’s no rhyme or reason as to how Plesk will handle multisite – at least on unix. I have had it working perfectly using several different configurations – and likewise fail (landing on the Plesk default page) using those same configurations.

Your best bet is to use a dedicated IP number to setup a subscription for yourdomain.com and immediately add “*” (without the quotes) as a subdomain. Next, go set an “A” record in your DNS for yourdomain.com to the dedicated IP address. While you’re there, go ahead and add an * subdomain “A” record for yourdomain.com.

Then, under Tools & Settings, Tools & Resources, IP Addresses, click said dedicated IP number and in the resulting interface select yourdomain.com as the “Default site.”

From there, it depends on what plugin or other process you use to map the domains to the subsites. You don’t actually need a plugin, but the method of doing it without one isn’t supported, so all your sites could whack out one day and you’d be faced with coming up with a new method (immediately), so not for the faint of heart.

Finally, throw the dice and hope that you don’t periodically get a site that simply will not map (even though dozens of other sites are already successfully mapped under the same network using the same settings) and you end up with the dreaded Plesk default page.

Okay, I’m a lamer. But maybe I can still be a hero for some of those banging their heads over this…

After chewing out geniuses that build this software, I took my own advice and ripped out my entire WordPress directory and database and restored them to an older version. But I still got 404 on my %category%/%postname% permalinks!

This clearly meant it wasn’t the WordPress 2.7.1 update.

So, after a couple of WTFs, it occurred to me that it had to be permissions or the Apache server configuration. (I’m not a programmer, but I do hack a little admin here and there.)

Anyway, first I ran my usual WordPress premissions commands: chmod -R 644 * and then chmod -R +X * and made sure permissions were okay. But still, I got the 404s.

So next, I grudging began scanning, line by line, through the httpd.conf file (which has moved a few times over the years and is now located at /etc/httpd/conf/httpd.conf in Fedora) and there it was! Properly placed between the <Directory> section was the AllowOverride directive set to none!

Of course when the AllowOverride directive is set to none, the .htaccess file is completely ignored! So I quickly set it to all and BAM! everything worked.

Of course, you may not want to set AllowOverride to all as there are other ramifications besides making your pretty permalinks work. But that’s something you can read about (see http://httpd.apache.org/docs/1.3/mod/core.html#allowoverride) after your blog is serving up pretty linked pages.

Hope that helps someone. And again, sorry to all you hard working WordPress project people.

Personally, I’m good with the new interface layout. It’s nothing new that a certain percentage of people do not like to change things. I think you see this same sort of thing every time a new Windows workstation version comes out. People adjust. Life goes on.

Anyway… on to issues.

I’m wondering if there is a reason why ID numbers aren’t ever displayed anywhere. I know I can hold my mouse over the link and get it there, but it seems like the kind of thing that would be displayed somewhere – especially for categories.

Well, that was pretty much it. Happy Thanksgiving!

Having the same problem, I searched Google for this:

“Is its parent directory writable by the server?”

I then found a link to this:

http://wordpress.org/support/topic/117888

Which essentially says that people having the same problem shouldn’t be so lame and they should go here:

http://wordpress.org/search/Is+its+parent+directory+writable+by+the+server%3F?forums=1

Of course, your post – asking the same question over again – comes up first in the results.

Clearly a lot of resources are being wasted, both in looking for the solution and in scolding those looking as being unwilling to really look for the solution. So I guess the next question becomes, “Is there some way to make a ‘sticky’ article appear at the top of the results when someone actually makes a proper search?”

Otherwise, it kind of seems like some old school geek penalty that is being imposed on everyone unfamiliar with the intricacies of UNIX. While I know that type of attitude is warranted in many cases, I’m not sure it is appropriate in the forums for a program that has such well-known and specific problems.

In any event, I must go now, as I need to wander aimlessly through the 133 articles that come up for the error we are discussing.

Best of luck.