Hey - hang on man - this is totally unfair critism.
Your problem as was explained several times by the great volunteers at PostNuke was NOTHING to do with PostNuke. You would have had the same problem with any software that you tried to use that uses the mySQL database. I believe your problem was that you haven't taken the time to understand any of the underlying principles of the sophisticated tools that you are trying to use!
MySQL has its own user permissions system. Once you have created a database you have to create a user with the appropriate permissions to use that database, WITHIN the mySQL permissions system itself. You can use SQL statements (GRANT etc) to do this or the very handy phpMyAdmin tool (that you would have to install on your system).
I don't think anyone would recommend that you use the "root" user with a "blank" password in a real application !!
Try having a good look at www.mysql.com and please don't slag off excellent open source software when the problem is your own understanding!
Login
Donate to Zikula
Installation, Configuration, & Upgrades
::
Another "Cant create Database" error
-
-
- rank: Moderator
- registered: March 2002
- last visit: 26.08.08
- Posts: 7720
-
Posted: 10.05.2004, 03:19
In this case the username 'root' isn't such a problem as it's a windows machine so theres no relevant the the root account on a unix box but the account almost certainly has create/drop database writes amongst the other permissions that you'd not want an account for a publically facing application to have.
If the password is a blank one rather than 'blank' (which was my original reading) then there's a bigger problem there.....
-Mark -
- rank: Legend
- registered: December 1969
- Posts: 6596
-
Posted: 10.05.2004, 03:28
My point was that if you used root it would open up potential security risks with in the DB< not the system. Though I'm under the impression, in this case, he's using it on an intranet, so it's more secure. But it still stands, you need to learn a little about the tools you're using. -
- rank: Softmore
- registered: May 2004
- last visit: 18.02.06
- Posts: 74
-
Posted: 10.05.2004, 03:31
I appreciate the flame site admin. I have used PostNuke before.. but only in its "installed" form. My website used to be hosted in some place in Jersey. A friend of mine gave the site space to me for free. The site access has ended and now im trying to do everything from my house so i don't have to go through this again.
I don't really wish to in stall this myself, but i have a website that needs to be up and running. I never claimed to know everything abut PHP mysql or anything of that nature, and i find it really funny that you finally have something to say (non-constructive) after i have finally figure this ordeal out myself. Thanks... Now thats support.
My setup was fine, and the fix took about 5 minutes. My database name and pass are still what i set them at and im done pulling my hair out. Sounds like a good thing to me ;)
See you again sometime ;) -
- rank: Legend
- registered: December 1969
- Posts: 6596
-
Posted: 10.05.2004, 06:58
That was not a flame in any way shape or form. It was logical advise that it would be wise for you and anyone to keep in mind. Running and administering PostNuke on a remote server is totally different than running a server, and if you're going to attempt to run a server, you should do some research and reading on the platforms you need. PostNuke.com is not the place to learn how to do MySQL, PHP Or Server administration. -
- rank: Freshman
- registered: May 2003
- last visit: 20.05.04
- Posts: 37
-
Posted: 13.05.2004, 03:16
Sorry if you thought my comments were "flame" - they weren't meant to be.
If you're happy with your fix then thats fine (I suppose). But just bear in mind your sites security may be on the paper thin side? I think we were all just trying to suggest /advise that a little bit better understanding of the mySQL user / security issues would be wise.
Good Luck.
