PubwichFork is an open-source PHP web application that allows you to aggregate your published data from multiple websites and services into a single HTML page.
PubwichFork is an improved version of the original Pubwich application, since Pubwich is not actively maintained anymore by the original author. PubwichFork fixes several bugs and enables filtering of the data streams.
If you need to upgrade from your current Pubwich(Fork) install, please check the upgrading section in this file.
Installing PubwichFork 2.9+
Get it from the repository and change to development branch:
$ git clone https://github.com/haschek/PubwichFork.git $ cd PubwichFork $ git pull
Install necessary vendor libraries, you need to install Bower before you can use it for that step:
$ bower install
Change the permissions on the cache directory to make it writeable for for you and the user group of the webserver, e.g. on Ubuntu:
$ sudo chown youruser:www-data usr/cache/ $ sudo chmod ug+w usr/cache/
It may be easier to allow writing to all (777) but this is not recommended for security reasons.
usr/configuration/config.php. (Optional: if you want to use a custom theme, duplicate
usr/themes/your_theme_nameand edit the
Edit the newly created config.php to fill the blank spaces with your informations (API keys, usernames, site’s URL, etc.) and to modify the arguments passed to
Pubwich::setServices(). See the Service configuration section of this file or read the Service Class manual.
Everything should be working now.
Currently we have 3 different Pubwich(Fork) development branches:
1.x: the first official Pubwich application, the last official release was Pubwich 1.5 - Pubwich is not maintained anymore since 2011
2.1: May 2011 Pubwich was forked, community commits and fixes were merged in, and it was extended (e.g. adding filters and improved caching options, responsive default theme). Around 80 commits were made since then. The current stable release is PubwichFork 2.1
2.9+: the current version, an intermediate release to
3.xthat is not finished yet. Nonetheless, it includes a lot of changes: project folders were restructured, usage process of vendor libraries was changed, the template system has been improved and the default theme is updated and mobile first now.
Upgrade from Pubwich 1.x to PubwichFork 2.0 and 2.1
Last official Pubwich release was 1.5., please remember that important changes were made in Pubwich 1.4., e.g. Twitter OAuth support and the new template engine. Please check the old Pubwich manual about upgrading if you are still using a Pubwich install before version 1.4.
Upgrading from Pubwich 1.5+ to PubwichFork 2.1 should be simple:
cfg/config.phpand your customized user theme.
Install PubwichFork and re-configure it, using your configuration backup.
Copy your theme folder to
Usually your old config file and user theme should work with PubwichFork. If not, please report bugs.
Upgrade from PubwichFork 2.1 to 2.9+
Backup your PubwichFork installation.
Install PubwichFork 3.x and copy your configuration backup file to
Copy your theme folder to
If you developed own service classes, copy them to
PubwichFork 2.9+ is compatible to configurations and filters from 2.1. The old template system is now deprecated but it is still supported in 2.9+
All services are configured in the
config.php file, usually a service
looks like this:
array( 'Flickr', // service name 'photos', // service id array( 'method' => 'FlickrUser', 'title' => 'Flick<em>r</em>', 'description' => 'latest photos', 'total' => 16, 'key' => '________', 'userid' => '________', 'username' => '__________', 'row' => 4, ) )
In this example
Flickr is the service name,
photos is the
service ID and the inner array is the service configuration. Some
parameters can be used for all services:
title→ box title
description→ box description
total→ number of items to display
cache_limit→ cache invalidation time in seconds
The simplest and wide supported
Feed service can be configured by
url→ URI of the feed
link→ the URI of the website the feed is used for
There are several other service classes, e.g. for Facebook, Twitter, Youtube, Vimeo, Flickr, Reddit, GNUsocial and more. For further info please read the Service documentation.
Custom themes and templates
Themes contain all main and sub templates for page chrome, layout containers,
channel boxes, list items; and the public graphics and stylesheets for the
layout. Your theme folder must be in
All templates are written in simple Mustache syntax, all main and sub
templates are in
yourtheme/templates folder, using
.mustache as file
For further information please read
the manual about how to develop custom themes and user templates.