I can’t figure it out either. It looks to be something from the map’s many and various JavaScript callback functions. Maybe try putting that map in an iframe, and see if that insulates the problem. Make a new page, with nothing on it except the map. Put the map in the top-left corner. Then draw an iframe on the contact page where you want the map to appear, and target that map page into it.
Walter
On Jan 12, 2014, at 3:31 PM, Todd wrote:
Yes, I did. Very strange. I’ve been looking at it but so far I can’t suss out what the specific problem is.
Wow! No wonder I was struggling if Walter can’t spot the problem.
The same page using Perch Maps with Perch 2.3.4 works fine, in 2.4.2 it breaks. That’s the only common thing I can find so far. Or course Perch support appear to draw a line if their maps work on a blank page by itself.
Isolation using an iframe won’t work as the page is referenced in Perch. I’ll just put a Google map in direct through Freeway instead if I can’t find a solution soon.
David
On 12 Jan 2014, at 20:37, Walter Lee Davis email@hidden wrote:
I can’t figure it out either. It looks to be something from the map’s many and various JavaScript callback functions. Maybe try putting that map in an iframe, and see if that insulates the problem. Make a new page, with nothing on it except the map. Put the map in the top-left corner. Then draw an iframe on the contact page where you want the map to appear, and target that map page into it.
Walter
On Jan 12, 2014, at 3:31 PM, Todd wrote:
Yes, I did. Very strange. I’ve been looking at it but so far I can’t suss out what the specific problem is.
Which led me to believe I’d missed it out on the Perch content template but no so. Could there be a missing
in the Google Code? Surely not.
Although that seemed too much of a hack to proceed with it. I’ve checked and I can’t spot the closing div unless the browser is covering it by completing the mistake?
David
On 12 Jan 2014, at 20:31, Todd email@hidden wrote:
Yes, I did. Very strange. I’ve been looking at it but so far I can’t suss out what the specific problem is.
Use a proper editor (TextMate etc.) to find the missing closing tag or use a dedicated comparison app to see the differences between the original file and the one you modified. Should be easy to spot.
Todd
I’ve checked and I can’t spot the closing div unless the browser is covering it by completing the mistake?
On 12 Jan 2014, at 23:19, Todd email@hidden wrote:
I would be inclined to try one of these:
Use a proper editor (TextMate etc.) to find the missing closing tag or use a dedicated comparison app to see the differences between the original file and the one you modified. Should be easy to spot.
Right found the solution, so easy when you know how.
The gotcha with the Perch Maps element is that if you’re working with inline content you need a html wrapper around the inline map content and within that wrapper but outside the content map content div like so…
<----- wrapper -------->
<----- content div------->
<--------- Perch Map -------->
<----- content div------->
<------------- Extra div to stop Perch Map from obliterating “content” but not the map itself ------------->
<----- wrapper -------->
You don’t need that extra div if content div is position absolutely.
Who would have thought! Anyone like to offer an explanation?
–
David
On 12 Jan 2014, at 23:19, Todd email@hidden wrote:
I would be inclined to try one of these:
Use a proper editor (TextMate etc.) to find the missing closing tag or use a dedicated comparison app to see the differences between the original file and the one you modified. Should be easy to spot.