petit

It’s just a guess, but I think you should look in the theme you use to see if some rules thre cuts the posts short.

In the default theme its possible to use the <!– more –> quicktag to cut off the post, but in the MODERN theme I temporaily use ( https://ulfpettersson.se/design/modern/ ) by some mechanism, lengthy posts get cut off.

I’m supposing this is a new instll with no data in the database.

When reinstalling, did you follow the install instructions by the letter? Or did you forget something like running the https://<yourdomain>/<yourblog>/wp-admin/install.php from your browser.

And when creating the new database, did you check the wp-admin/wp-config.php to have the correct database name, user and password?

By the error message it woudl seem that you don’t have any MySQL accessibel, but the message could be too insensitive.

Some questions:
Have you created a MySQL database for your WP blog? It might be nescessary, Your Service Provider will know.

Have you given the correct database name, user and password in the wp-admin/wp-config.php ( renaming it from wp-config-sample.php )?

Is this about WordPress 2.0?
The famous 5-Minute Istall at https://codex.www.ads-software.com/Installing_WordPress#Famous_5-Minute_Install
should work.

Oki – Thanx!

By studying the CSS for the default theme I’m using, I found that there are img classes called alignleft and alignright with padding and margin settings. By attributing my left aligned image class=??alignleft??, I got the space I wanted.

Just a thought.
You say the wp-content directory IS writable. Does this mean it’s writable by all ( or at least the web server ) ?
To write to the wp-content directory I think it also should be “executable” by the user attempting a write operation, i.e the web server.

If you have the index.php page in the directory you are addressing and it doesn’t show up, you’ll have to check that your web server is configured to recognize index.php as a legal index page as well as index.htm, index.html and possibly default.htm(l).

Just a hunch!
At upgrading, did you overwrite the wp-config.php, where the database name and user/pw resides. In that fatal event, restore the old config file.

msadventrues: Struggle on!
Seems like a lot of trouble. My own experience ( lucky me ) is that following the upgrade directives let me upgrade from WP 1.5.2 to 2.0 RC2 and later to WP 2.0 without any problems.
The blog resides on a UNIX/Apache by my service provider.
Now the problem with your “old site” indicates to me that the web server doesn’t recognize the index.php file as something to load by default, hence the listing. Web servers by default are configured to recognize index files named index.htm, index.html, default.htm(l) etc.
If you go to https://<yoursite>/yourblog/wp-admin/ with your browser, the web server should load the index.php page.
For this to happen the web server must be configured to recognize this page as a valid index page.

Maybe you well know all this and maybe someone else doesn’t.

Yes – really strange behaviour. I think you should have a look at the wp-smiley class in your themes Stylesheet if it exists. If not, you might check the CSS rules for img or p.img.
It seems as if your smileys take up a lot of space, which could be the reason they split your lines.
The smileys should be 15 px by 15 px, so where does the orange square come from ?
It may be that the CSS rules are to give extra margin or padding to images.

That’s excellent!
Considering the price and the voulontary basis of support it’s amazing.

Strange indeed!
Maybe you should check how it looks inside your database using mySQL Admin.
I’m using charset=UTF-8 which you may view source at my dummy blog at https://petitpub.com/blog/
( This is relly a dummy so far and not released ??

Aziza: I don’t know what the problems are with your “special” Swedish characters. As a Swede I’m also using the same characters and I still have them after installing WP 2.0.

This is something unicode was supposed to solve. However it’s not without complications.

The browser will see an XHTML page with a certain charcter set like UTF-8 or iso-8859-1 and should interpret the page content accordingly.
The content is stored in a MySQL database and it is also possible to set the character set for the database.

You may find some advice in this thread:
https://www.ads-software.com/support/topic/38615

Thanks to all hard working wordPress developers!
What a Christmas gift!

I followed the very precise instructions for upgrading, althoug I already had the RC2 installed.
I made a backup of my database with the backup plugin and
a backup of all directories in my WP installation,
disabled all plugins and
deleted all files and directories except the wp-content directory and the wp-config.php config file.
I then copied the wp 2.o distribution to my server blog directory.
Finally I run the wp-admin/upgrade.php script from my browser.
I checked my permalink structure and as I’m not using any .htacess file, it worked as before.

So now I’m off to check my plugins.

I guess lots of people had the novel idea, I’m sure I did.
I mean it’s a bit lonely to write a novel, so why not a collaborative one.

Severely moderated, mind you ??

Oh, my!
It’s already there.