jDiction Forum

English => Install & Configure jDiction => Topic started by: dmbn on March 15, 2016, 05:00:36 pm

Title: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: dmbn on March 15, 2016, 05:00:36 pm
Hi!

After updating my joomla to 3.4.8 there is a problem with jdiction. I have 2 languages: german (main language) and english. After editing articles, saving and closing, there are no article changes to see in the frontend. After ca. 10 minutes the changes are shown up. This problem appears only on german site. If i click on the english flag, the changes are there immediately after editing the article. what could it be? Thanks in advance!
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: Harald Leithner on March 15, 2016, 05:22:18 pm
joomla cache?
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: dmbn on March 15, 2016, 05:36:46 pm
I have emptied the cache, but no change.
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: Harald Leithner on March 15, 2016, 05:46:32 pm
if german is the native language jdiction doesn't anything.
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: dmbn on March 15, 2016, 05:51:29 pm
but if I switch to english, the changes are there. so I thought, jdiction should be involved in the problem
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: Harald Leithner on March 15, 2016, 05:53:16 pm
the translation from jdiction is for the english version, so there it works ;-)

are you sure there is no caching anywhere?
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: dmbn on March 15, 2016, 06:24:29 pm
after disabling caching the same problem occurs with english.
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: Harald Leithner on March 15, 2016, 06:28:40 pm
please give me a link and a superuser account.
Title: Re: problem with joomla 3.4.8 and jdiction 1.4.2
Post by: dmbn on March 17, 2016, 01:31:22 am
[SOLVED]: Indeed, there was a problem with cache, not with jdiction. plus, very kinky. disabling cache in System - Configuration - System - Cache - Off didn't solve the problem. only deactivating cache plugin did it. But obviously, this bug came indeed with the the update to 3.4.8. Thanks, Harald!