Hi Eric,
I’m using Total Cache and Cloudflare in my site but has no conflict at all.
I have several users that have similar situation like yours and most of them has jquery conflict with another plugin. But in some other case, they are forcing the async attributes to script tags which links jquery and prettyphoto.
I can’t look at your site though because it display an info that still under construction. You check where the javascript fails in Google Chrome:
1.) Open new tab.
2.) Press f12.
3.) Open your site( with Simply Instagram running ).
4.) The developer tool will log the error in console tab.
Please let me know if somehow, the error points to Simply Instagram.
I’m using PrettyPhoto plugin for the popup.
Hope this helps.
Thanks
I’m having a similar problem. Errors show that the files for prettyPhoto css and js simply are being referred to wrong — it’s trying to load like this:
http://myurl.com/wp-content/plugins/nfs/c88fake88/h8fake8/mnt/128822/domains/myurl.com/html/wp-content/plugins/simply-instagram/css/simply-instagram-prettyPhoto.css?ver=3.8.1
Looks like it’s putting the root path to my plugin directory in there with the url. I’m using MediaTemple, btw.
Ok, I found the problem. If you use WP Better Security, like I did, to change the directory of your content folder, it puts a line in your wp-config file that sets the relative path to your content folder … like this
define( ‘WP_CONTENT_DIR’, ‘/nfs/444fake//mnt/555555/domains/yourdomain.com/html/wp-content’ );
and that gets used by the Simple Instagram plugin (and possibly other plugins) when spitting out the paths to the prettyPhoto js and css.
