Closed (fixed)
Project:
Node import
Version:
5.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
3 Aug 2007 at 22:17 UTC
Updated:
28 Apr 2011 at 13:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
rimma commentedI just find this issue no just for forum type but possibly for all content types.
this module set comments to disable, no matter what your original setting.
I try to change from the database, but even i set from database table, it still does not work.
what is problem? it is bug?
hopefully , somebody knows.
Thanks.
Comment #2
rimma commentedComment #3
rimma commentedany idea, I greatly appreciate.
Comment #4
rimma commentedComment #5
rimma commentedI find a way to do that is update my table column from database.
but I do not how to do that from node import module.
Comment #6
taqwa commentedi need this as well
Comment #7
taqwa commentedComment #8
BradM commentedjust noticed this too, imported over 1000 nodes that have disabled comments.
I have limited access to the tables via the database module, so I managed to switch comments back on by using the 'query database' option. Note, if you choose to use the example below, do so at your own risk! Backup your tables!! Modifying tables in this manner scares the **** out of me...but like I said, it worked for me.
I have a node type set up as "tvseries" -- first I entered this in the query window:
select * FROM node where type='tvseries'This then told me that I was dealing with the correct data -- all comments were set to "0". Essentially 'Disabled' = 0, 'Read only' = 1 and 'Read/Write' = 2.
Then, I entered this in the query window:
UPDATE node SET comment=2 WHERE type='tvseries';Bam, all my tvseries nodes are now set to 2, meaning people can leave comments. Whew.
Comment #9
rimma commentedThanks BradM.
I do a similar way as you.
just update all nodes to make comments available.
Comment #10
platypus media commentedJust updating the nodes is not a feasible answer when importing large quantities of data.
Comment #11
BradM commentedI know it may be a pain but it doesn't matter if you're importing 1 or 10000 nodes. The query does it all for you.
Comment #12
peterpoe commentedHere is a patch to import comment options. I have mildly tested it with both valid and unvalid data, but it's fairly simple so it shouldn't give any problem.
Comment #13
rimma commentedHi Peterpope,
Thank you for your patch.
I will try it later for a big database.
thanks.
rima
Comment #14
Robrecht Jacques commentedI've added a new support file: comment.inc which will be included when comment.module is enabled:
This implements the same functionality as the patch provided.
Committed to DRUPAL-5 branch. It will be included in the next release (5.x-1.3). Thanks!
Comment #15
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #16
alexmoreno commentedwonderful. In my situation i had problems with feedapi (now feeds) and nodecomments. Importing using Feeds results in nodes with comments disabled... great review web without reviews possibility, don't you think? :-)
solution:
UPDATE node SET comment=2 WHERE `type` LIKE 'type_of_content'
thanks a lot :-).