Any plans for porting this community essential module to Drupal 7? Thanks!

CommentFileSizeAuthor
#90 facebook_status-d7_conditions.patch2.13 KBdamienmckenna
#77 facebook_status.patch315.23 KBskottler
#61 facebook_status_to_d7.patch530.06 KBicecreamyou
#16 facebook_status-7.x-671822-16.patch209.07 KBpillarsdotnet

Comments

pribeh’s picture

pribeh commented

From the front page:

The next step for this module is probably a full Facebook-style Publisher, but the implementation of this is undecided and in the distant future, and may have to wait until D7. (I am planning to develop a D7 version of this module, but it may not have a full release on the day Drupal 7 is released.)

Please do not open issues in the queue that request features already on the roadmap.

icecreamyou’s picture

icecreamyou commented
Status: Active » Closed (works as designed)

Major bonus points for pribeh. There will be a D7 version. I haven't started it, and I don't know when a stable version will be ready, but it will not have the kind of delay after D7's release that D6 was notorious for.

mehtatejas’s picture

mehtatejas commented
Status: Closed (works as designed) » Active

Any plans for porting this community essential module to Drupal 7?
Thanks

icecreamyou’s picture

icecreamyou commented

My answer is still the same as #2, which is also the same as what I said in my response to your email.

mehtatejas’s picture

mehtatejas commented

Drupal 7 was officially released in first week of jan. and I would like to use Drupal 7 with your popular module. Can you please suggest when can you start porting this module to drupal 7 version.

ven7ura’s picture

ven7ura commented
Title: Please port to Drupal 7 » Port Facebook-style Statuses to D7

May we get any upgrades on this?

Thanks in advance, subscribing. :)

PD: Changing the title for Dashboards.

icecreamyou’s picture

icecreamyou commented

From the project page:

I am planning to develop a D7 version of this module, but I'm not sure when it will be ready. The port will start some time after the 6.x-3.x branch gets stable enough.

The 6.x-3.x branch should get a beta some time next week hopefully. That is as much as I know right now. The project page will continue to reflect the status of the roadmap.

ven7ura’s picture

ven7ura commented

Thanks for the info!

Will wait for this great module.

danielm’s picture

danielm commented

subscribing

bensnyder’s picture

bensnyder commented

Beta is out :)

BenK’s picture

BenK commented

Subscribing

nikkubhai’s picture

nikkubhai commented

Eagerly waiting. Thanks :)

dgastudio’s picture

dgastudio commented

+1

Shadlington’s picture

Shadlington commented

Sub'd

pillarsdotnet’s picture

pillarsdotnet commented
Version: 6.x-2.x-dev » 6.x-3.x-dev

Has anyone run the 6.x-3.x version through coder upgrade to get a start on the 6.x-7.x upgrade?

If not, I may do it myself...

pillarsdotnet’s picture

pillarsdotnet commented
StatusFileSize
new facebook_status-7.x-671822-16.patch209.07 KB

Okay, I ran it through coder for a first-pass attempt.

Here are the results -- don't expect them to work yet.

hypertext200’s picture

hypertext200
he/him
Primary language Singhalese
Location New York City
commented
Status: Active » Needs review

Started a github for this module https://github.com/heidisoft/Facebook-style-Statuses, you can contribute there and finally we can contribute back to the d.o. community

rogical’s picture

rogical commented

Subscribing

yugongtian’s picture

yugongtian commented

+1

kokrull’s picture

kokrull commented

Subscribing

nikkubhai’s picture

nikkubhai commented

@IceCreamYou : Don't you think waiting for 6.x.3.x-rc1 will greatly postpond the 7.x version release. Many people are asking for 7.x version, many more are waiting. This module has become a necessity for us. So, please please please think of porting the module to 7.x asap.

Shadlington’s picture

Shadlington commented

If you *need* this right now then I would suggest you think about either a) Writing patches or b) Offering to fund development.
That sense of entitlement is misplaced in open source.

IceCreamYou is doing this for free, in his own time (until someone pays him to do it).
If he wants to finish an RC first (which I also believe is the most sensible option) then that is his decision.

If you started building sites in D7 before the modules you consider necessary were ready, then that is your own fault.

nikkubhai’s picture

nikkubhai commented

@Shadlington : I totally agree with you. And by no means I am saying that IceCreamYou is doing something wrong. I am neither blaming nor advising him. I am just requesting him;if its possible for him to think of porting FBSS to D7.

Shadlington’s picture

Shadlington commented

Okay I think I was a little harsh earlier - apologies, I'm tired and irritable this morning.

Still, he's already aware of it.
That said, the number of outstanding issues on the D6 version is dwindling so an RC might not be that far off.

icecreamyou’s picture

icecreamyou commented

Here's the deal:

The port of FBSS to D7 will begin with a patch generated by the Coder Upgrade module as suggested in #16. This patch is currently about 4000 lines, and I intend to apply it by hand so I can see what changes are being made -- so that is going to take awhile. I expect that that will get us about 85% of the way there in terms of code and 60% of the way there in terms of functionality, not including integrations. Integrations are a whole separate story, because a lot of modules have changed APIs between D6 and D7 versions. Views in particular will be tough to upgrade because even though its API hasn't changed much, the changes are not documented at all.

I would prefer to get fixes into the D6 branch of FBSS before porting it to D7 if only because once I have a D7 branch I have to do twice the amount of work for every patch. Also once the D7 branch gets stable enough I will stop work on the D6 branch, so it would be nice to fix any issues that actually matter in D6 before that happens.

There are other priorities to balance as well. For example, the Facebook-style Micropublisher module is in limbo at the moment -- it hasn't been upgraded to support the 6.x-3.x branch. Although I'm not the primary maintainer of that module, it is an important part of the FBSS ecosystem, and I want it to become part of the core FBSS package at some point.

The good news is that I will be working at Acquia this summer, and a significant portion of what they are hiring me to do is work on this module. The work will (at least initially) be targeted at stabilizing the 6.x-3.x branch, but that's good news for the 7.x branch either way.

Also, I'm very aware as the maintainer that the lack of a D7 branch is holding back some sites from adopting this module (not that there's a serious alternative). Believe me, I want it done as soon as possible too. But unfortunately it's a slow process.

nikkubhai’s picture

nikkubhai commented

Thanks Isaac for your explanation. :)

webankit’s picture

webankit commented

+1

dremy’s picture

dremy commented

+1

sonnykt’s picture

sonnykt
Location Melbourne, Australia
commented

+1. subscribed.

achton’s picture

achton
Location Denmark
commented

Subscribing.

icecreamyou’s picture

icecreamyou commented

For all those subscribing, the major blocker to a 6.x-3.x release candidate (and therefore the major blocker to a D7 port) is the instability of the comments submodule. Check out the roadmap and please help if you can.

JamFar’s picture

JamFar commented

+1. Subscribing.

bigsyke’s picture

bigsyke commented

+1!

a.siebel’s picture

a.siebel commented

subscribe

johanbeckers’s picture

johanbeckers commented

+1 subscribing

scw’s picture

scw commented

hi, so when updating to D7 you may wanna checkout this on github. Picked that up from #17 and did a "few" improvements.

Babalu’s picture

Babalu commented

i have downloaded the release from github and enabled it, but now i can't access the user profiles

scw’s picture

scw commented

make sure using 7.0-1.0-dev branch NOT master (was the initial from #17). Just for clearness i stripped out the whole ahah stuff that's not necessary anymore also all js. There is a problem when enabling the module with the initial default views (facebook_status_stream, was it called like that????). I deleted it and made a new one based on a very old D6 installation. So, not very reliable... Anyways, that is and should not be my problem. I just did changes that are necessary to run on D7. cheers

Babalu’s picture

Babalu commented

oh, but i have downloaded the 7.0-1.0-dev branch from screamwork not the master and i can't access user profiles not yet

Babalu’s picture

Babalu commented

your new release works :) thx

good_man’s picture

good_man commented

subscribe

dilari’s picture

dilari commented

While d7 port might me happening soon, can I suggest a name change?
Since "This module is not affiliated with Facebook in any way." Why name it facebook-style-statuses ?
I understand that 'facebook' might be what people are looking for when searching for such a module-set but it does not have to be in the name does it? I think it deserves it's own name. A-drupal-one.
Some suggestion: drups, member-stream, status-stream, drupstream, drupals,..

moved to : http://drupal.org/node/1172302

MacRonin’s picture

MacRonin commented

I figure the name was chosen to describe the function rather than show an affiliation.

The module itself creates a status display that is similar to the one Facebook has.

dilari’s picture

dilari commented

I suppose that's true and I understand, yet we don't call drupal a 'wordpress-like-cms' right?

moved to: http://drupal.org/node/1172302

@good_man (#45) : yep, done.

good_man’s picture

good_man commented

@dilari: can you keep this issue to it's purpose and move your suggestion to another issue?

good_man’s picture

good_man commented

@dilari, thanks a lot ;)

nikkubhai’s picture

nikkubhai commented

@Isaac: What should we do with the github branches of D7 created by some of the users above? Should we try them? Will they be used while you make your D7 port?

Michael3185’s picture

Michael3185 commented

Re the original title; "Port Facebook-style Statuses to D7"... An essential port, of course, but I hope the D6 version is coded to perfection before development goes 90% to a D7 version.

Many site developers won't be changing to D7 for quite some time, me included. I've been an 'update' beta tester too many times in the past, and will only trust D7 when it's at least a year old and very well tested. Right now, D6 is a comprehensive playground with lots of nice toys.

rogical’s picture

rogical commented

to the members started from Drupal 6, you're very much right.

to the much crowd start from Drupal 7, it's a pity they still can't get such a nice module in the modern social world.

rorymadden’s picture

rorymadden commented

subscribe

timonweb’s picture

timonweb commented

subscribing

Anonymous’s picture

Anonymous (not verified) commented

>> Many site developers won't be changing to D7 for quite some time

Nope, my company has adopted D7 straight away and we are already launching high-scale community sites on it. Only thing lacking, D7 fb status microblog with heartbeat integration. Will work on that coming few days, see where I can help out.

D7 is worth an early adoption, because of stuff like fieldable comments (e.g. to create advanced review forms), fieldable everything, entity API, Search API module with Solr integration,... and much more amazing stuff that is completely lacking in D6.

Even D7 Groups module is fully fieldable, which is an amazing step ahead.

icecreamyou’s picture

icecreamyou commented

Re #47: I didn't write them and I haven't reviewed them. If you are upgrading, you probably shouldn't try them. If you are installing from scratch and just playing around on a dev site, it's probably worth trying them. I'm going to take a look at them when I start building the D7 branch but I'm not going to start from them.

Re #48: That's what I've been doing, and the 6.x-3.x branch is stable now. (I'm aware of some problems, but all software will always have problems, and some of them will get outweighed by the D7 port.) FWIW, my time on the D6 branch is sponsored by Acquia, so it's much easier to put resources into it.

Now that the 6.x-3.x branch is stable, I'm trying hard to figure out when I will have the time to port the module to D7. I was hoping it would be this weekend but something came up. Next weekend is the 4th of July and I will be visiting my parents so I probably won't get much done. But hopefully I can start the following weekend, or maybe on weekday nights before that depending on what else is going on.

Anonymous’s picture

Anonymous (not verified) commented

@36 your 7.0-1.0-dev doesnt work, on enabling it the module-page gets into a never-ending loop and crashes with memory exhaustion (even at 512MB PHP memory). I only enabled the core module.

Drupal pages then show menu errors:

Notice: Undefined index: access in _menu_link_translate() (line 913 of C:\Inetpub\wwwroot\123.com\includes\menu.inc). =>

Notice: Undefined index: access in _menu_tree_check_access() (line 1446 of C:\Inetpub\wwwroot\123.com\includes\menu.inc). =>

The module page is broken and I have to manually disable the module in the system table.

Anonymous’s picture

Anonymous (not verified) commented

Ok, the menu errors are due to the devel_generate menu item,

  if (module_exists('devel_generate')) {
    $items['admin/generate/facebook_status'] = array(
      'title' => 'Generate statuses',
      'description' => 'Generate a given number of statuses. Optionally delete current items.',
      'page callback' => 'drupal_get_form',
      'page arguments' => array('facebook_status_generate_form'),
      'access callback' => '_facebook_status_generate_access',
      'file' => 'includes/utility/facebook_status.generate.inc',
    );
  }

This breaks. Removing this solved the problem.

Anonymous’s picture

Anonymous (not verified) commented

@#36 - status posts are not stored in the database,...

nikkubhai’s picture

nikkubhai commented

I hope to see the port soon now. :)

AquaticDisorder’s picture

AquaticDisorder commented

sub

rdoiron’s picture

rdoiron commented

Looking forward to using this on our new 7 site when it's ready.

halloffame’s picture

halloffame commented

IceCreamYou do you work on this module alone? Looks like it is the case.

Can we find another developer that you're willing to work with? I'm willing to sponsor another developer to speed things up. But I'm not gonna do it alone. Say we pool in some money from other willing participants and find someone. Would this be possible?

icecreamyou’s picture

icecreamyou commented
StatusFileSize
new facebook_status_to_d7.patch530.06 KB

I do work on this module alone.

I will review any patches that get posted in this issue until this issue is marked Fixed. Feel free to sponsor whoever you'd like. The attached patch is a diff from #36 to the current dev (a ton of changes have gone in to FBSS since the branch point of #36 from 6.x-3.x though). I am going to start by going through that patch by hand -- hopefully this weekend unless I get too distracted by some other awesome things I have on my to-do list.

Drake’s picture

Drake commented

+1

nikkubhai’s picture

nikkubhai commented

@IceCreamYou:
I wanted to say the say same thing as in comment 60. This issue was started on January 1,2010. Its more than 1 and half year !!! Still not even a dev version of 7.x has been ported. But, its not the case that you are not working. You have been working regularly and sincerely. I highly appreciate it.
I feel that the module now is too big to be maintained by a single person. Why don't you ask for a co-maintainer? There were some guys who helped earlier by submitting patches. But you niether responded them and nor reviewed or committed the patch. This is probably the only module which is actively maintained and has not got D7 version till date.

pillarsdotnet’s picture

pillarsdotnet commented

probably the only module which is actively maintained and has not got D7 version

That's a bit harsh, and provably untrue. Searching Drupal modules for "Actively maintained" yields 2972 results. Restricting the search to Compatibility: 7.x yields 1346 results So there are at least 2972 - 1346 = 1626 modules with the same problem. In other words, fewer than half of all "Actively maintained" modules have a D7 version, as of today.

EDIT: Searching for "Actively maintained, Under active development" yields 2495 and 1187, respectively. So even "Actively maintained, Under active development" modules are only 47% upgraded to D7.

icecreamyou’s picture

icecreamyou commented

Well "active development" is probably an overstatement for a lot of modules that are marked that way. However the main reason there is no D7 branch is because there is active development. D7 was released at an awkward time in FBSS's dev cycle when I was between 6.x-2.x and 6.x-3.x, and I chose to work on 6.x-3.x instead of porting 2.x to D7. So shoot me. Now we have an awesome and stable 6.x-3.x version that would not exist if I had to maintain two branches in parallel.

Why don't you ask for a co-maintainer?

The distinction between someone who submits a patch and a co-maintainer is that the co-maintainer can commit the patch. If there were any patches in this thread I would review and commit them, so there's no need for a co-maintainer. So far only pillarsdotnet has submitted a patch, way back in #16, and that was a straight run through Coder so there was really nothing to review.

FWIW, the D7 branch of FBSS is going to live at a different, as-yet-unannounced namespace, and publicmind (maintainer of the FBSMP module) will be co-maintainer because FBSMP is going to merge into the main FBSS package. He actually has less bandwidth than I do, but it will help.

nikkubhai’s picture

nikkubhai commented

@pillarsdotnet: By active development, I mean the module which is really being developed actively and not the one which has been just marked as. I am sorry if it seems harsh. Actually, I am a fan of IceCreamYou . See his commits; he commits almost daily and also responds to all the issues asap.

rogical’s picture

rogical commented

@nikkubhai, yes you may be a little harsh before, but I'm also quite agree with you on the new branch of D7 dev.

I'm a totally a D7 user, and always eager to see a D7 port of this.

A new D7 dev branch would let users to easilly track and submit issues, as well as patch operations, it will also boost the development progress, while we still talk all the porting issues here is not a good way.

dargno’s picture

dargno commented

eagerly awaiting further progress :)

originally i'm looking just to add comments to the user profiles, though this module will fit in pretty well either ...

Good luck on developing and i'd be happy to test any dev builds...

ryan.armstrong’s picture

ryan.armstrong commented

Same here. Thanks for all of your hard work IceCream

mefisto75’s picture

mefisto75 commented

sub

nikkubhai’s picture

nikkubhai commented

will it be done this weekend?

icecreamyou’s picture

icecreamyou commented

I hope so. It's the next thing on my to-do list. I actually have a note on my desk that says "Port FBSS to D7 ASAP" to remind me. But my parents are in town so I don't know whether I'll have an extended block of time to really get going on it.

icecreamyou’s picture

icecreamyou commented
Priority: Normal » Major

I hate to disappoint, but my parents visiting took up most of my time this weekend and I wasn't able to get going on this. I might be able to put some time in on nights this week. However it happens, this is a priority for me, and I am actively trying to make the time to get this to happen ASAP.

In the mean time, patches help! Even if it's just running the latest dev through Coder Upgrade, it means a little less time I have to spend on that.

d0t15t’s picture

d0t15t commented

can't wait!

capnjav’s picture

capnjav commented

Thanks @IceCreamYou for your ongoing efforts, its much appreciated... Looking forward to a drupal 7 port!

nikkubhai’s picture

nikkubhai commented

this weekend?

skottler’s picture

skottler commented
StatusFileSize
new facebook_status.patch315.23 KB

Just a quick update on the status of the migration. I've attached the patch generated by coder. I will be working with IceCreamYou this week to get rolling on porting to D7. We are going to map dependencies and then start to move over to D7.

Sylense’s picture

Sylense commented

sub

pumpkinkid’s picture

pumpkinkid commented

subscribing... Want to keep track and help out if I can.

dargno’s picture

dargno commented

Awesome some more progress :)

As soon as we have some kind of dev release i'd be happy to throw it against my dev site ...

icecreamyou’s picture

icecreamyou commented

Sam (skottler) and I are going to do a sprint today, starting sometime between 5 and 7PM EST. You are welcome to join in (even if you start before I get going) -- see http://fbss.icecreamyou.com/sprint-d7-port for instructions.

Fixdit’s picture

Fixdit commented

+1

ShadowMonster’s picture

ShadowMonster commented

subscribe

capnjav’s picture

capnjav commented

@IceCreamYou I'm working on porting Mentions to Drupal 7 (might even be a nice include for Commons) and want to ensure functionality with FBSS 7.x-3.x.

Will there be any likely changes to the naming of facebook_status_save() and facebook_status_delete()?

Can't wait for FBSS 7.x-3.x

ctalley5’s picture

ctalley5 commented

subscribing

Anonymous’s picture

Anonymous (not verified) commented

@77: why did you start from scratch? There was already a working D7 version at https://github.com/screamwork/Facebook-style-Statuses

I'm using this one on my site, only thing still broken was the Rules integration and some minor issues. Have succesfully integrated screamwork's package with Heartbeat for D7 as well.

icecreamyou’s picture

icecreamyou commented
Status: Needs review » Active

Will there be any likely changes to the naming of facebook_status_save() and facebook_status_delete()?

Those functions don't even exist in 6.x-3.x. :-P The functions you are looking for are facebook_status_save_status() and facebook_status_delete_status(). However in terms of Mentions, the related hooks are probably more useful.

why did you start from scratch?

Because there were about a bazillion-and-a-half changes since the branch point for screamwork's code, and that version also has a bunch of hacks in it including security vulnerabilities. It would have been more work to fix that version and bring it up to date than to start from where Coder Upgrade gets us and bring over the few useful fixes that screamwork added.

The current "official" port exists at https://github.com/IceCreamYou/Statuses. I have really only worked on the main module, and I would be surprised if Views integration was working, and frankly I'd also be surprised if AJAX was working -- and I haven't tested it, so there may be WSODs. In other words, it's not even worth trying to use it right now unless you want to help write patches. However, I will be actively working on this code, so if you are able please help! To get started follow the instructions at http://fbss.icecreamyou.com/sprint-d7-port

Once the main module is somewhat usable I will bring the code back to d.o.

zamir’s picture

zamir commented

+1

montchr’s picture

montchr commented

subscribing

damienmckenna’s picture

damienmckenna
Location TN, USA
commented
StatusFileSize
new facebook_status-d7_conditions.patch2.13 KB

IceCreamYou: here's a patch to fix some syntax problems with the condition() statements.

icecreamyou’s picture

icecreamyou commented

Thanks! Committed via nikkubhai's pull request.

skottler’s picture

skottler commented

IceCreamYou, do you want to start doing some merging from the pull request into the master? Its starting to get confusing about how patches are being managed - we also need a master that contains the most up to date changes, notes, patches, etc.

bcarroll28’s picture

bcarroll28 commented

sub

icecreamyou’s picture

icecreamyou commented

IceCreamYou, do you want to start doing some merging from the pull request into the master? Its starting to get confusing about how patches are being managed - we also need a master that contains the most up to date changes, notes, patches, etc.

What do you mean? D7 development of FBSS is at https://github.com/IceCreamYou/Statuses and there are no open pull requests or pending patches to be committed. The preferred development workflow is described at http://fbss.icecreamyou.com/sprint-d7-port

icecreamyou’s picture

icecreamyou commented
Status: Active » Needs work

Just so everyone is aware -- the D7 branch of FBSS is now located at the Statuses project. It's definitely not ready yet, but feel free to try it and open issues (preferably with patches!) in the issue queue.

Right now, only the main module has been ported; saving statuses via AJAX doesn't work (but you can use the module by disabling AJAX in the settings); and most of the custom Views handlers don't work. Assistance with any of that would be deeply appreciated.

pumpkinkid’s picture

pumpkinkid commented

SWEET! I hated that this module was called Facebook Style Statuses... Although I do understand why it was called that to begin with :-)

Thanks for the update!

skottler’s picture

skottler commented

Sorry about the previous comment, I didn't realize the original Git repo was not longer being utilized. I really wish I had more time to work on this.

icecreamyou’s picture

icecreamyou commented

I just tagged a second unstable release of Statuses (the FBSS D7 port). (Give it a minute if you don't see the new release -- Drupal.org has to generate the tarball first.) Saving statuses via AJAX now works for me, and comments at least work with AJAX disabled (haven't tested them with AJAX enabled). No integrations (i.e. most submodules) have been ported except Views, and several custom Views handlers are broken. Please test, report bugs, and post patches if you can!

ezra-g’s picture

ezra-g commented

To facilitate wider testing, perhaps it would be worth adding the D7 development snapshot to the project page :).

ezra-g’s picture

ezra-g commented

...Unless we're supposed to be using https://drupal.org/project/statuses ;).

skottler’s picture

skottler commented

@ezra-g the statuses project is the new home of the former Facebook-style statuses project :P

pillarsdotnet’s picture

pillarsdotnet commented
Title: Port Facebook-style Statuses to D7 » Port Facebook-style Statuses to D7 Statuses
Project: Facebook-style Statuses (Microblog) » Statuses (Social Microblog)
Version: 6.x-3.x-dev » 7.x-1.x-dev
Component: Code - API » Miscellaneous
icecreamyou’s picture

icecreamyou commented
Project: Statuses (Social Microblog) » Facebook-style Statuses (Microblog)
Version: 7.x-1.x-dev » 6.x-3.x-dev

Moving this back to FBSS -- it's not Statuses that needs upgrading. :-) The FBSS queue is where people look for an issue on upgrading FBSS to D7. The Statuses queue is where issues should be posted about things that haven't been fixed in the port yet.

icecreamyou’s picture

icecreamyou commented

FWIW, #1263952: Make sure the recent theming changes look good in standard use cases is the last issue blocking the 6.x-3.0 release. Once the changes from that issue are ported to D7, I will consider the base module and the status comments module stable, so I'll release an alpha and close this issue. Help with this is appreciated as always...

icecreamyou’s picture

icecreamyou commented

#1263952: Make sure the recent theming changes look good in standard use cases has been committed and now needs to be ported to D7. Once it has been ported I will release an alpha. There are two other blockers to a stable release: #1255648: Rules integration is broken and #1296238: calls to flag_get_flag('follow')->fid or ->status fail. Help with these issues is appreciated!

icecreamyou’s picture

icecreamyou commented
Status: Needs work » Fixed

I put out a new unstable release so I'm marking this issue fixed. The D7 version isn't production-ready yet but the core modules seem to be stable.

Status: Fixed » Closed (fixed)

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