As a follow-on to #2055951: Interesting MySQL issue appears to cause randomish "twitter_views_handler_field_formatted_tweet->render()" errors, the current best structure for storing the various Twitter IDs is a BIGINT. Review the schema of all supported versions of the module and fix them.

Comments

damienmckenna’s picture

Issue summary: View changes
damienmckenna’s picture

Version: 7.x-6.x-dev » 7.x-5.x-dev
Status: Active » Needs review
StatusFileSize
new2.87 KB

This fixes {twitter}.in_reply_to_status_id, {twitter}.in_reply_to_user_id and {twitter_account}.twitter_uid.

damienmckenna’s picture

Version: 7.x-5.x-dev » 6.x-5.x-dev
StatusFileSize
new2.96 KB

Ported to 6.x-5.x.

damienmckenna’s picture

Version: 6.x-5.x-dev » 7.x-6.x-dev
StatusFileSize
new2.87 KB

Ported to 7.x-6.x

  • DamienMcKenna committed 82d2e13 on 6.x-5.x
    Issue #2531874 by DamienMcKenna; Changed {twitter}.in_reply_to_status_id...

Status: Needs review » Needs work

The last submitted patch, 4: twitter-n2531874-5-7.x-6.x.patch, failed testing.

  • DamienMcKenna committed a9d3db3 on 7.x-5.x
    Issue #2531874 by DamienMcKenna; Changed {twitter}.in_reply_to_status_id...
damienmckenna’s picture

Status: Needs work » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.