I have changed the javascript compression in easysoical to (uncompressed) it worked now,will kee updates if it failes

Hello aelsharawi,

I'm sorry that missed up of this post thread, okay keep us updated then.

no worried ,I know it is weekend,but looks like it didnt work,can you please ,see if it is reproduced at your end ?

Hello Aelsharawi,

Regardless of what settings I change on the back end, the front end doesn't seem to be modified. Can you please advise if there are any other caching mechanism on the site?

I re-enabled compression,and added a direct cdn inside easysocial "instead of the flare one"

thanks mark for your help,yes there is "cdn" cach of jss and css, I will flush it now (will take few minutes to be effective)
===
or you can directly access the website through the direct ip (attached)

also in this cloud ,there is some compression

the website is slow now,I assume that you are editing something so I will not change anything unless I got your feedback
=======edit===
I created a clone for you with the last version of the main

I noticed that you disabled the system-cach plugin ,can you advise of other modifications that you changed in the main domain.
ps: your changes are still at the clone
=I reinstalled easyscoial in the main domain=

I think it is working now

here is what I did
1-reinstall easyscoial
2-clear chach
3-recomplile themes in easysocial
4-clear the browser cach

it is now working ,I dont know if it is a bug or not,for you MARK u can play with the clone as much as u can ,to identify if it is a bug or not.


thanks

Hello Aelsharawi,

I think there's some intensive caching on the css / js which causes those errors (It was probably fixed in some instances) but because it is heavily cached, it's probably throwing those errors.

thanks MARK ,Can you advise which files do I need to exclude from caching ?

is it com_ajax ?

see here at

http://kbase.jotcomponents.net/jotcache:help:direct40j3x:exclusion

Hello Aelsharawi,

Hm, no it's not really related to ajax calls but the javascript files itself. Whenever you hit any js errors, the best way to troubleshoot it is via,

1. Turn off all cdn / cache

2. Change to development mode

3. See which file is throwing errors and what line, report it to us.

At times, compressing all javascripts into a single file could be problematic because we do not know if the previous javascript from modules / other extensions are throwing errors and breaking the whole js block