Closed (won't fix)
Project:
Facebook-style Statuses (Microblog)
Version:
6.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
31 May 2010 at 12:52 UTC
Updated:
18 Nov 2010 at 22:06 UTC
Jump to comment: Most recent file
Comments
Comment #1
icecreamyou commentedI'm not going to add an option to do this.
I don't know how to keep variables from being available in a template although I'm sure it's possible. But that's a general question, not FBSS-specific. (Really though, the resources needed to generate the FBSS form are trivial.) I can tell you that Panels -- one of the most widely used Drupal modules -- doesn't disable any template variables when it overrides a page, so I'm sure it's not anything that you should be concerned about.
Comment #2
adam_c commentedThat seems to be drupals answer to everything, 'we'll just load it anyway, it's only a little bit of exrta processing'. Ok it may be, but if you have dozens of modules adding a little bit extra that isnt needed to every page load, and you have a massive number of page loads, that all adds up to a LOT of extra processing.
I think this is drupals downfall, things should only be loaded/processed if they are required.
IMHO i don't think contributed modules should decide what is loaded and what isn't, it should be the admins job.
Sorry for the rant, i've just been getting a little annoyed with drupals bloating problems lately. I do actually really like your module :)
Comment #3
icecreamyou commentedI agree with you, for the most part. I mean, that's what a framework does -- it loads everything you might need because that saves you the time of figuring out how to get what you might need otherwise. That can mean performance problems on very high-load websites, but considering the number of very high-load websites using Drupal, it's obviously not crippling.
Anyway, FBSS gives you a lot of options as far as what is displayed. The actual loading is up to core. But I'm glad you like the module.
Comment #4
heronog commentedHi, I'm sorry to bring this thread back from death.
I would also like to be able to choose to not display the Status block in the user profile.
This is not for performance, but to allow a theme to put the block/form in a sidebar. The way it is now, it will only show inside the main content of the profile, below the title and tabs for the page.
The use case I propose is, if a theme wants to show the status update box/form on a header or a sidebar, in a fixed spot through the entire site, it can activate the status block and put it in that region, but when the user sees his own profile, he will be presented with the status box mixed with the content, which creates UI inconsistency.
If a checkbox to hide this block from the user profile was provided, it would allow more flexibility in the way this module is used.
I'm attaching a diff file for 6.x-2.x-dev from September 6th 2010
The default is to show the block, so it won't affect existing sites.
Comment #5
icecreamyou commented2.x is in critical bugfix mode only. You can always just theme it out.
Comment #6
heronog commentedwhat needs to be done to get this feature? checkout from cvs is giving me some old code (I guess it's old, it's much less polished than the 2.x-dev tarball )
which version is the right one to patch?
Comment #7
icecreamyou commentedI don't use HEAD or MAIN in CVS, you'd have to check out the DRUPAL-6--2 branch directly to get the 2.x code from CVS. But a setting to disable showing the status update form on user profiles does not exist in any publicly available code. Right now, if you want to get rid of it, you have to override the user profile.