Zh GoogleMap Troubleshooting - Revision history

Admin: /* Error: Oops! Something went wrong */

2020-05-12T12:04:39Z

Error: Oops! Something went wrong

← Older revision		Revision as of 12:04, 12 May 2020
Line 13:		Line 13:
	It caused by: Google started require Google Maps JS API Key for new sites (after June 22, 2016)		It caused by: Google started require Google Maps JS API Key for new sites (after June 22, 2016)

	[https://~~developers~~.google.com/maps/pricing~~-and-plans/standard-plan-2016-update~~ Read more]		[https://cloud.google.com/maps-platform/pricing Read more]

	You have to get API key and enter it into component [[Zh_GoogleMap_Description#OptionsAnchor\|options]].		You have to get API key and enter it into component [[Zh_GoogleMap_Description#OptionsAnchor\|options]].

2019-10-09T14:21:11Z

← Older revision		Revision as of 14:21, 9 October 2019
Line 157:		Line 157:


	{{Languages}}		{{Languages\|Zh_GoogleMap_Troubleshooting}}

	[[Category:Zh GoogleMap\|Troubleshooting]]		[[Category:Zh GoogleMap\|Troubleshooting]]

2018-11-08T08:46:57Z

Placemark Title is too big

@@ Line 34: / Line 34: @@
 Problem of big title caused by template styles.
-My template is working well, therefore I correct it to show this situation :)
+Open your template CSS file and add into the end style overriding.
+Define for both tags, for example, change styles like
 <pre>
@@ Line 96: / Line 45: @@
 </pre>
 Or you can define different size for h2 and h3

2018-11-08T08:42:05Z

Placemark Title is too big

← Older revision		Revision as of 08:42, 8 November 2018
Line 27:		Line 27:

	== Placemark Title is too big ==		== Placemark Title is too big ==
	~~This problem~~ caused by template styles.
			For placemark title created h2 or h3 tag.

			What tag use - it is component option. Press "Options" button (for example, in map list), scroll down to find '''HTML tag for InfoWin Title'''.

			Problem of big title caused by template styles.

	My template is working well, therefore I correct it to show this situation :)		My template is working well, therefore I correct it to show this situation :)

2018-11-08T08:39:13Z

Placemark Title is too big

← Older revision		Revision as of 08:39, 8 November 2018
Line 84:		Line 84:
	You can also define not for special template section, for example, change styles like		You can also define not for special template section, for example, change styles like

	<~~code~~>		<pre>
	h2.placemarkHead,		h2.placemarkHead,
	h3.placemarkHead {		h3.placemarkHead {
	font-size: 1.4em;		font-size: 1.4em;
	}		}
	</~~code~~>		</pre>

	Open your template CSS file and add into the end.		Open your template CSS file and add into the end.
	Or you can define different size for h2 and h3		Or you can define different size for h2 and h3
	<~~code~~>
			<pre>
	h2.placemarkHead {		h2.placemarkHead {
	font-size: 1.4em;		font-size: 1.4em;
Line 101:		Line 102:
	font-size: 1em;		font-size: 1em;
	}		}
	</~~code~~>		</pre>

	Or just for class, in this case it will work in any case of component option		Or just for class, in this case it will work in any case of component option
	<~~code~~>
			<pre>
	.placemarkHead {		.placemarkHead {
	font-size: 1em;		font-size: 1em;
	}		}
	</~~code~~>		</pre>

	== Infowin or Zoom control has bad shape ==		== Infowin or Zoom control has bad shape ==

2018-11-08T08:38:05Z

Placemark Title is too big

← Older revision		Revision as of 08:38, 8 November 2018
Line 82:		Line 82:


			You can also define not for special template section, for example, change styles like

			<code>
			h2.placemarkHead,
			h3.placemarkHead {
			font-size: 1.4em;
			}
			</code>

			Open your template CSS file and add into the end.
			Or you can define different size for h2 and h3
			<code>
			h2.placemarkHead {
			font-size: 1.4em;
			}

			h3.placemarkHead {
			font-size: 1em;
			}
			</code>

			Or just for class, in this case it will work in any case of component option
			<code>
			.placemarkHead {
			font-size: 1em;
			}
			</code>

	== Infowin or Zoom control has bad shape ==		== Infowin or Zoom control has bad shape ==

2016-11-11T08:48:11Z

Error: Oops! Something went wrong

← Older revision		Revision as of 08:48, 11 November 2016
Line 15:		Line 15:
	[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]		[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]

	You have to get API key and enter it into component [Zh_GoogleMap_Description#OptionsAnchor options].		You have to get API key and enter it into component [[Zh_GoogleMap_Description#OptionsAnchor\|options]].

	== Error: link.hasClass is not a function ==		== Error: link.hasClass is not a function ==

2016-11-11T08:47:22Z

Error: Oops! Something went wrong

← Older revision		Revision as of 08:47, 11 November 2016
Line 15:		Line 15:
	[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]		[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]

	You have to get API key and enter it into component options.		You have to get API key and enter it into component [Zh_GoogleMap_Description#OptionsAnchor options].

	== Error: link.hasClass is not a function ==		== Error: link.hasClass is not a function ==

2016-11-11T08:45:53Z

Error: Oops! Something went wrong

← Older revision		Revision as of 08:45, 11 November 2016
Line 1:		Line 1:
	== Error: Oops! Something went wrong ==		== Error: Oops! Something went wrong ==

			If you've got on site page error like

	[[File:Error-Oops-Key.png]]		[[File:Error-Oops-Key.png]]

	~~This message~~ in browser console caused by: Google started require Google Maps JS API Key for new sites (after June 22, 2016)		And in browser console you can see messages:

			Google Maps API error: MissingKeyMapError

			Google Maps API warning: NoApiKeys

			It caused by: Google started require Google Maps JS API Key for new sites (after June 22, 2016)

	[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]		[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]

2016-11-11T08:42:07Z

← Older revision		Revision as of 08:42, 11 November 2016
Line 1:		Line 1:
			== Error: Oops! Something went wrong ==

			[[File:Error-Oops-Key.png]]

			This message in browser console caused by: Google started require Google Maps JS API Key for new sites (after June 22, 2016)

			[https://developers.google.com/maps/pricing-and-plans/standard-plan-2016-update Read more]

			You have to get API key and enter it into component options.

	== Error: link.hasClass is not a function ==		== Error: link.hasClass is not a function ==