Téléchargement
Démosphère est un logiciel libre et gratuit (sous licence AGPL V3)
Le code de Démosphère progresse continuellement.
Contactez-nous si vous avez besoin d'aide pour l'installer et pour le configurer (contact [at] demosphere (.dot.) eu). Nous pouvons également vous soutenir et héberger votre projet si vos objectifs politiques sont proches des nôtres (voir www.demosphere.eu).
Téléchargement
- image du code source mise à jour quotidiennement : demosphere.tar.gz
- extension Firefox : demosphere-ffox-extension.xpi
Recent changes
.
Oct 11, 2011
Mobile: mobiles (smartphones) will see a simplified mobile-freindly version.
Many small bug fixes. Upgrading tinymce. Adding microdata schema.org
July 27, 2011
Image Zoom: images that have been resized to fit into the center or right columns can now be zoomed. The original (larger) image is shown in a popup. This is backwards-compatible with existing images.
Title on events pages. Many sites use two titles: 1) the long title, written for the front page and 2) a title at the begining of the text of each event. Front-page titles were re-displayed (small grey text) at the top of each event page. This looked bad. The frontpage title is no longer displayed on event pages. You can choose to change this in the configuration.
Editing non-event pages (story nodes): the editor has been fixed so that you can edit story nodes with all the features that you have in event pages (including document conversion).
Microsoft Internet Explorer 7&8 : the display of the frontpage on ie7 and ie8 has been improved. Unfortunatelly it seems that IE8 is going to be around for a long time...
July 18, 2011
Support for embeded videos (youtube and dailymotion)
To add a video use the "demosphere token" insert button that has been
added in the text editor.
Easier editing of the front page :
- "featuring" an event in two clicks
- simple editing announcements and messages in a text editor.
- direct links for changing topics, slogan ...
July 7, 2011
open street maps : It is is now possible to use open street maps (and others) on event pages. The software still uses google maps for interactive maps. This release comes with some other small changes and bugfixes (performance...).
July 1, 2011
There are no major new features, but a few bug fixes and small improvements.
Mail filtering: I noticed that the mail filtering (previously called mail rules) interface was not used much . I rewrote part of the interface. It now has many more explanations and is more user-friendly.
Public event form: several small bug fixes and enhancements. The management of attachments has been re-written.
Event display: I added an ical link so that visitors can easily add events to their calendar software.
Feed import: prettier default names for feeds.
Event editing: The "needs attention" field is now automatically updated for certain common cases, to avoid clicking twice.
Everywhere: better support for microsoft office docs: docx
May 23, 2011
Moderation workflow
Previously, events could be either published or not published. They could also be complete / incomplete and repetitions could be confirmed / unconfirmed. On the "pending events" page, you could also say that an event was waiting or rejected by adding things in its title.
This was fairly confusing and most groups did not use it.
The whole system has been re-written.
Events now have three new properties: "moderation status" and "needs attention" and "moderation message".
Moderation status can be:
- 'just created'
- 'waiting, not published'
- 'published, unconfirmed'
- 'published, incomplete'
- 'published'
- 'rejected, shown'
- 'rejected, hidden'
- 'trash'
Needs attention can be:
- ok
- needs attention level 1
- waiting publication request
- needs attention level 2
- new private event
- has been self edited
- published by non admin
- open published
- publication request
A new feature here is "rejected shown" category. This feature is optional, it is disabled by default. To enable it, go to the demosphere configuration (section: misc.). With this new feature you can display a page (and archives) that shows events that were rejected. Certain sites use this kind of page for more transparency on their moderation.
Another new feature here is "rejected hidden" category. These events will not be shown, but will be archived. Previously you had to manually delete rejected events, so they where lost.
Another new feature here is the "trash". Previously you could only delete events. If you made a mistake, your data was lost. Now, you can put events into the trash bin, and recover them. The trash bin will be automatically emptied after 7 days (not implemented yet... soon).
The new property called "Needs attention" is used to say that an event needs to be checked by a moderator. There are two levels. level-1 will just change the color (light red) of the event on the "pending events" page. Level-2 events will appear in red on the top of the "pending events" page. Needs attention is used for example, to show that an event is a publication request (submitted from the public form) or that an event has been self-edited.
The "moderation message" property can be used as a short reminder for moderators. You can write anything you want here. It will never be shown to non-moderators. You no longer need to add any moderation text to the title.
Pending events page, repetitions page
The pending events page ("list" on some sites) has been completely re-written. You can now directly edit events on this page. Changes will be immediately saved (you do not need to submit). Just click on the field you want to change. Currently, you can edit the following fields: moderation status, needs attention, dates, times, moderation
message, title.
The list of events on the repetition page also uses the same system.
event email: iCalendar attachment
When users send an email from an event, it now contains an attachment that is an ics (iCalendar) "invitation". If the person receiving the email has a calendar integrated into his email system, he will be able to add this event to his own calendar. The current works with with Thunderbird+lightning (sometimes) , evolution and gmail. It doesn't work on certain other systems. Please tell me if you find an email+calendar system where it does not work (I need the exact version of the system).
events featured on frontpage
You can now display important events on the top of the frontpage.
To use this, edit the event and check:
extra options->publication status->sticky on top of lists
May 4, 2011
Repetition management.
I have changed a lot of things in the management of repetitions: There no longer is a notion of a "reference" for a group of repetitions. Before, there was a reference and all repetitions where updated automatically when the reference was changed. Now, all repetitions belong to a group. When any event in that group is changed you can individually select which fields you want to update in all of the other repetitions.
The only place the "reference" is still used, is when you create new repetitions. New repetitions will be copies of the "reference". You can now select which reference you want to use.
Access to repetitions managers is now available directly through a tab, you no longer need to edit the event to get to the link.
You can now add events to a repetition group, after they are created.
Feed import.
I'm trying to make feed import more reliable, and also make it easier to fix broken feeds. The first step has been to improve error reporting. Now, broken feeds and broken articles display a complete description of the last error. xml (rss/atom) is now always cleaned-up (using tidy). That was optional before, the option was removed. All downloads now use curl instead of wget (internally, this is a big change). This allows for better error reporting.
The display of feeds was improved.
Comments
A few problems where fixed in the display and editing of comments. A simpler version of the tinymce editor is used (not the full backend form editor). Comments are now cleaned-up, and foreign images in comments are imported, to avoid privacy problems. IP addresses are displayed for anonymous comments in comments list (available from the panel). This helps identifying multpile posts from a single user (troll...).
Text matching diff
As for last month, I've worked on the display differences between similar documents. This is another complete rewrite. The previous version was way too slow. This code is much simpler.
wysiwyg / tiny mce
Upgraded to new version of both the drupal wysiwyg module and the tinymce editor.
demosphere_dtoken_copy_part
This is a bit complex, but can sometimes be quite useful. Please test it before you use it and contact me for a more detailed explanation.
Purpose: You often have several events that share a common piece of text, but other pieces of the text can change. For example, a group of events may share a common presentation text, but each individual event has a different description. Changing the common text is a lot of work because you have to change it in each event. In this case, you can divide your text into several parts (using horizontal lines). Then you can tell the software that one part will be shared between several events.
Usage: if you are editing /node/1234
Add this in the part of text that will be common:
demosphere_dtoken_copy_part(1234)
Then, if you edit /node/5678, you can add the same token in one of the parts:
demosphere_dtoken_copy_part(1234)
All of the text in the part of /node/5678 cotaining the token will be updated when /node/1234 is changed. Be careful to use full/large horizontal lines (not the small ones).
April 9, 2011
User calendars
Each user can have his own calendar ("user calendar" : displayed on your Demosphere site).
This feature has been around for a long time but had a lot of bugs.
All of the code was cleaned up and merged with the widget configuration.
(the widget allows a user to display a custom calendar on his own web site).
"self-edit" links
Previously, you could edit an event and send an email to the organizer saying "your event has been published". Now, you can also include in that email a special link. This link allows the organizer to directly edit the event by himself. You will receive an email telling you that somebody edited his event.
Just add "%self-edit-link" in the email.
Role for "private" events
A new role called has been created. It is called "private event creator". If you assign this role to a user, he will be able to create his own events. His events will not appear on the frontpage, but they will appear in his "user calendar" and "widget".
Role for "frontpage" publishers
Another new role has been created. It is called "frontpage event creator". If you assign this role to a user, he will be able to create and publish events on the frontpage. But he will not access the whole interface and will not be able to change any other events.
All three previous features (self-edit, private events and frontpage publishers), required a change in the way event text was handled. Previously, we used a format called "Full HTML" for events. This had security implications, and meant that only trusted people could publish or edit events. Now we use "Filtered HTML" so that less trusted people can change events. This implied significant changes in the code.
The backend form also needed to be adapted so that all features (including doc convert) could be used from all major browsers (including MS internet explorer).
an email alias manager;
This only concerns "hosted" sites (sites that are on the Demosphere server).
The manager allows you to create and modify any email aliases you want.
That means you can create any email addresses for your domain.
For example, if your domain is xyz.demosphere.eu, you can create emails addresses like abcd@xyz.demosphere.eu.
a better diff display
The interface that displaying differences between events, emails and feeds (the "similar docs" link), has been improved (but still requires some work).
a better unit testing framework
This has no direct impact for you. Many features in Demosphere are automatically tested every day to make sure no bugs appear. Writing tests and maintaining them is a lot of work. I've switched from selenium 1 to selenium 2 (webdriver). That required writing a new testing interface and re-writing all of the tests.
Other smaller changes:
backend form: no js in validation bug
backend form: events near date fix
backend form: no js in validation bug
created events where not in filtered format
mail import: allow delete / force large emails
map shapes: adding manager
frontpage cities: fixing bug
event public form: adding stricter check for dates
backend form: fixing paste email source
place compare problem
user email: allowing user name change for random user name
March 6, 2011
Event selection forms:
The main changes concern the event selection interfaces:
- front page options
- widget form
- email subscription form
- feed url builder form
- ical url builder form
- json "feed".
I've reorganized the code so that all of these interface share common parts. These changes are mainly internal and should not have much impact for you, but they are an important step for the future of the code.
The only new features are:
- ical url builder (similar to the rss/feed url builder)
- all options are now available to all of these interfaces. (for example the "most-visited" option is now available for all of these interfaces).
Map shapes:
Previously users could select all events that where inside a circle on a map. This is enough for most uses, but sometimes users want more complex regions. I have added preliminary support for polygons. The user can upload a kml file with a polygon.
February 8, 2011
- The options button on the front page.
- Small navigation improvements in feed import (menus, selector...)
- Support for revisions (experimental)
- Several small bug fixes
December 24, 2010
Before we begin the new coding season (jan - sep 2011) here are a few changes that were done since september.
SEO: you can customize the page <title> and the <meta> keywords and description.
This information is normally automatically generated. However, for important events, you can get better results in search engines by writing custom titles, keywords and descriptions.
Extra options in feed import:
- tidyFeedXml: some sites have feeds that are broken (bad xml). Use this option to automatically clean up their xml.
- fixHttpsToHttp: some sites have feeds that point to "https" (secure) domains, but don't have valid certificates. This causses feed import to fail. By choosing this option, "https" is converted to "http".
hidden event links: (disabled by default) if you choose this option, hidden text and links will be added to your events. They will appear if someone copy-pastes your event. This technique is also used by wikipedia.
A few small bug fixes.
All events are now available through a fairly complete JSON interface.
July 28, 2010
Feed import: new GUI for html content selector
I have added a new interface for choosing the html content selector in the feed import component.
This was an important but quite difficult step in creating feeds. I wrote an interface that allows you to simply click on a part of the page that contains the article (like firebug). The system then uses an algorithm to automatically search for a good content selector that works on several articles in the feed.
I think this new system is accessible to non-technical users.
The html content selector now supports both CSS selectors and XPATH selectors.
(for example: "#article" instead of "//div[@id="article"]")
Feeds are now required to have a selector (empty selectors not allowed).
July 22, 2010
I just updated your sites with a new version of the demosphere code.
The main new feature is the "widgets" that allow users to display a customized version of the calendar on their own web-sites.
Other changes include:
- template files for the frontpage, for other pages and for the main calendar. Previously we used theme functions, which require more understanding of PHP. Now it is simpler to change the basic layout of the site.
- the main calendar generating code has been re-written. This should not have any impact on you.
- a lot of smaller changes, mainly code cleanup.
- city domains: You can now use: http://city1.example.org instead of http://example.org/city/city1
You can configure it in the frontpage section of demosphere, and then configure your DNS and your apache server (add a ServerAlias for each city).
Widgets:
The widget code is still beta. I would appreciate your feedback and suggestions.
There is not yet a link to this feature on the frontpage, so you will have to type in a url like this:
http://yoursite.org/widget-config
There are a lot of configuration options for the widget and probably some more will be needed. Please tell me if you need more options.
You will notice that users can individually select and remove events. They can also add events that do not exist on your site (the event is a link to an event on another site).
June 16, 2010
1) Map in backend event form:
You can now choose a position on a map directly in the backend event form. (you don't need to go to google maps any more, and you don't need the firefox extension to enter a map). There is a search box that allows you to enter your address just like the google map interface. A red rectangle shows what will displayed in the map.
2) CCK compatibility.
Drupal can be extended using the CCK module and views modules. CCK form fields were not rendered in the backend-form. Now they are. Form elements can be re-ordered. There is a special form element called "extra-options". All form elements after "extra-options" are hidden inside a fieldset (click on it to open in).
3) Upgrade to drupal 6.17
Drupal 6.17 was not a security update so it was not urgent. Now Demosphere is up to date.
4) user emails and feed builder
Users can select which events they want to receive by mail, or which events they want to have in their RSS feed. Previously, they entered a point on a map and a distance. The distance part wasn't very intuitive. Now a red circle is drawn to explicitly show which area is included.
5) direct (open) publishing.
By choosing an option in the Demosphere configuration you can enable open-publishing. Now topics and cities are correctly supported.
6) small bug fixes.
May 14, 2010
I've implemented a new feature so that users can easily change the colors (or icons) associated to topics (or event types). These are the colors displayed on the frontpage (in the topic selector -top right, and beside each event). These colors are also displayed in the interactive map.
This is a commonly requested feature when new collectives install a site. It will probably not be very useful for existing sites.
Colors are configured through the normal configuration system (section: "frontpage")
The system automatically computes new icons for each color. Images for marker points (interactive map) are also computed.
The code is merged on the trunk, and I will update each one of your sites in the coming days.
