This week we have proceeded to simplify the management of the register forms for the events. From now on, the forms used by users to register in an event organized by our organization, will be the same ones as those from the forms service.

1.- With this aim, we have improved the forms service by adding the possibility of linking a form to a service and the possibility of defining the different states of a register.
2.- In the same way, we have created an option that allows to import or "copy" other forms fields, which is very useful in case we are creating two similar forms; it permits to design the first one and, then, we just have to copy it and modify what we need; that way, it is not necessary to create every single field again.
3.- Existing events forms and registers have been migrated with the purpose of avoiding losing any data; fortunately, the new system is quite similar to the previous one.
4.- One of the advantages of using the forms service instead of using the events forms is that the latter let us reorganize the fields, add or delete fields established by default, fix compulsory fields...

To show you this new service we put the following screencast at your disposal:


*The first thing we’ll do is to create a form and we’ll call it “Design Workshops”, for instance.
*This form will be linked to the events service.
*We’ll define the fields, their order and which ones are compulsory.
*We’ll now go to “Events” and create a new event with its data.
*In “Use the form” we’ll select the form “Design Workshops”.

Now we have the event, so we check it and publish it. If we want to sign somebody up for the event, we can do so from the “Events Management”, by clicking on Register.
If we want the list of people who are registered for the event, we’ll just click on the person's register number, which appears next to the event title, and we'll have the list in an excell or CSV file.

• Another service in which we have made an improvement is “News”: now, we can define if we want the subsections' news to be shown or not in a section’s view in the Blog & RSS preferences or in the snippets. That is to say, for example, that from a section, we can see the news divided in sections in snippets.

This doesn’t happen by default in order to remain compatible with the platform’s system we have been using up to now. This is useful when there is a section which has several contents we want to subclassify and we'd like to see all of them at the same time.

• Some presentation and functional faults related to news sections have been solved as well.