Both remain highly popular among customers, website admins, developers, content editors - here is why: Now that many websites have upgraded to Drupal 9, the Views and multilingual functionalities in Drupal have not changed much. Among lots of other things on the list, there were multilingual capabilities and the Views built into the Drupal core. Navigation from one language to other will therefore only be possible through the language switcher block.When Drupal 8 was released in November 2015, its list of new features was really impressive. Since the English and Swahili version of the site are only supposed to show content in the specific language, the language should be set to "Only current language" with a language switcher, and with links to the translations hidden (admin/settings/language/i18n). For now I leave that one out while I configure all other content types, dis-allowing "language neutral" to enforce the appropriate display of future content. I'll configure Localisation Client instead. Instead I've added another role "translator" with the appropriate rights. Two roles have been set up for ICanLocalize translators or managers, which are redundant now. However, according to their website, ICanLocalize does not offer Swahili translations (. Īmong the modules installed is are also modules for the 'ICanLocalize' service. If any translations done for this site would be submitted there, then that would be an added bonus. On there is a group for Swahili (which according to Wikipedia is the same as Kiswahili.) but no contributions have been made at all there. But all the interface and text like the footer do need to be bi-lingual. There are polls on the site which don't need to be aggregated. The site is bi-lingual (English and Kiswahili), and content that is not translated is not supposed to be shown on the other language version. Since I was asked to explain afterwards what I've done, I'll just blog here while I go along. I'm working on the configuration of a bi-lingual site so that the partners in Tanzania can add Kiswahili translations. What needs checking now in which format the dates should be displayed, and whether it needs a timezone conversion. I've enabled "date" to get a CCK date field and added it to the content type event. I've changed that to filter on node type so that it only shows events but then I noticed that the node type "event" didn't have a date field. Ĭalendar: A calendar block was set up, but showed also pages that were published. I had to log in as the specific user to add it correctly. The second problem seems to be a bug: as site admin I was trying to add twitter accounts to other users, but while I was adding them from the specific users page ( > edit > twitter accounts), the account got added to my own account. Admittedly, it says in the description, but since I don't have access to the modules directory, it requires somebody else to do the changes. I encountered two problems: First, quite counter-intuatively, the twitter module version 6.x-3 requires the 6.x-2 version of the oath module. The latest tweets will be displayed in a block in the left sidebar, so I'm making a block and page for all tweets in views. So all it needs is adding a the existing twitter account to a user, or better just making a new user 'twitter'. Twitter: The site uses the twitter module to import tweets. In addition to localisation, I'm also adding some last bits to the site - "de puntjes op het i"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |