bob58

I have linked the two diff files in my blog at:
https://bobsblog.de/bob/index.php/2006/03/20/upgrade-auf-wordpress-202/

btw.: I know my theme is broken, but time is a valueable gift …

That depends on where you are upgrading from. 2.0? 2.0.1? 1.5.1? … there have to be a lot of lists. But of course it’s possible.

You can always do a diff on the old version and the new one and then upload only the changed files. I do that because it’s interesting to see what changed.

Take a look at the rating plugin:
https://codex.www.ads-software.com/Plugins/Posts_Miscellaneous

That might depend on how you set the image URL (src). You should always do something like
https://mydomain.com/wordpress/wp-content/myPicture.jpg
or
wp-content/myPicture.jpg

If you use /wp-content/myPicture.jpg, the browser requests the wrong url …

Maybe, you can find a plugin that does that …

https://codex.www.ads-software.com/Plugins/Images

Did you install both blogs to the same database with the same table prefix (wp-config.php)?

Can you have a look into what cookies were set when you try to login?

Hi,

no experience with 50 but with two.

Upload WP to the directory for your first subdomain, change wp-config.php to your db server and set the table prefix to wp01_ (do the installation to make sure, your db is configured correctly).

Then copy the above directory to the directory of your second subdomain and change the table prefix there to wp02_ … do the install …

Go on like this for another 48 times and all subdomains will work with one database.

I had a look into the code …

If the last post (to display) is reached, have_posts() rewinds to the first post. And I was wrong: If the last post is not yet reached, you get the information if another post is to be displayed.

I’m not sure, if have_posts() resets the loop (that could make sense), but the information you get is if there are posts in the system. So if there is at least one post available, you will allways get true.
Or in other words: that won’t work anyway …
Edit: My answer refers to the original problem. Moshu’s idea works of course.

As there are no user groups in WordPress (except for maybe the user roles, but that won’t fit there), I don’t see a way of doing that. You can hide a category from ‘guests’, meaning users who aren’t logged in …

That’s not a tricks:

https://static.www.ads-software.com/archive/wordpress-1.5.2.zip

Whow, your server seems to be very secure …
It looks like he refuses to deliver the style.css.
If I enter the adress of the stylesheet directly, I’m redirected to your blog’s main page …

With other words: Ask your hoster.

He can use the html-entities (their names). It’s not very handy, but it works in wordpress and is not too complicated. I have the same problem, because I often use non german keyboards and need german characters.

Take a look at that:

https://www.w3schools.com/tags/ref_entities.asp

That’s it. I think, the main target was to get it as secure as possible. Having ‘strange’ characters in a basic concept like a username can cause a lot of trouble (especially, if a lot of the developers can not test it) …
Don’t get me wrong, I’m german and my last name has a ‘strange’ character in it. But I prefer less problems in development (and less bugs) to usernames with umlauts. But that’s only my opinion.

Do all the other ‘Umlaut’-Users have the same problem or can they log in ?

That part has changed, the usernames are more restricted (to ASCII). But as far as I understood the code, the restrictions should only apply to new users, not to existing ones. You should insert an error report into trac.

https://trac.www.ads-software.com/

Maybe your user can use the “send password” functionality, to get his password and change it afterwards.

As I see it, the only things you can do, is
– change the user names to non umlauts or
– switch back to 2.0 (might be difficult without backup …)

There’s a third way: only change wp-include/functions-formatting.php

the function sanitize_user( $username, $strict = false)

should contain only the old line

return preg_replace('|a-z0-9 _.-|i', '', $username);

But that’s definitely a hack !