For silverstripe-opengraph, I will check and implement it in my code.
All the functions I want to add in the frameworks will be used in the
development process, so it will be more efficient to write them in a way
that it will be reusable by others, so the creation of the new Facebook api
will not take a lot of time.
For the technical details:
Corn job is a good idea for pulling in facebook updates, but it needs to
be in Linux server .
Sending the updates to facebook
- for the first policy(a content<=> a statue) Updates in the website
would be available in Facebook as soon as it's approved and appeared
in the website: the content with the comment will be send to facebook in
- for the second one, approved update will be available in facebook
when the period of updating is finished by using
1. corn job or schtasks for windows with a periodic update.
2. Every time a user enters the website, we check when is the last time
we made a successful update. If the period was exceed, we send all
updates to facebook from the website.
Getting the updates from facebook
To handle that, The admin choose between tow options:
- Before a user try to enter a page or add a comment.., we do get all
the updates related to the content
- when admin enter control panel , we do a full update
*The following facebook contents: text (link , stream )photos, and videos
will be supported.*
More New functions:
- For each content , we get the number of likes and of shares, and the
admin is able to show them or not
- The admin is able to set the policy, if he want he could let the
content author choose how to publish the content in facebook: that means
as text(link , stream, location )photos, and videos.
- He could also choose if it will be possible to the content author to
publish a content only in facebook and not in the website(it's better then
giving them a direct access to the Facebook page.This content could be then
updated or deleted from website control panel
- If it's possible for content author to choose publish mode, he will be
able to choose between text(link , stream,, location ) photos, and videos.
For photos its possible to choose the photo, for video , it's possible to
upload the video in facebook before submitting the content , after the
video is uploaded he could insert the video in the content .If the content
other didn't have the permission to write directly in the website, we
upload the video or the image in temporary folder and when they
are approved, they appear in facebook.
- The admin could set the policy for handling the facebook comments
: whether it will need the get approved or not to be published in the
New functions for the facebook api
- new function for the api to get number of shares and of likes
- functions for handling video,image , link , stream
1. April 30 – May 20 : Checking the Coding guidelines, Installing
development environment, Reading and understanding deeply the
source,Discussing with mentors about the final details of the project,
2. May 21 – May 23: Defining the changes needed in the database
3. May 24 - July 13: Adding new functions in the silverstripe front end
4. JULY 13
5. MID TERM EVALUATION Dead line
6. July 13 – August 6:Adding new function to the control panel
7. August 6 – August 12:Collecting the functions used and adding them to
8. August 13-August 20: Testing the new version of silverstripe, Writing
The new version a the cms wtih Facebook integration
The new api , with a documentation
Do I need to make a mid term deliverable?
2012/4/3 xeraa <P.Xe...@gmail.com>
> Hi Riadh,
> I think that the silverstripe-opengraph doesn't have the some purpose of
>> my new facebook api(I will forget about twitter).
> No it doesn't, but it might come in handy, as it wraps (at least part of)
> the Facebook API in SilverStripe. It's up to you how you want to approach
> this, but we're obviously striving for new functionality and not redoing
> existing one.
> What I want is to create functions that could be used to implement the
>> new cms Facebook feature in framework:
>> Basically, I will create the follwing functions
>> - get one or many the statue, and all the comments of a statue , get
>> the information about the user that added the comment or the statue
>> - adding new set functions : function to add statue ,update statue,
>> delete statue, add comment , update comment and delete comment
>> - in api facebook if you want to comment a post , you will need the
>> post id, and because in the most time we want to synchronize the website
>> and the facebook page, a new set of funtions wil be available for creating
>> updating and delete post and comments with the content id in the cms(
>> withoot converting each time the content id to the cms id)
> Ok, this sounds reasonable, but could possibly be expanded further. For
> example with technical details (information from FB is pulled in via a cron
> job, information is pushed to FB via a post-commit hook,...) as well as
> deliverables (which FB content types should be supported, on what content
> types do we want to provide FB comments,...).
> I'd love to see a schedule (I'll do XXX in the first week, YYY in the
> second week,...), so we can get a better picture of the overall project and
> the deliverables. And please keep the mid-term evaluation in mind.
> You received this message because you are subscribed to the Google Groups
> "SilverStripe Core Development" group.
> To view this discussion on the web visit
> To post to this group, send email to firstname.lastname@example.org.
> To unsubscribe from this group, send email to
> For more options, visit this group at