Hi,
your database settings are defined in the wp-config.ini which should be in the base directory of your wp. An normally if you managed to install wp you must have defined them correctly in this file before. Maybe there could be other restrictions to the db by your provider..well thats just a guess.
best regards
bee
If you have MySQL 4.0.x you may need to remove the charset part of the table definition in the main plugin file. That’s not supported until 4.1. Or upgrade your MySQL.
To bee dudler
thx ur answer but I still don’t know how to fix the problem
could u tell what is the code I need fix in wp-config.ini??
To RogerTheriault
the MySQL version is 5.0.45-community
by the way
Is exist the plug-in like Nextgen and it could use watermark funtion??
thx a lot
harker
Hi,
harker1113 the thing is if you have wordpress successfully installed and running your entries made in the wp-config.ini regarding db access should be ok anyway, but ngg seems to have a problem with them which is quite unusual.
So did you setup wp yourself, on which kind of hosting is it running, have you tried to ask your provider what the problem could be?
The question with watermarks depends on with what features (GD Library) php is running on that server.
best regards
bee
I think the problem not on provider
because I have two blogs made by wordpress
the other one use the same server,same plug-in(NGG)
it never have this problem…
but the different is the wordpress version of older site is 2.1.3
and NGG version is 0.52a
is it possible where the shoe pinches
thx ur answer
harker
Hi,
maybe that one is another hint:
http://wordpress.org/support/topic/181695?replies=2
best regards
bee
Thx ur hint
but I already try this way ,but it doesn’t work…
Hi,
which language versions of wp and ngg do you use and have you tried if there could be conflicts with other plugins in use?
best regards
bee
Why not upgrade WP to 2.5.1 and see if things improve from there?
And if you have two blogs on the same DB be sure you’re using different database prefixes!
I found out where is the problem!!
when I change wordpress version back to 2.1.3
and use NGG 0.52a
finally, it work without any damn problem!!
so I guess there exists something bug between NGG 0.96 & wordpress 2.5
I’m having the same problem, unfortunately I have no option of turning my WP version back to 2.1.3 Any thoughts on what could be causing the problem. I’m running WordPress 2.7.2
