UPDATES EasyBlog 6.0.11 Released! Update to the latest version now!

Helpdesk

Your Time
Our Time
Response Time
24 — 48 hours
We strive to provide the fastest ever response possible. However, we are not super beings.

Allow at least 24 — 48 hours
  Support is offline
It is currently off working hours and most of us aren't around

Rest assured that we will get back to you as soon as the day starts tomorrow!
  Support is offline

EasyBlog - FaLang Translation Compatibility

Gary Miller · ·
1:39 AM Thursday, 07 January 2016
High
Hello, I am working with the developer of the popular FaLang extension to add translated content to EasyBlog 5 in Joomla 3. I have been able to configure the FaLang extension so that it sees the EasyBlog content via a few XML documents (available through other posts on your forum). The issue I ran into is that the translated content was not appearing through the front-end of my website. Stéphane, the FaLang developer, was great in that he went in and looked into the issue. From what he tells me the issue is that the EasyBlog content revision system is over-writing the translated content. This takes place is:
administrator/components/com_easyblog/includes/post/post.php around line 560:


public function checkoutFromRevision()
{
$workbench = $this->revision->getContent();

if (! $workbench) {

// somehow the revision id is exists but the revisions.content is empty.
// we need to regenerate the revisions.content.
$this->checkoutFromPost();

} else {
$this->setWorkbench($workbench);
}

$this->revision_id = $this->revision->id;
}


Stéphane's solution was to set the Workbench to Null so that the EasyBlog software would not overwrite the translated content.


public function checkoutFromRevision()
{
$workbench = $this->revision->getContent();

$workbench=null;
if (! $workbench) {

// somehow the revision id is exists but the revisions.content is empty.
// we need to regenerate the revisions.content.
$this->checkoutFromPost();

} else {
$this->setWorkbench($workbench);
}

$this->revision_id = $this->revision->id;
}

We are both wondering if there is a better way to get the same results or if this solution looks acceptable? If you have any suggestions or recommendations they would be greatly appreciated.

Thanks!
--Gary
The replies under this section are restricted to logged in users or users with an active subscription with us