Thread Starter
Spencer
(@boostwebsales)
I created a test page to further troubleshoot this.
It is now instead bringing up a window with the same page inside of it.
http://shortsaleexpertsandiego.com/test
Very strange.
Thread Starter
Spencer
(@boostwebsales)
I moved everything to the test page. The original contact button is now just going to a static page so I can proceed in development of the site.
Hi, on your test page I notice two things wrong:
1. Your theme or another plugin that is not respecting WP’s own the wp_enqueue_script() method (that is there to prevent this kind of problem) loads an older version of the jQuery library for a second time in the footer:
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
You need to find out who’s doing that and elimitate that second call.
2. Your test link in the source looks like:
<a href="http://shortsaleexpertsandiego.com/test#InlineDivID3" class="fancybox">Click for FancyBox Test – Not Working! </a>
but you need to make it:
<a href="#InlineDivID3" class="fancybox">Click for FancyBox Test – Not Working! </a>
You need to adapt that URL. If you are sure you used only #InlineDivID3
(without the full domain) than it might be automatically prepended the Google Analytics plugin… In that case, and if you cannot switch that behaviour off in its settings, switch to another analytics plugin.
Thread Starter
Spencer
(@boostwebsales)
Awesome that fixed it thanks!
Any idea what is causing the strange vertical black lines around the fancybox?
I do not see those in Opera 11.5, Chrome 12 or Firefox 5 … Are you using IE?
Thread Starter
Spencer
(@boostwebsales)
I see them in Chrome 12.0.742.122 and Firefox 5.
I will upload a screenshot in a few minutes.
Thread Starter
Spencer
(@boostwebsales)
http://shortsaleexpertsandiego.com/images/1.jpg
http://shortsaleexpertsandiego.com/images/2.jpg
Note the vertical black lines around the edges of the fancybox.
These are screenshots from Chrome 12.0.742.122
The issue is not present in Firefox now that the .js issue is fixed.
I see what you mean on the screenshots but cannot reproduce them on my side. No idea what could be causing it but it looks like a CSS issue…