Support Forum
lol. no need to debate meaning of localhost anymore... understand your situation now...
should be no need to unlock root... we do not attempt to use it... so to verify, in you wp-config.php file, you have a proper db user, db name and db pw set up?
but Andy authored the importer though I think the vbulletin addon was authored by a user... will need to see if Andy has any ideas in the morning (night long upon the UK)...
Visit Cruise Talk Central and Mr Papa's World
Whew, glad to hear I'm not stranded out here with a weird, unsolvable problem.
I assume my wp-config is properly configured. (I x'd out half of it here for security.)
/** The name of the database for WordPress */
define('DB_NAME', 'xxxxxx_wp648');/** MySQL database username */
define('DB_USER', 'xxxxxx_yesahnew');/** MySQL database password */
define('DB_PASSWORD', 'xxxxxxxxxxxxxxxxx');/** MySQL hostname */
define('DB_HOST', 'localhost');
nope. we are here to help...
and I assume (sorry if dumb question) but the data you entered in the vbulletin input fields in our plugin match what is in the vbulletin config file?
this one is bit odd, because as I said, I think the vbulletin addon was user contributed, but has worked many, many times... but our different db converters also ask for the wp db info too - so was bit surprised that vbulletin did not too...
but Andy will be around tomorrow morning and may have more insight though he seemed as confused as I in earlier posts...
Visit Cruise Talk Central and Mr Papa's World
Steve is not quite right. As the importer plugin is being run in the base WP environment we do not need to collect the WP connection data as we already have that so it is only the source DB connection data we need.
For reasons unknown (because of the errors you DO see) - the importer seems to be throwing an error over something. This calls our error handler as normal but it seems that the php mysql functions being used IN the error handler are attempting to be connected with the root user and this is why it makes no sense to me. These should be connecting with the WP database user name/password.
Perhaps another question for your host - and maybe a good one to ask - is if, for any reason, they have blocked the use of the php mysql extension functions...?
YELLOW
SWORDFISH
|
My host just asked me for logins to WP so that he could run the import and see what's going on, and now something else has come up. I uninstalled Simple:Press, then went to reinstall, and now when it starts that process, it kicks me over to the login screen. I re-enter my logins and the screen goes white. That's in IE. In Chrome, it ran through the installation, but when I hit "Import" I get a message that I don't have sufficient permissions.
saponitown.com/wp/wp-admin
un: coop4
cificap87^23
I know someone said this script has run many many times before, successfully. We're on cpanel. Is anyone aware of it running successfuly on that? Could the script need to have WP un/pw entered, like they are on the other scripts (what had Mr Papa confused)?
Should I just wipe out this WP installation and do a fresh install?
i really don't know what to say except that you clearly have some weird things going on there.
The hosting control panel isn't going to make any difference to anything. And none of the importer scripts collect the WP credentials - as I said - there is no need. The vBulletin importer script is not the most commonly used and - as we have said - was not written by us. But it has been used to my knowledge quite a few times as I know I have had the issue of the prefix come up before (seems some do and some don't).
Does this login issue happen every time you try this or did you not try and repeat the exercise? And is the 'permissions' message using Chrome one of those unhelpful and somewhat bewildering WP messages - just a sort of white box on grey with no way to get out of it?
YELLOW
SWORDFISH
|
Yes, it's a white box on grey. The login issue is a brand new development. In IE, it was telling me I don't have sufficient privilieges to proceed. I'm going to try and wipe out this WordPress installation and start from scratch all over again. Doesn't the options table store a lot of stuff? I've got another host who can do a free move for me. I suppose I'll try that eventually, just try it somewhere else and see what happens.