Google Analytics script not 'closed' in 3.0.7
-
-
- Brian Shea
- Sr. Rocketeer
- Posts: 176
- Thanks: 18
- Web Management, Server Admin, Google Apps Service Provider
-
Andy, about the PM feature.
I found it searching for Private Messages, but I also just checked the FAQ to see if it was there. It is not.
www.rockettheme.com/forum/index.php?f=15..._v=viewtopic#p427446
Not a big deal, as my first place to look is to search, but maybe it can be added to the FAQ? -
Website Hosting and Management
for the non-technical, non-geeks
G+ Page for Seven Sages , a Google Apps Authorized Reseller
-
-
-
- Brian Shea
- Sr. Rocketeer
- Posts: 176
- Thanks: 18
- Web Management, Server Admin, Google Apps Service Provider
-
Sean,
I sent a little more info in a PM. -
Website Hosting and Management
for the non-technical, non-geeks
G+ Page for Seven Sages , a Google Apps Authorized Reseller
-
-
-
- Sean Habing
- Elite Rocketeer
- Posts: 1028
- Thanks: 1
-
Thanks Brian,
just checking that out. Seems identical to my local testing environment i am not seeing a javascript error or anything on your site which is a good sign so i think its closing properly as well. I can recreate the layout as well on mine.
Are you getting a javascript error? if so what browser?
Sorry just trying to narrow it down
Cheers
-
-
-
- Brian Shea
- Sr. Rocketeer
- Posts: 176
- Thanks: 18
- Web Management, Server Admin, Google Apps Service Provider
-
I hadn't noticed an error using Firefox, and I just checked with IE8.
I only noticed an issue when I was trying to setup Analytics, and Google kept telling me it couldn't find the code.
That's when I checked the source code and I see GA there, but I noticed there was no closing </script> after it.
It just seems to flow into the next script. -
Website Hosting and Management
for the non-technical, non-geeks
G+ Page for Seven Sages , a Google Apps Authorized Reseller
-
-
-
- prim
- Preeminent Rocketeer
- Posts: 17290
- Thanks: 217
-
"I hadn't noticed an error using Firefox"
Did you check the Error Console in Firefox? - Please reply with a direct link to the issue & create a new thread for each new issue.
A template is only as good as the content that goes into it
- DanG
-
-
-
- Brian Shea
- Sr. Rocketeer
- Posts: 176
- Thanks: 18
- Web Management, Server Admin, Google Apps Service Provider
-
prim wrote:
"I hadn't noticed an error using Firefox"
Did you check the Error Console in Firefox?
No Javascript error.
I never used the Error Console before. Thanks.
The only error I pickup on the site is:Warning: Unknown property 'border-radius'. Declaration dropped. Source File: http://marineac.com/templates/rt_panacea_j15/css/template.css Line: 100
But these forums fill up my console.
-
Website Hosting and Management
for the non-technical, non-geeks
G+ Page for Seven Sages , a Google Apps Authorized Reseller
-
-
-
- Sean Habing
- Elite Rocketeer
- Posts: 1028
- Thanks: 1
-
Hello,
Just viewing the source on your site and i can see that the </script> tag is indeed closed. What gantry does is collect all the JS into one block as you are seeing there.
Cheers
-
-
-
- Brian Shea
- Sr. Rocketeer
- Posts: 176
- Thanks: 18
- Web Management, Server Admin, Google Apps Service Provider
-
thank you. I'm getting stats now.
What is odd is that I never had a problem with Google finding it's code before. And when I used an external plug-in, Google found it right away.
Perhaps because the GA code is part of the Gantry script, Google takes longer to recognize it? Or, maybe Google still doesn't 'see' it, but it still tracks stats because of the script?
I'll check it on the next site I setup to see if I run into Google not 'verifying' the tracking ID is installed. This becomes a Google issue, but if it doesn't verify we might want to add a little comment in Gantry stating that google doesn't verify, but the stats work. -
Website Hosting and Management
for the non-technical, non-geeks
G+ Page for Seven Sages , a Google Apps Authorized Reseller
-
-
-
- Sean Habing
- Elite Rocketeer
- Posts: 1028
- Thanks: 1
-
Hi Brian,
I am not 100% sure what the root cause of that was. It might be that google is looking for a definition that is slightly different thus causing the error but i dont think the script tags should effect that.
Please let me know what happens on the next site as if it occurs again then we might have some formatting issue
Cheers
-
Time to create page: 0.037 seconds