Closed (duplicate)
Project:
Twitter
Version:
6.x-2.6
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Jul 2009 at 17:32 UTC
Updated:
11 Dec 2011 at 20:37 UTC
Jump to comment: Most recent file
Comments
Comment #1
sillygwailoVerified in 2.6.
Comment #2
graker commentedAnother issue for Preview: #633450: Status reset at node preview. Checkbox is not fixed though.
Comment #3
graker commentedI fixed 'twitter post' checkbox to save its state through node previews. The patch is attached.
Comment #4
skizzo commentedThe patch does fix the problem on my system
Comment #5
hefox commentedProbably fixes the issue, but I've never seen values in forms handled like that for preview (though it is 3:32 AM so my memory isn't as chirpy as that annoying bird outside is), so I suspect something else is at fault, perhaps the javascript?
Also, if the 3.x branch has this also, the code in question has been moved into a separate module (twitter_post)
Comment #6
graker commentedHmm. Maybe I didn't understand you right, but actually it is a common way to handle #default_value in forms.
Comment #7
hefox commentedAah... Looked around trying to find examples of that, but found this a pathauto one instead, http://drupal.org/files/issues/262464_pathauto_node_preview_11.patch . Instead of using form_values, they use that one in $node, so with that in mind re-patched. Same effect, but looking in $node seems more common.
Comment #8
hefox commentedoops copy and paste.
Comment #9
graker commentedYeah, it's nearly the same thing. I just more used to use $form_state since this way I can handle default values for all forms, not only node edit ones.
Comment #10
phreestilr commentedNot sure why, but when I made the changes in #8, I started getting the message "Successfully posted to Twitter" when new accounts were created. I instead used the patch in #3, and it seems to be working fine
Comment #11
hefox commentedguessing ya using content_profile phreestili?
Ignore my patch in #8, shouldn't be done in prepare I realized soon after, should be done in form_alter; I think it'd be best to use a combination of a patch, where it checks if isset $node->twitter in the form_alter, as it's shorter, but shrug.
Comment #12
phreestilr commentedYep, I am using content profile
Comment #13
skizzo commentedneither patch #3 nor #8 do apply cleanly to 6.x-3.0-beta3
Comment #14
steinmb commentedDuplicate of #633450: Status reset at node preview