Pligg importer
Posted January 15th, 2008 by dennis
Can anyone shed more light on using the pligg importer?
right now -- all I get is this message, (accessed via Administer ---> Site Building --> Pligg Importer):
"Please configure the module first - the category NEEDS to be set!"
I'm clueless as to what I need to do here.
You need to go to
You need to go to admin/category and add a vocabulary nammed categories I guess...
Read the step by step installation even if you installed drigg in one "easy" package.
http://blog-money-wiki.com/blog/
It means...
Hi,
You actually need to have Drigg properly installed and configured for the importer to work.
Please read this:
http://www.drigg-code.org/pages/download_and_install
Or install drigg-distr.tgz (STRONGLY suggested if you are new to Drupal!)
Lret us know how it goes,
Merc
no luck
I tried both routes before I had posted, several times at that, and again just now. I'm getting the same message. There seems to be no documentation about this module, whatsoever..
Any ideas? appreciate it.
Apologies...
Hi,
Please accept my apologies for the state of the pligg importer.
It would be _fantastic_ if you could give me:
* ssh or FTP access to the server
* the admin login/password
* the basic info about your site
I no longer have a pligg site to import, and am finding really hard to debug this...
You can trust me :-D
Merc,
ok
let me setup a sandbox -- i'll post the info tonight
OK thanks...
Hi,
OK thanks a lot!
Merc.
more info
what is needed? just the replicated pligg and access to the domain host via ftp?
Ideally...
Hi,
It's better if we talk about it my email
merc followed by "mobily1" and then .com
In general, the ideal scenario is:
* ssh access to the host. FTP is "ok" as well, but it will slow me down a lot
* The pligg db to be imported, with login and pass
* writing access to the the drigg module files (especially the importer)
* admin user/pass for the Drupal site which will import things
Bye,
Merc.
sent
hi merc, I've sent you the info -- will continue to update this thread until resolution, so stay tuned.
dennis
OK
OK...
It's a little late now. I will work on it tomorrow.
Please let me know your IM contact details, and let me know what time you'll be online!
Merc.
new errors
I was able to get it further -- I am no longer getting that error--I am seeing an import screen, and when i entered all the info in the fields and submitted, I got this list of warning:
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 289.
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 333.
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 360.
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 429.
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 458.
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 513.
* warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in /home/content/d/p/a/dpark/html/sandbox/sites/all/modules/drigg/drigg_pligg_import.module on line 529.
the thing is, it also says that the data was imported, but when i look in the db, no data was imported.
solved
The issue was this -- the pligg importer operates on the assumption that the (pligg) database is prefixed with 'pligg_'. In my case, I had changed this prefix to 'rs1_ ' ; hence the stacktrace you see above.
the resolution to this was opening both the database schema, and the data, and doing a case sensitive find/replace all on the two strings.
Thanks for the help Merc!