[lucrando]

I’m using a WP Multisite and deactivated all plugins for this test.

I created a gallery as a portfolio item but it doesn’t work and doesn’t show any message error.

http://www.lucrandonaweb.com.br/novo/portfolio/campanha-compasso-moveis/

What could be happening?

[Mehmet S.]

It has worked on my pc.

[lucrando]

On my mac with Lion 10.7.5 it doesn’t work :(

I tried to test it on Safari Version 6.0.2 (7536.26.17) and Google Chrome Version 23.0.1271.64

:( What a should to do?

BTW, in this page it works like a charm on Safari and Chrome:

http://themes.pixelwars.org/responsy-wp/portfolio/some-project-6/

[lucrando]

I already cleaned my mac and cache browser with ccleaner.

Are there some file permission needed for it works?

[Mehmet S.]

See:

[lucrando]

Ok Sali. Thanks for your help and I already understood it.

But, what I should have to do to fix it and get it work for Safari and Google Chrome for mac?

[lucrando]

why the Responsy version 3.1 running here works in all browsers for me:

http://themes.pixelwars.org/responsy-wp/portfolio/some-project-6/

but Responsy 3.4 in my site doesn’t works

Is possible to get the Responsy 3.1?

[lucrando]

ah! On Firefox 16.0.2 for Mac OS it works.

[mnib]

I am having the same problem with Firefox 17.0.1 on OSX and Safari 6.0.2.

In addition to not having any of the sliders loading (only getting the loading circle) on the homepage and my subpages (e.g. portfolio), I also am not getting a mouseover effect on any of the post images, and they are also not linked. This means, for example, that any portfolio links from thumbnails, be they in the portfolio gallery or in the homepage “latest projects” block do not exist. The image is there, but no link and no mouseover.

Firebug does not catch any errors.

I can replicate the error on:

http://mynameisbreanne.com (does not work on Firefox or Safari)
http://www.lucrandonaweb.com.br (does not work on Firefox or Safari)
http://themes.pixelwars.org/responsy-wp/ (Firefox only; Safari is fine)

[mnib]

Okay, working now, though I didn’t change anything.

For anyone who may encounter this in the future, the problem I was facing was actually a problem with the fonts loading; the resources requested from themes.googleusercontent.com/static/fonts/* were not loading, which I assume is why all of the overlays (which use those fonts) were not behaving properly. Just a guess, anyway.