Fork Meetup 26/03/2015

the public

Yesterday, thursday 26 March 2015, we finally organized another event. The previous real event was somewhat about 2 years ago. This meetup was Symfony-flavoured, as many people wanted an update about the move towards Symfony. So yesterday we gathered in the Combell-offices in Ghent, to talk about Fork and Symfony. We had one intro-talk and two "real" talks:

  • Update on Fork and the Symfony integration by Tijs Verkoyen
  • Effectively using the Symfony Components in Fork by Wouter Sioen
  • Having fun with the Symfony Container by Bram Van der Sype

Update on Fork and the Symfony integration

Tijs talked briefly about which components are already integrated into Fork and the future. The future will hold more meetups, more Core members, more ... So if you are interested in participating as a Core member, send us an email (info [at] fork-cms.com).

See https://joind.in/14294 for the slides.

Effectively using the Symfony Components in Fork

Wouter talked about how you can use some of the components already available in Fork in more detail. He explained Routing, DependencyInjection, Console, EventDispatcher. And last but not the least he discussed the Functional tests.

See https://joind.in/14182 for the slides.

Having fun with the Symfony Container

bram talking about the DIC Bram, who works at SparkCentral, showed us some nice tricks with the Symfony Container: tagging and Compiler Passes. It showed us some features most of us didn't know about, but will be handy in the future development of Fork.

See https://joind.in/14183 for the slides.

 

We would like to thank all the speakers: Wouter, Bram and Tijs, and Combell for sponsoring the location, drinks and food. If you would like to keep up with new announcements for events you can check our MeetUp-page.

Read More

New GitHub labels

You may have noticed that we cleaned up the labels we use for issues/pull requests on GitHub. We now follow the same structure as the Symfony repository.

Read More

Using SwiftMailer in Fork CMS

Since our 3.9 release, all mail communication runs through the Swiftmailerbundle. This is the officially supported way of sending mails through Symfony. It's  based on the widely used and well documented library Swiftmailer.

Read More

Forkathon: introducing tests!

  • Written by Tijs Verkoyen on Saturday 28 February 2015
  • 2 comments

At 26 february 2015 Wijs and Sumocoders teamed up to work a full day on improving Fork CMS. We gathered in a room and started coding, some developers paired to fix issues, others reviewed the Pull Requests, while other were integrating tests!

Yep, finally! We introduced tests, most of the test are functional tests as Fork CMS isn't ready for real decent unit-tests. Therefore we will have to refactor a lot of code, but the functional tests are a real nice start, and will enable us to refactor more code.

Ofcourse this resulted in a lot of changes, well some statswe merged 22 pull request and closed a lot of issues. In the upcoming week we will release Fork CMS 3.9 which will include all these changes!

PS: vytenizs is working hard to integrate Twitter Bootstrap in the backend, take a look: https://github.com/forkcms/forkcms/pull/1077.

Read More

Sitelinks search box

Since our 3.8.5 release, we've added a nice new feature for the marketing focussed sites build on Fork CMS. Google's Sitelinks Search box has been added. This snippet makes sure users will be able to use the search functionality from your Fork CMS website in the search results from Google itself.

Read More

Input wanted: Changing a profile's password

  • Written by Dieter Wyns on Wednesday 28 January 2015
  • 5 comments

Our core technical people have a meeting each month to discuss new implementations, merge pull-requests and view open issues. Last meeting in December, while reviewing the pull-requests we came across an implementation of Jeroen Desloovere about notifying profiles, see #971.

His changes would affect the way you can edit profiles in the backend. It adds new settings which allow an admin and the profile to get notified when a profile changes. A nice new feature!

During the review we stumbled into a new discussion about the functionality of changing passwords of a profile in the backend. Some argued it would be enough if you could reset a password. In this way the administrator would never know the password of a profile which is a very nice security principle.

What do you think, should an administrator be able to edit a password? Or just have the ability to do a reset?

Read More