This is sample code to generate article link:
<a class="blg-title" href="<?php echo osc_route_url('blg-post', array('blogSlug' => osc_sanitizeString(blg_get_slug($b, 'article')), 'blogId' => $b['pk_i_id'])); ?>">
So ID does not matter (basically text is also irrelevant to have link functional).
Plugin will use this to get slug into url:
blg_get_slug($b, 'article')
This is piece of slug function:
if(isset($blog['s_slug']) && trim($blog['s_slug']) <> '') {
$text = $blog['s_slug'];
} else if (blg_get_title($blog) <> '') {
$text = blg_get_title($blog);
} else {
$text = __('post', 'blog');
}
Means if you've defined slug in article, this one is alway used, otherwise is generated from title.
This is piece of title function:
if(isset($blog['locales'])) {
if(blg_field('title', $blog['locales']) <> '') {
return blg_field('title', $blog['locales']);
}
}
if(isset($blog['s_title']) && $blog['s_title'] <> '') {
return $blog['s_title'];
}
It's checking in locales.
It use getBlogLocales from model to get locales.
So, locales are added in form ['locales']['en_US'], ['locales']['de_DE'], ... etc.
blg_field function is build to find most suitable locale.
If exists, it returns locale of osc_current_user_locale(), otherwise site default locale, otherwise search for first non-empty.
So basically do not see any problem here.