I stopped using this module several months ago. I enabled it today to review some of the db content that had been added so I could pull it out and reformat as needed. Although I loved the look of the module, and the effort that obviously went into building it, I could not overcome the mountain of bugs and errors I encountered trying to implement it.

I am going to disable the module again so this post is for information only as I will not be able to troubleshoot.

I happened to run a drush registry rebuild today and received the following warning:

A file has been declared in a module's .info, but could not be found.[warning]
This is probably indicative of a bug. The missing file is
sites/all/modules/fbsmp/fbsmp.rules_defaults.inc.

PS: command run was: drush rr

After struggling with this module for months, I decided to build my own content type for facebook style status wall updates. I used a content type, embedded the node/add form in a panel on the user account page (/user) and created various views, customized comment template php wrappers, Rules and specific visibility settings to recreate all the functionality I was getting from this module, with none of the "issue queue" problems. Even with all that, the look and feel of this module is still superior, if you can get it functional.

If anyone needs assistance let me know.

Comments

IceCreamYou’s picture

Project: Statuses (Social Microblog) » Facebook-style Micropublisher
Component: Integrations » Code - API

Moving to FBSMP

FWIW, there are typically two main issues you'll find with using nodes as status updates: lack of support for AJAX updates, and all the various overhead associated with nodes. But really if you can get AJAXiness to work (which is not a small problem) it shouldn't be super different.

Anonymous’s picture

I am using Ajax comments with views. I made the node/add form available in a separate view and just show both views on user/%1. Various visibility rules and relationship views round out the facebook wall functionality.

The ajax comments module works well and replicates the auto grow comments function. That having been said, replicating the look and feel of this module is extremely difficult and time consuming. I would much prefer to just have used it, but the issue queue is simply too overwhelming for use in a production site. I was constantly running into errors and bugs. I hope you are able to find a new maintainer, as I feel this functionality is critical to any Drupal social networking site, and other than build your own solution, this is the only module.