› Forums › Easy FancyBox Pro › Not working on new install
- This topic has 4 replies, 2 voices, and was last updated 8 years, 8 months ago by Kelly J.
11 October 2014 at 00:53 #3788
When clicking on an image the page seems to grow at the bottom, but no image is displayed.
Running the latest versions of standard and pro. Also running a few other photo related plug-ins, disabled them and activated the default theme and still images are not popping up. Installed at GoDaddy.
While site is under development it can be viewed here… http://dpiperinn.com/dpi/photo-gallery/
11 October 2014 at 03:25 #3789RolfKeymaster
Hi Kelly, it looks like something is blocking or interfering with requests or responses on your site. No idea what it could be but your site loads extremely slow, if at all. The background image for example takes me 50 seconds to load.
And then I get errors like these below in the browser console but each try they seem to be slightly different. One time a file loads, the next time an error occurs… Very strange.
Resource interpreted as Stylesheet but transferred with MIME type text/html: "http://dpiperinn.com/dpi/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox-1.3.6.pack.css?ver=1.5.6". (index):25 Resource interpreted as Script but transferred with MIME type text/html: "http://dpiperinn.com/dpi/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox-1.3.6.pack.js?ver=1.5.6". (index):355 GET http://dpiperinn.com/dpi/wp-includes/js/jquery/jquery.js?ver=1.11.1 net::ERR_CONTENT_LENGTH_MISMATCH (index):26 Uncaught ReferenceError: jQuery is not defined jquery-migrate.min.js?ver=1.2.1:2(anonymous function) jquery-migrate.min.js?ver=1.2.1:2 Uncaught ReferenceError: jQuery is not defined (index):343 Uncaught ReferenceError: jQuery is not defined jquery.cycle.all.min.js?ver=2.9999.5:1 Uncaught ReferenceError: jQuery is not defined jquery.fancybox-1.3.6.pack.js?ver=1.5.6:25 Uncaught ReferenceError: jQuery is not defined jquery.easing.pack.js?ver=1.3:14 Uncaught ReferenceError: jQuery is not defined jquery.mousewheel.pack.js?ver=3.1.3:8 Uncaught ReferenceError: jQuery is not defined (index):360 GET http://dpiperinn.com/dpi/wp-content/themes/kayjayone/images/bg.jpg net::ERR_CONNECTION_RESET (index):106
Now the first two errors are strange (the server does not seem to recognize the correct mime type for these two fancybox files while other script and stylesheet files are recognized just fine) but these are not blocking errors. However, the third one is and it explains all subsequent errors breaking all scripts, among which FancyBox is victim too.
It might have to do with file permissions, or maybe something went wrong during upload via FTP? Do you get any errors in the server log files?
You might be able to learn more from GoDaddy support on how to fix what looks like a server related issue.
11 October 2014 at 23:04 #3791
Thanks for your quick response! The site was going up and down, you might have been accessing the it during that time. The errors I see in the console are a little different…
Resource interpreted as Stylesheet but transferred with MIME type text/html: "http://dpiperinn.com/dpi/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox-1.3.6.pack.css?ver=1.5.6". /dpi/photo-gallery/:25 Resource interpreted as Script but transferred with MIME type text/html: "http://dpiperinn.com/dpi/wp-content/plugins/easy-fancybox/fancybox/jquery.fancybox-1.3.6.pack.js?ver=1.5.6". (index):355 [cycle] terminating; zero elements found by selector jquery.cycle.all.min.js?ver=2.9999.5:1 Uncaught TypeError: undefined is not a function jquery.fancybox-1.3.6.pack.js?ver=1.5.6:25L jquery.fancybox-1.3.6.pack.js?ver=1.5.6:25K jquery.fancybox-1.3.6.pack.js?ver=1.5.6:25s.onload jquery.fancybox-1.3.6.pack.js?ver=1.5.6:25
The final error, Uncaught TypeError is received once clicking an image. Contacted GoDaddy, they suggested changing file permissions, which I did. Still stuck.
Thanks for your help!
11 October 2014 at 23:59 #3792RolfKeymaster
OK, yes all other errors are gone. I still get amazingly slow load times. The background image took over 1 minute this time even though it’s ‘just’ 600Kb. If I browse through the galleries on the original html site (in the root) then these images load much faster. About 10-13 seconds for 300Kb. This difference seems odd to me and it might be related to this mime-type thing…
Is there a .htaccess in the root? Does it have a rules that might be interfering with normal WordPress operations in the /dpi/ subdir?
12 October 2014 at 01:17 #3793
There was something weird in the root .htaccess file. Removed it and things are working as expected. Great plugin and great support! Thanks for your help!
- You must be logged in to reply to this topic.