PHPackages                             markguinn/silverstripe-fb-comments - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. markguinn/silverstripe-fb-comments

ActiveSilverstripe-module

markguinn/silverstripe-fb-comments
==================================

Really simple FB comments for Silverstripe.

51501[1 issues](https://github.com/markguinn/silverstripe-fb-comments/issues)PHP

Since Feb 18Pushed 10y ago1 watchersCompare

[ Source](https://github.com/markguinn/silverstripe-fb-comments)[ Packagist](https://packagist.org/packages/markguinn/silverstripe-fb-comments)[ RSS](/packages/markguinn-silverstripe-fb-comments/feed)WikiDiscussions master Synced 1mo ago

READMEChangelogDependenciesVersions (1)Used By (0)

Simple Facebook Comments Module
===============================

[](#simple-facebook-comments-module)

A really simple module for adding Facebook comments to a silverstripe site. There are probably better ones out there, but this is meant to get you up and running in 5 minutes or so.

INSTALLATION:
-------------

[](#installation)

1. Create an app in the fb developers area.
2. Either 'composer require markguinn/silverstripe-fb-comments' or download from github into an 'fb-comments' folder in your site root.
3. Either install 'tractorcow/silverstripe-opengraph' module (recommended) or add an 'OGApplicationID' method to SiteConfig with your fb application ID. If you do the former, you'll need/want to add $OGNS to your html tag and probably set OpenGraphObjectExtension::$default\_image in \_config.php.
4. Add 'FBCommentsExtension' to BlogEntry or Page (or whichever classes you want comments available). Probably something like:

```
BlogEntry::add_extension('FBComments');

```

4. Add the following just after the opening body tag IF you're not already including the FB API for something else (like buttons, etc):

```

```

5. Add the following where you want comments to show up:

```

```

CONFIG OPTIONS:
---------------

[](#config-options)

The following configuration options are available on FBComments:

- num\_posts - The number of comments to show initially. Default is 3.
- comment\_width - The width of the comment area. Default is 600
- color\_scheme - See FB documentation for details. Default is light.
- notify - list of email addresses to notify if there's a comment
- notify\_from - address from which the notification should come
- notify\_subject - subject of the notification email

By default, there is no notification when a new comment is posted, but if you set a list of addresses, the plugin will send an email to those people.

SAMPLE CONFIG FILE
------------------

[](#sample-config-file)

```
---
name: 'fbcomments'
---
BlogEntry:
  extensions:
    0: 'FBComments'
FBComments:
  num_posts: 10
  comment_width: 600
  color_scheme: light
  notify:
    0: 'mark@adaircreative.com'
  notify_from: 'noreply@yoursite.com'
  notify_subject: 'New comment on yoursite.com'
---

```

DEVELOPERS:
-----------

[](#developers)

- Mark Guinn -

LICENSE (MIT):
--------------

[](#license-mit)

Copyright (c) 2013 Mark Guinn

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

###  Health Score

22

—

LowBetter than 23% of packages

Maintenance16

Infrequent updates — may be unmaintained

Popularity16

Limited adoption so far

Community5

Small or concentrated contributor base

Maturity41

Maturing project, gaining track record

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://www.gravatar.com/avatar/485dfc9fc93cad085c83c3276f19b6e9322ee910ab0e1685de0db42228dbf97b?d=identicon)[markguinn](/maintainers/markguinn)

### Embed Badge

![Health badge](/badges/markguinn-silverstripe-fb-comments/health.svg)

```
[![Health](https://phpackages.com/badges/markguinn-silverstripe-fb-comments/health.svg)](https://phpackages.com/packages/markguinn-silverstripe-fb-comments)
```

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)