Tweet text cannot be longer than 32 characters

I see this problem in my site as well. I've been searching for a fix for a few days. Anyone else run into this?

  \sites\all\modules\tweetbutton\tweetbutton.install (1 hits)
	Line 18:           'length' => 32,  
  \sites\all\modules\tweetbutton\tweetbutton.module (1 hits)
	Line 114:     '#maxlength' => 32,

change 32 to 140. it works for me

The patch, based on Stakcreativa's comment is attached, please review. Cheers!

I have reviewed the patch and implemented it on 2 sites, which fixed the 32 character max string length. It worked fine on both sites and I have yet to see an issue arise.

the patch looks fine at first glance but without hook_update_N() the problem will only be fixed for new installations, not for sites already using an older version.

You can change the values from phpMyAdmin to tables "field_data_field_tweet_basic" and "field_revision_field_tweet_basic" like in the attachment.

I attempted to change the values in phpMyAdmin from 32 to 140, but that had no impact on getting the original error message.

In addition, I'm finding that this problem is preventing us from editing any existing content on our site. When I try to edit page content on pages with titles that are more than 32 characters, this error prevents the saving of any edits. This is a very critical problem that is forcing me to disable the Tweet Button module until it is resolved.

I wish the Drupal 7 version of this module worked the same way as the Drupal 6 version.

For the current stable version (7.x-2.0-beta1+1-dev), you can simply fix this issue:

Edit tweetbutton.module file at line 114 replace "'#maxlength' => 32," with "'#maxlength' => 128,"

(field_tweet_button_text database field has VARCHAR(128) by default)

I have changed the maxlength for the form elements to fix this issue.

As install file has been written correctly, no need the patch that file. Update the maxlength for the field 'account' (tweetbutton_field_widget_form) as 32 and 'text' as 128.

This solved my issue.

I am updating with a minimized patch file.

Updating again by keeping only relevant patch for this issue.

Works for me.

Updating with a patch which path changed.

test please ignore