It would be nice if this:

global $user; print facebook_status_form_display(NULL, $user->uid);

Could ship with the module. I don't want to use php filter in my blocks.

Thanks!

Comments

icecreamyou’s picture

icecreamyou commented
Status: Active » Closed (won't fix)

If it changes, it will be in 2.x, which is likely some months away.

Flying Drupalist’s picture

Flying Drupalist commented

Thanks for the reply, I don't understand what you mean change? It would just be nice if this becomes a block itself within the module. I'm not looking for any changes with it.

Thanks.

icecreamyou’s picture

icecreamyou commented

I won't add it until 2.x, if then.

Flying Drupalist’s picture

Flying Drupalist commented

Hi IceCreamYou, since 2.x has reached beta could this be under consideration as well?

icecreamyou’s picture

icecreamyou commented

It is in the module. It's the Facebook-style Statuses block with Legacy Mode and Slide Effect turned off in the module settings.

Flying Drupalist’s picture

Flying Drupalist commented

I think it's different. Legacy mode gives the status of the node/profile owner rather than the logged in user.

Turning off slide effect still keeps the message on top.

It would be great to have a block that just prints the form and nothing else, just like how this works:

global $user; print facebook_status_form_display(NULL, $user->uid);

Thanks!

icecreamyou’s picture

icecreamyou commented
Status: Closed (won't fix) » Postponed (maintainer needs more info)

I said you need Legacy Mode turned off.

I seriously considered this during development of the 2.x branch, but I conducted a usability review and concluded that removing the status text has a significantly negative usability impact in any normal UI situation. There are potentially places where it would not have a negative impact to remove the status text, but to get the form in all of those places would require using PHP, which wouldn't help you evidently.

So, I won't expose this through the admin UI. But I will consider making this much easier to do without using PHP in blocks; it will merely require that you run one short PHP script once. Is that satisfactory?

Flying Drupalist’s picture

Flying Drupalist commented

Thanks a lot! Though I don't really know what running a short PHP script once entails. I don't think I've ever done anything like that before.

About the message, since the message is also inside the form, isn't having it in both locations (inside form and above) redundant?

icecreamyou’s picture

icecreamyou commented
Title: User update form block » Option to hide status above textfield
Version: 6.x-1.x-dev » 6.x-2.x-dev
Assigned: Unassigned » icecreamyou
Status: Postponed (maintainer needs more info) » Active

Sure. I have documentation on it already, I'll point you to it when I get this committed.

That was my logic originally, and I was planning to get rid of the status text above the textfield as you have suggested. However, when I was testing with other users, they occasionally wanted to know what their previous status had been after they clicked the form (clearing it, except on user/* and share-status) and none of them thought it was illogical to have the previous status that way (although some noted that if the block was used above a minifeed like Facebook's, the text wouldn't be necessary because the status should already be in the minifeed). It probably doesn't make too much difference.

Also, I've been thinking about moving this and two other hidden options to an Advanced tab in the settings or something similar. We'll see what happens.

Flying Drupalist’s picture

Flying Drupalist commented

Great, thanks!

icecreamyou’s picture

icecreamyou commented
Status: Active » Fixed

Fixed in dev. There's a new Advanced Settings page with this option on it.

Status: Fixed » Closed (fixed)

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