jDiction Forum

Please login or register.

Login with username, password and session length
Advanced search  


jDiction 2.2.0 released. http://jdiction.org/downloads

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Hjelptilhjelp

Pages: [1]
Hi again!

I see from this post (http://forum.jdiction.org/index.php/topic,838.msg3307.html#msg3307) that there are some problems with JDiction and Joomla 3.4.1.

This might explain also my problems, so this post can be put on a hold until the JDiction is made compatible with Joomla 3.4.1.

Good luck with the work!


It might be that there is a general configuration error in my JDiction installation.

I have a general problem with the extension: On my computer it is translating the pages correctly (see screenshot below):

However, when I test how the site is displayed from e.g. tools.pingdom.com, the pages are not translated, therefore wrongly displaying the original non-translated version of the page (see screenshot below):

I have no idea why the translation process seems to work only on my computer.

Could you check if this page is translated to English: http://www.hjelptilhjelp.no/en/Grief-trauma-and-PTSD/how-childhood-trauma-shapes-the-children-s-brain

If it is not, this confirms that there must be some kind of error in how the Jdiction extension is working on my site.
If it actually is translated to English, how can it be that the Pingdom-screenshot is showing a non-translated page?

Thank you very much for your response in advance!

Hi again!

I found a solution for this issue. Using the sh404sef extension there is a possibility to edit Title and Meta data for each URL on the site. This means that there is easy to ensure that also the translated pages get the correct Title/Meta data to be fetched to Facebook.

In other words: this issue is SOLVED.  ;D

Extensions and jDiction / Re: Compatibility with OBRSS?
« on: April 05, 2015, 09:20:11 pm »
Thank you again!

The OBRSS team managed to make a custom add-on to make JDiction compatible with the OBRSS-component. I have tested it and it works great.

In other words: This issue is now SOLVED :D


I am using the JDiction extension to translate my content on a web site with a Joomla 3.x installation. My original language is Norwegian, and I use JDiction for translation to English.

I have a problem when I want to share content on Facebook.
When I am sharing a translated page (English) on Facebook, the title (og:title) on the shared content is Norwegian - but it should be on English.
In other words: The open graph information is fetched from the original/Norwegian page (e.g. "mywebsite.no/original-title"), although I am trying to share the translated/English version of the page (e.g. "mywebsite.no/en/translated-title").
The problem is only related to the "og:title" as far as I can see.

- The original/Norwegian title might be: Hvordan traumer former barnehjernen
- The corresponding translated/English title is: How childhood trauma shapes the children's brain

However: When sharing on the Facebook the result is:
- For the original/Norwegian article: The fetched og:title is: Hvordan traumer former barnehjernen (in other words correct)
- For the translated/English article: The fetched og:title is: Hvordan traumer former barnehjernen (in other words wrong)

Is there any chance that I could get a unique "og:title" for the translated URLs for the articles translated with JDiction, so that when I am a sharing a translate page the translated title is fetched be Facebook?

Any information on this issue is appreciated. Thank you for your response in advance!

Extensions and jDiction / Re: Compatibility with OBRSS?
« on: April 01, 2015, 08:44:43 pm »

Thank you for your reply. I am discussing the issue with the OBRSS team, and they are checking up the possibility to create a custom add-on for OBRSS to work with JDiction. Hope for a good solution in this way, as it would be great to be able to have a translated feed.  :)

Extensions and jDiction / Compatibility with OBRSS?
« on: March 29, 2015, 11:41:17 pm »

I am using the JDiction component to translate my site. In addition I use OBRSS extension to burn my RSS feeds to Feedburner.
I have a problem with the compatibility between these two components. The OBRSS doesn't connect to the sites that I have translated through JDiction. 

For example if I configure an OBRSS feed to include only articles containing a specific keyword / phrase, it doesn't connect to the translated article, only the original article (from Article Manager in Joomla).

My question is if there are any way to get the JDiction translated content to be "read" by third party components as if they were com_content articles?

Is there any code I can put into either the JDiction files, or into the third party extensions (like OBRSS)?

Thank you very much for your support in advance!

General Questions / Re: Site crash after uninstalling jDiction
« on: October 10, 2014, 11:20:15 pm »
Ok! I solved it, thanks to this post: http://forum.jdiction.org/index.php/topic,630.msg2532.html#msg2532

In short: had to change the "configuration.php" file from mysqli_jdiction to mysqli.
To be able to do this it I had to change permission on the configuration.php file to 777, and back again after it was uploaded to the server.

In other words: the problem is solved  :D

General Questions / SOLVED: Site crash after uninstalling jDiction
« on: October 10, 2014, 10:55:47 pm »

I uninstalled the jDiction extension, and have a big problem on my site: www.hjelptilhjelp.no. The error message is shown both frontend and backend:
JError: Unable to load Database Driver: jdiction_mysqli

I need to know if there is any way to recover the site from this? I understand that this must be due to the database settings that was done in Admin Site when using the extension.

Please give me a quick response on what I can do to recover the site. You can get access to cpanel / databases, or to FTP if any of this is needed. I also need to know if the only thing that will solve the problem is to recover the site from backup.

Thank you for your support in advance!

Pages: [1]