Help & tutorials

ubie_data is a main table - each row is an "item" the subdata is related to

Main table, each row is an

ubie_data_facts is for just facts or ideas, but also for texts describing a person or organisation. The field ubie_data_id is a foreign key that points to the table above. full_desc is only a "placeholder" behind a display element displaying data from many fields. Some fields may be unnecessary and will be probably deleted (storage_id etc)

Important -

1) this table has a one to many relationship with the main data. One entry in ubie_data could have many subentries in ubie_data_fact. This is necessary as the site is actually multilingual. So each fact under one single item could have own language but only one of them is displayed in list depending on the currently active content language.

2) as there is also need to separate personal and organisation data and simple fact/idea data during form submission, two MySQL views are created on this table - ubie_data_facts_poview (for persons and orgs) and ubie_data_facts_fiview (facts & ideas)


This table is for personal or organisation data. It has one to one relationship with the main table - that means there could be only one person or organisation per main item. 

Like in above example also two updateable views are created - ubie_data_who and ubie_data_what, one for personal and another for organisation data.

  • Struktuurubie_data
  • Struktuurubie_data_facts
  • Struktuurubie_data_facts_fiview
  • Struktuurubie_data_facts_poview
  • Struktuurubie_data_pr_comp
  • Struktuurubie_data_pr_comp_12_repeat
  • Struktuurubie_data_pr_wf
  • Struktuurubie_data_what
  • Struktuurubie_data_who
  • Struktuurubie_data_who_what

Component - Fabrik

Data - Wordpress + current site

This is aimed to be a workflow for collaboration in creating new common press releases. 

The drafts of press releases are displayed by the same way like news (Fabrik list reads posts from the wp_posts table) except here are shown only drafts that are not published in main blog site. In both cases the Fabrik lists prefilter feature is used. And in this case the Fabrik details view is used - here the beauty is not so important.

Inside this details view we see a Fabrik list. This is displayed with a Fabrik content plugin feature that allows to display Fabrik data embedded in articles or inside Fabrik views themselves. So here in this details view is a list view with data related to this record (blog post). 

Using this workflow

  1. The author posts the initiial text of the press release as a draft. No matter directly in the blog site or via Windows Live Writer (the most convenient way!)
  2. Other collaborators are seeing this draft and when they are something to say about (to propose changes, additions etc) then they post i.e. excerpt of initial text, replacing text that they propose instead and if needed their comment. The appropriate guides are displayed in this form
  3. The author reads the suggestions and makes corrections if needed. The best way of course again via W Live Writer. 
  4. Once the corrections are done, the author marks the appropriate suggestions as considered. 


Component - Fabrik

Data - Wordpress blog

Fabrik list reads data from a database table that contains the blog posts of Wordpress blog. In this case, the blog's database is residing in the same server under the same account. If it would be in different server then the other one had to be set to allow access from this host. 

In many technical reasons, however would be better if this current Joomla site tables and Wordpress tables would be in the same database. 

The list is set to show post titles, authors and dates. The links are targeted to the original blog site - otherwise the Fabrik details view would need some design work. 

The Latest news module shows the post from the same blog but by reading data from its rss (not from db table). 

Component - Fabrik

Created a list, form and appropriate elements, new database tables and viewsbehind it were created as well (and db table fields behind each element). In each addition user can determine whether to submit a person or an organisation, having or not a contact data, if person then whether he/she is alive or not etc - depending on choices the form fields are displayed or hidden. 

Althought there are used different fields for person and organisation names, both the full names and "sort names" are autocreated and submitted into one field. 


Introduction - module type "custom html", position 3. This is a module that allows user to create a custom html content and display it where needed. 

About UBI - this is a "module containing modules" - module type SP tabs and all modules that it contains are of type "News flash" showing articles titles and introduction parts. Each module displays articles from different categories.

To create a new tab -

  1. create an appropriate category for articles
  2. create needed articles under this category
  3. create a new module of type News flash, order it so that it would be displayed in needed position
  4. edit the module titled About UBI and add the new module

Next milestone - this comes from Calendar (component GCalendar) that shows events from Google Calendar. Module type - GCalendar next event. 

Latest news - module that shows news from newsfeed. In this case the blog's feed.