The cookie bar

There is a lot of discussion about the European Cookie Law. Where each country has his own implementation it isn't that easy to find a way to handle them based on the country, because it doesn't only depend on the country per user, it depends on who you target.

Therefore in the upcoming 3.7-release we implemented the most strict cookie law, which should fullfill for all countries.

How it works

A cookie bar is available in the template (you should include it in your custom theme). The cookie bar is visible the first time a visitor enters the website, when he hasn't a functional cookie set to hide the bar.

When the visitor hasn't a cookie (cookie_bar_agree) set all tracking is disabled and the data send to Google Analytics is anonymised.

When a user clicks he disagrees a functional cookie is set to hide the cookie bar, and a cookie (cookie_bar_agree) is set to false. The cookie bar will not be visible from then on. When this happens no tracking is done, and the data for Google Analytics is anonymised.

When a user clicks he agrees the same the cookie for hiding the bar is also set, and the cookie_bar_agree-cookie is set to true. From then on the cookie bar will not be visible, the Fork-tracking is enabled and the data for Google Analytics isn't anonymised anymore.

Consequences

  • The first visit of a user will always be anonymized.
  • If a visitor doesn't allow cookies, the visitor will be unique for each request.

CommonCookie::hasAllowedCookies()

This method returns if a visitor has allowed the usage of cookies. If you are using tracking-cookies in your own code, you should use this method to check if it is allowed.

Read More

Tip: Hidden actions

Some modules in Fork CMS have backend actions that are not visible in the menu. These are functions you don't need for regular website management but can come in handy when doing specific tasks. You access these actions by directly entering the url in your browser's address bar.

Read More

Welcoming our GitHub Moderator: Jeroen Desloovere

Next to our forum moderator we would like to introduce Jeroen who will follow up the GitHub issues and pull-requests. In this way we would like to improve the response time on incoming bug reports. He already started with tagging the current open issues and introducing a new tag: Discussion required. Whenever this tag is assigned the issue will get discussed during the next technical meeting.

Jeroen works as PHP Web Developer at a Belgian communication agency Siesqo, they chose Fork CMS as their preferred CMS and regularly contribute back. But also after work hours Jeroen is an active community member. Hardly a day goes by without him having an open pull-request ready.

Follow Jeroen on Twitter or GitHub via siesqo and deslooverej.

Read More

Welcoming our first moderator: John Poelman

Last week we introduced our integrated forum which made it possible to gain support, manage extensions or contribute with only a GitHub account. A new group of moderators will help us to maintain the forum and improve support to new Fork CMS members. As first member of the group, meet John Poelman!

John is a well-known Fork CMS community member and with more than 350 replies one of the most active members of the old forum. Two years ago he made his first pull-request and didn't stop since.

His side project Instathals shows already 386 instagram photos of his hometown Herentals. On his blog - based on Fork CMS off-course - you'll find a variety of technological articles, visit at bloobz.be. Follow him on Twitter and GitHub.

Read More

New integrated forum

A few new users warned us that their forum topics didn't show up on the forum like they were supposed to. Besides, new users needed to register for another account just to ask a question. That's why we integrated a new forum into our support section. You can now report bugs, contribute code / documentation / translations, discuss, ask questions, comment or manage your extensions with only a GitHub account.

The next step is moving all discussions from the old forum to the new one, until the move is complete the old forum will still be accessible. The forum module will also be open-sourced later on.

Fork CMS support screenshot

We hope you'll find all the answers you need on our renewed support section. If not, ask around on the new forum!

Read More

Profiles on fork-cms.com

  • Written by Dieter Wyns on Thursday 31 October 2013
  • 3 comments

By far the most important factor of an open-source product is the community. The people behind a project bring innovation, durability, maintenance and great features. Therefore it's important that their vision and ideas are reflected onto a public dashboard.

Fork-cms.com profile example

With Profiles we take a first step on showing the faces behind Fork CMS. For now, your own profile allows you to share your Extensions and Showcase items into a centralised list. The functionality will expand over time, with a truly transparent platform as end goal. To maintain control and guarantee the same level of quality we review each entry.

Along with the profiles comes the ability to subscribe to our new newsletter. Again, we want to focus on quality. The subscribers will receive an email when a major version is released or other significant updates.

Stay tuned!

Read More