In november 2019, publiq vzw (formerly known as CultuurNet) starts the End of Support phase of the Culturefeed Drupal 7 module suite. This means that you can continue to use Culturefeed, but publiq vzw will not invest anymore in this Drupal 7 module suite.
As an exception, critical security updates will still be provided if needed.
The End of Life (EOL) date of the module suite is set to the same date as the EOL of Drupal 7 core, ie. November 2021 (https://www.drupal.org/psa-2019-02-25).
We built this final 4.0 release, which contains a major security update, and some incompatible changes compared to the latest 3.10.2 release. Some less used modules are moved to a separate repository. If you update to this version please check & should you use one of these modules, reinstall them from a separate repository. After that all things should work as usual.
-
https://github.com/cultuurnet/culturefeed_pages [DEPRECATED]
-
https://github.com/cultuurnet/culturefeed_roles [DEPRECATED]
-
https://github.com/cultuurnet/culturefeed_messages [DEPRECATED]
-
https://github.com/cultuurnet/culturefeed_calendar [DEPRECATED]
-
https://github.com/cultuurnet/culturefeed_userpoints_ui [DEPRECATED]
-
https://github.com/cultuurnet/culturefeed_entry_ui [DEPRECATED]
As an alternative for the Culturefeed Drupal 7 module suite, publiq vzw focused on:
-
A new, easy to use API in a developer-friendly Json format: https://projectaanvraag.uitdatabank.be/#!/integrations#api
-
An even easier to use widget platform: https://projectaanvraag.uitdatabank.be/#!/integrations#widgets
We also have a Drupal 8 version on https://github.com/cultuurnet/culturefeed_d8 with the most commonly used modules culturefeed_agenda, culturefeed_content, culturefeed_search, culturefeed_search_api and culturefeed_user.
However, these modules will not contain the full functionality as was provided in the Drupal 7 edition, and it will not be heavily extended by publiq the same way we did this for the Drupal 7 edition. We are still happy to review and accept pull requests from external developers or partners, though.
Drupal module suite for building an event site based on events gathered in an external backoffice "outdatabase" (UiTdatabank), but with the extra tools you can do a lot more. For this version you can only use it having a key and secret from the UiTdatabank or use the demo key from this page.
Live demo connecting production API only available from 7:00 till 20:00 (Brussels timezone)
Live demo connecting acceptance API only available from 7:00 till 20:00 (Brussels timezone)
Important note |
---|
Since the culturefeed 3.6 release PHP v5.5 is the minimum requirement and also the PHP INTL extension is needed. To install the extension on your system take a look at this blogpost. |
When you start with a clean Drupal install or just for setting up a quick demo site we created a Drupal install profile ("Installation profiles provide specific site features and functions for a specific purpose or type of site distributions"). This included also a shell script (Build.sh) which downloads:
- drupal core (at the moment 7.56)
- drupal contribs (bootstrap 3.0)
- culturefeed
- culturefeed_bootstrap
- vendor/cultuurnet/cdb
- vendor/cultuurnet/auth
- vendor/cultuurnet/search
- vendor/cultuurnet/culturefeed-php
- vendor/cultuurnet/calendar-summary
- vendor/cultuurnet/sitemap-xml
- lessphp
Prerequisites:
- php > v5.5 and the php intl extension (see important note above)
- git installed
- drush installed
- composer installed (http://getcomposer.org/doc/00-intro.md#downloading-the-composer-executable)
Place the module suite in your sites/*/modules folder, you can do this with GIT or download it here.
git clone https://github.com/cultuurnet/culturefeed
Afterwards copy the composer.json file from the root of the module suite to the root directory of your Drupal. If you use already composer.json you have to add the required libraries.
{
"name": "cultuurnet/culturefeed",
"type": "drupal-module",
"description": "CultuurNet culturefeed Drupal module",
"license": "Apache-2.0",
"require": {
"composer/composer": "~1.0",
"mobiledetect/mobiledetectlib": "dev-master",
"cultuurnet/search": "~1.2",
"cultuurnet/cdb": "~2.1",
"cultuurnet/culturefeed-php": "~1.6",
"cultuurnet/calendar-summary": "~1.0",
"cultuurnet/sitemap-xml": "~1.0"
},
"require-dev": {
"phing/phing": "~2.10"
},
"minimum-stability": "dev",
"prefer-stable": true
}
After that run composer install
or composer update
if already using composer. This will download our libraries and add a theme to a vendor directory. It will also create a composer.lock file. Typical we add vendor/* to the .gitignore file.
Last step is to include autoload.php in your settings.php file of your site.
require 'vendor/autoload.php';
You should now be able to enable the modules (typically you start with culturefeed, culturefeed_ui, culturefeed_search, culturefeed_search_ui and culturefeed_agenda) and fill in your key and secret:
- culturefeed core at admin/config/culturefeed/api-settings
- if culturefeed_search enabled also at admin/config/culturefeed/search
It's a good practice to connect your user/1 (admin) user with a UiTID account:
- Log in as user/1
- Go to culturefeed/oauth/connect and login to UiTID.
If this works culturefeed core is configured well. And if you get results at the path agenda/search culturefeed_search is working as well.
We created 3 tutorials to integrate the most common use cases:
Most of the modules have an dependency on these PHP libraries. See "Install" how to install theme with composer.
###CultuurNet\Cdb Fluent PHP library for manipulating, serializing and deserializing data present in CultuurNet's CdbXML 3.2 or 3.3 format
https://github.com/cultuurnet/cdb
###CultuurNet\Search Php library for creating SOLR queries (basic SOLR queries and custom business logic)
https://github.com/cultuurnet/Search
###CultuurNet\Auth The consumer-side of the authentication flow of CultuurNet's UiTID, which is based on OAuth 1.0a Core solid base for consumers of various OAuth-protected resources provided by CultuurNet
https://github.com/cultuurnet/Auth
###CultuurNet\CultureFeed-PHP Integration of all UiTID API calls.
https://github.com/cultuurnet/culturefeed-php
###CultuurNet\calendar-summary The calendar-summary PHP takes a CultureFeed_Cdb_Data_Calendar object (hence the dependency on cultuurnet/cdb, and formats it. Right now there's a HTML formatter and a plain text formatter. Current options: 'lg' (for permanent events only this option is available), 'md', 'md', 'sm', 'xs'.
https://github.com/cultuurnet/calendar-summary
###CultuurNet\sitemap-xml-php PHP library for writing sitemap XML conform with the sitemaps.org schema. Example see http://www.uitinvlaanderen.be/sitemap.xml. Only needed when you turn on the culturefeed_sitemap module.
https://github.com/cultuurnet/sitemap-xml-php
Culturefeed Bootstrap is the only supported and recommended base theme for Culturefeed. It's a responsive subtheme of the Bootstrap Framework and has it's own subtheme to start from. But of course you can implement Culturefeed in your prefered theme as well.
https://github.com/cultuurnet/culturefeed_bootstrap
Please enable only the modules you need.
Core of the module suite and is required by the other modules. It provides the settings form where you can enter the API Information.
Base framework to enable searches on your site. Out of the box this module doesn't provide any interface elements (use Culturefeed Search UI and Culturefeed Agenda instead). It provides some drush commands and caching.
Provides a Culturefeed search page available on 'agenda/search' and detail pages. The blocks provided by this module can be used to extend the detail pages of events, actors and productions. Includes also a simple search form.
Basic elements to build up an event search (such as provided by Culturefeed Agenda).
- Basic search form with type selector in the front (can be extended)
- Sort block
- Active filters
- Facets
To integrate a search page we also wrote a tutorial.
Views integration to list events, actors or productions. To create culturefeed views, create a new view and configure it to show Cdb items. Once the view is created, following handlers can be set:
- Fields
- Filters
- Sort
This module logs every query to our API, on the screen for admins or to the watchdog. Handy tool to check which is the performance killer, your Drupal install or our API's.
Functions to do a CRUD on events are already in library, but we are building a form to create, update and delete events in our UiTdatabank as well.
User can create a page (locations, performers, families, schools, …) or become member and follower.
Wiki page not yet available
Provides a collection of pages and blocks to enhance the user pages with UiTID information. To do this it will override and/or enhance the default Drupal user pages. Some features:
- edit profile page
- edit account page
- search users page
- caching
- teaser (formerly connect)
- most active user
- login (formerly profile box)
- profile menu
- e-mail confirmation reminder
- search users
- profile summary (formerly My UiTiD)
To integrate UiTID we also wrote a tutorial.
All ‘social’ features: likes, comments, attends, etc.
Integration with the UiTPAS card system. It contains multiple pages and blocks that can be used to build an interface that allows:
- easy access to the advantages and promotions a passholder has access to,
- possibility to register your UiTPAS,
- highlights of promotions and actions.
To integrate UiTPAS we wrote a tutorial.
To create mailings with search results from event (based on lifestyleprofile, Vlieg weekendflash, …). Not yet available for partners. Please contact us if interested.
Send messages to other users (most likely page owners), interesting when actors become pages.
Collect on line userpoints (for specific actions like writing reviews) and claim promotions (Vlieg). Not yet available for partners. Please contact us if interested.
Pre-assign roles to UiTID users that have not logged in yet. Drush integration.
UiTkalender functionality not yet released on UiTinVlaanderen (some extra features are going to be added in next release)
Adds a CultureFeed content field to add a search query to any of your content types.
With this functionality your user can save a search and create alerts from it.
Creates a sitemap for events, productions and actors, see example http://www.uitinvlaanderen.be/sitemap.xml.
There already a lot of integrations live on the 3.x version (and still counting):
- http://www.uitinvlaanderen.be
- http://www.uitinmechelen.be
- http://www.uitinsint-niklaas.be
- http://www.2014-18.be
- http://agenda.hbvl.be
- http://agenda.gva.be
- https://www.uitpas.be
- https://www.muntpunt.be/agenda/search
- http://www.starttoswim.com
- http://www.cultuurkuur.be
- http://www.uitmetvlieg.be
- http://agenda.besteburen.eu