Bug reports Found a bug? Post it here please.
Version 7.x > Bug reports > Google Maps: API Reference View modes: 
User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 1/7/2013 12:31:43 PM
   
Google Maps: API Reference
It appears when I use the Basic Google Maps webpart, it links to the Google API javascript library twice when the webpart is placed on a page: once in the <head> tag and once in-line right before the MainScriptPath script is loaded. When I debug my javascript I get errors stating having two references of the same library can cause problems. Can you verify this is the case?

User avatar
Kentico Consulting
Kentico Consulting
richards@kentico.com - 1/8/2013 8:45:50 AM
   
RE:Google Maps: API Reference
Hey FroggEye,

we've consulted this issue with our developers and what we got is this: The only location where the google maps API is registered is in "BasicGoogleMaps" class in "RegisterMapScripts" method which is also called only from "OnPreRender" event in "BasicGoogleMaps" control and by "StaticGoogleMaps" web part in its "OnPreRender" method.

The result is that only single google maps API script is called and it's not even referenced from the HEAD section of the page. This has been tested on Kentio CMS 7.0.9.

May I ask you what exact version of Kentico are you using for this?

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 1/8/2013 12:49:04 PM
   
RE:Google Maps: API Reference
Using 7.0.7. If I remember right I put the <script> reference in the page template HEAD section but I did remove it because when I look back at the page template I don't see any values in there. I do have versioning running as well, could it be saving or displaying a previous version of the page template or even a webpart (I've seen that before where an editable text webpart will be deleted and if it is added back to a template with the same ID, it inheirits the text that was previously entered).

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 1/14/2013 3:37:05 AM
   
RE:Google Maps: API Reference
Hi,

If I am getting this correct, you added something to the head section of the page template and you do not see it on the live site (or in the live site rendered HTML)? If so, the only thing I can think of is full page caching. Have you tried clearing the cache?

Or, correct me if I misunderstood you. Thank you.

Best regards,
Juraj Ondrus

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 1/14/2013 4:02:27 PM
   
RE:Google Maps: API Reference
Yes, I did add the <script> reference to the HEAD of the template. Then shortly after, I removed it from that template as I found the BasicGoogleMaps webpart added it where needed. Now when I look at my source code after the live page renders, I find it is still in the HEAD section as well as in the body. Could this have to do with our team accessing a single database with 2 different URLs?

For instance, we develop locally with localhost. Then deploy the code to our test server which is test.domain.com. 2 different instances of code but 1 database. I notice when I check out an object on localhost and someone goes to test.domain.com the document isn't checked out. Same goes for if I check something in.

For this particular instance, I've checked both urls and neither are checked out or have anything in the head section.

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 1/29/2013 12:56:57 AM
   
RE:Google Maps: API Reference
Hi,

Are these instances configured into the web farm synchronization which ensures these things?

Best regards,
Juraj Ondrus

User avatar
Kentico Legend
Kentico Legend
Brenden Kehren - 1/29/2013 3:44:40 AM
   
RE:Google Maps: API Reference
They are not, yet. And would my local machine and a server be considered a web farm?

User avatar
Kentico Support
Kentico Support
kentico_jurajo - 1/29/2013 4:25:26 AM
   
RE:Google Maps: API Reference
You are connecting to one DB, the applications do not know about each other - this can cause issues and the cache and so on are not synchronized. So basically yes, you should use web farms synchronization.

Best regards,
Juraj Ondrus