I use formblock module (http://drupal.org/project/formblock) to create a block where users can quickly create new issues in OpenAtrium (screenshot : http://share.dnotes.net/2010-12-09_12-40-48.png). It works like a charm; the only problem is Rubik's js removes the buttons when the window is scrolled to the top, because the block still has a div.column-main div.buttons. The attached patch fixes the issue without too much overhead I believe, and to me it makes sense as a general principle as well.

I've tested this with the node entry forms and Rubik still functions as intended.

CommentFileSizeAuthor
#2 dont_take_my_buttons_2.patch627 bytesdnotes
dont_take_my_buttons.patch645 bytesdnotes

Comments

dnotes’s picture

dnotes commented
Title: Fix for rubik use with modules like formblock » Fix for rubik use with modules like formblock (patch attached)
dnotes’s picture

dnotes commented
Title: Fix for rubik use with modules like formblock (patch attached) » Fix for rubik use to allow hiding side buttons on some form instances (patch attached)
Category: bug » support
StatusFileSize
new dont_take_my_buttons_2.patch627 bytes

Whoa! How embarrassing. I posed a BAD patch; actually with that patch the buttons at the bottom of node forms would be removed but not put back. I've attached a different patch, and in contrast to the first, I don't believe it will have any annoying effects on other forms -- at least not so long as they're in the #content region.

The only problem is that if you place that block in a "content" region, such as the center column on a three-column page, it will still have the missing-button behavior. I was trying to find a way around that, but I misunderstood the form display functionality employed in Atrium and ... wow, interesting results.

Now that I understand a bit better, I'm definitely demoting this to a support request. If you've read this far, I'd love to hear if you have any ideas about how to recycle a node form in a sidebar block, hide some elements with CSS, and still have buttons. Always.

If you feel like making my day, and if it doesn't break any of the button-hiding goodness that you want, you might also consider applying this patch. But... I won't hold my breath.

haydeniv’s picture

haydeniv commented
Issue summary: View changes
Status: Needs review » Needs work

The only problem is that if you place that block in a "content" region, such as the center column on a three-column page, it will still have the missing-button behavior. I was trying to find a way around that

Sounds like this is still needs work.

aramboyajyan’s picture

aramboyajyan commented
Status: Needs work » Closed (won't fix)

All old and outdated 6.x issues are being closed.
Maintainer support will be provided only for major / blocking issues.

If you feel like this issue should be re-opened, feel free to do so.

Thanks!