trouble with multiple status update forms on the same page [#1804202]

Dear maintainer,

when including several facebook status streams and multiple update forms in several nodes context at once, the facebook status form works fine on all included nodes, but the fbsmp plugins only ever update the first update form. Clicking any plugin icon always displays the plugin form on the first status update form. Any pointers how I can help, fix this?

Thanks!

John

Comment	File	Size	Author
#1	screenshot fbmsp multiple.png	11.86 KB	wickedwookie

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

wickedwookie CreditAttribution: wickedwookie commented 9 October 2012 at 09:40

File	Size
screenshot fbmsp multiple.png	11.86 KB

Attached you will find a screenshot to help better understand the problem.
The right column is the "first" status upbdate box with #id edit-facebook-status, the one in the middle is edit-facebook-status-1 and so on. Clicking on any attachment/plugin icon always addresses the first one.

Thx,
John

Comment #2

Dinesh Kumar Sarangapani CreditAttribution: Dinesh Kumar Sarangapani commented 10 October 2012 at 05:16

Hi wickedwookie,

There is a stable 6.x-2.0 version released for fbsmp, please use the stable release and make an issue. If you are using the stable version the mention the proper versions of module you are using. For more details refer here

Comment #3

IceCreamYou CreditAttribution: IceCreamYou commented 10 October 2012 at 06:04

Actually, as noted on that page, bug reports should ideally be filed against dev:

If the bug still exists in the latest official release, upgrade to the latest development version (-dev) and verify the bug still exists there (it may very well be fixed in -dev, but not yet made it into an official release). Ideally, all bugs should be filed against -dev as all code changes are only applied to -dev.

With regards to the problem in this issue -- FBSMP was clearly not designed to have multiple status update forms on the same page. I think the problem you're experiencing is because the module targets a specific CSS ID to insert the form into, and there should only be one DOM node with a specific ID on a page. Not sure of the best solution off the top of my head.