You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the Generico dataset for reusing content in moodle. It's a step forward! In fact I'm using a master course with building blocks which are distributed to slave course. Works nicely>
But there is one need: automatic linking (soft linking) of multilingual strings:
When showing a dataset, there is automatic linking of activity names. As long as it is not multilingual: {mlang EN}Activity Name{mlang}{mlang NL}Activiteitsnaam{mlang}
In case the activity name is multilingual string for an activity name, the name is correctly shown in the language of choice, but is isn't automatic soft linked.
Automatic linking (soft linking) of multilingual strings would be a step forward.
Best regards,
Bert
The text was updated successfully, but these errors were encountered:
Is this a Moodle limitation that you are describing? Or a Generico one? ie Does it work when Generico is not involved?
I wonder did you consider moving the order of the filters so that Generico is above multilang and autolink_activity_names filters? Do this in: site admin -> plugins -> filters -> manage filters
Also note that if you use Dataset in the "custom script" area of the template, that it will be inserted into the page from the front end. So well after filter parsing is complete. If you do so in the "body" of the template then it will be parsed on the back end and the content passed on to subsequent filters. Working the dataset without javascript is a bit hard, unless the data you pull is quite simple. Fingers crossed you can do it in the template body area.
Justin,
I'm using the Generico dataset for reusing content in moodle. It's a step forward! In fact I'm using a master course with building blocks which are distributed to slave course. Works nicely>
But there is one need: automatic linking (soft linking) of multilingual strings:
When showing a dataset, there is automatic linking of activity names. As long as it is not multilingual: {mlang EN}Activity Name{mlang}{mlang NL}Activiteitsnaam{mlang}
In case the activity name is multilingual string for an activity name, the name is correctly shown in the language of choice, but is isn't automatic soft linked.
Automatic linking (soft linking) of multilingual strings would be a step forward.
Best regards,
Bert
The text was updated successfully, but these errors were encountered: