Closed (fixed)
Project:
Facebook-style Statuses (Microblog)
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Reporter:
Created:
6 Sep 2008 at 07:12 UTC
Updated:
21 Sep 2008 at 17:33 UTC
Jump to comment: Most recent file
Comments
Comment #1
icecreamyou commentedThe standard way to do it, that's already part of the module, is to turn Facebook Status Mode off in the module's settings. However, that gets rid of a number of other things that you might want.
I'll interject as well that the reason the name is in the label is to make it more coherent, so the user knows that their status will be in the form "[username] [status]" instead of just "[status]." You may want to reconsider the title of your block...
I'm not going to change this in the module (although in the next version, the colon after "Status" in the label will be translatable). But if neither of those options works for you, you can simply add this line in the code after line 295:
Comment #2
gausarts commentedOk, sorry for not getting the point. Actually what I had in mind was simply:
[username]: the facebook_status form-text
Without label Status:. That would make more like facebook status form, with a simple touch of CSS floating or inline. I don't want to touch the module, but I have to give that code a try to fit the current need. Thanks
Comment #3
icecreamyou commentedAh. Well the word "Status" is translatable right now and in the next -dev release the colon will be too. So to get rid of that and just use the username, you just need to set the translation to blank.
If you don't want to wait or you don't want to mess with translations, replace line 302 with this:
...and comment out line 291:
Comment #4
gausarts commentedWow, great and thank for the quick reply. I was still thinking over to express the right things in my mind, but you come quickly with the answer. Lots of thanks.
Comment #5
icecreamyou commentedNo problem.
By the way, if you'd like to post the CSS in here to get the username to display on the same line as the status-update field, I wouldn't mind adding that to the module. I've been thinking I should do that at some point.
Comment #6
gausarts commentedI haven't made any change to the module, but I should confirm if this is indeed like facebook:) Please correct me:
Comment #7
gausarts commentedHere's after your suggestion
Comment #8
icecreamyou commentedYes... I'm now understanding even better why this issue was opened. :)
My question was, how did you get the label inside the textfield without allowing it to be edited? I will understand any code you show me, I just sometimes have a hard time writing my own CSS. I know you don't have to modify the module to do this, but if you show me what you did then maybe I can integrate it.
Comment #9
gausarts commentedHere is the CSS code for my specific block need. Uncleaned, as most are just to override precedent CSS codes:
Comment #10
gausarts commentedI guess if you can make the $xname placed inside a span, even without making you go to table design, only with pure CSS, we can correct the problem with the width of .facebook_status_block input#edit-name. Haven't tried myself to hack the module, just a guess. Thanks
Comment #11
icecreamyou commentedI still can't duplicate what you've got--the label won't appear inside the textfield. If you'd like to write a patch to make this work (it doesn't have to be patch format since I'll apply it manually anyway) using drupal_add_css I'll probably integrate it; if not, we can just mark this issue as fixed.
Comment #12
gausarts commentedOk, thanks, fixed. Just to clarify things, I didn't do anything with the module. It's only CSS. The label is not inside the textfield, only appears to be inside it. They just stay inline. Then .facebook_status_form #edit-name-wrapper pretends to be the textfield:) Thanks again for the support.
Comment #13
icecreamyou commentedI know that; but the CSS could be added to the module if I could figure out the #edit-name-wrapper part.
Anyway, thanks for the head-start, and I'm always happy to help.
Comment #14
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.