Tagged: x
-
AuthorPosts
-
January 16, 2017 at 5:16 pm #1332721
I am just confused. One answer points to another post, that intern points to another. I see no real solutions really. I’m sure I missed it somewhere, but my eyes got tired. I really don’t care if it’s Cornerstone or not. If I have to put a function in Function.php temporarily ignore the API or whatever, where ever.
Then A person says “it worked”, but is back in a month an says the same issue exists again? Is this issue fixed, or for the maps do I just look elsewhere for them…NOT FOR THE THEME!!!! Just for the map solution.
January 17, 2017 at 12:56 am #1333121Hi there,
Thanks for writing in! Kindly specify your problem properly. Let us know where you have used map but not working. Provide your URL and login credentials in private reply so that we can check. All you need to use your API Key, correct latitude and longitude and it should work fine if there is no interference with any other plugin.
Hope this makes sense.
January 17, 2017 at 1:38 pm #1333962All I was saying, is I saw post after post where either people couldn’t make it work at all (the posts varied in dates in dates no doubt), existing maps stopped working, or both etc. In my case ALL existing maps still work?? The issue I do have is when I tried to use a new map the way I was used to I got a JS error.
I do NOT use a MAP, or CACHING plugin.
Certainly it all makes sense if thats all there is to it. I’ll try again harder I guess. Thanks
January 17, 2017 at 2:39 pm #1334056Hi There,
Maps should work.
Would you mind providing us with login credentials so we can take a closer look? To do this, you can make a post with the following info:
– Link to your site
– WordPress Admin username / password
– FTP credentialsDon’t forget to select Set as private reply. This ensures your information is only visible to our staff.
Thanks
Joao
January 17, 2017 at 5:39 pm #1334228This reply has been marked as private.January 17, 2017 at 5:46 pm #1334232This reply has been marked as private.January 17, 2017 at 6:46 pm #1334370So, to clearify, all I am am saying now is I can no longer adjust the height of the map…as I could before when I just used the short code like:
[google_map lat=”33.665318″ lng=”-84.036311″ no_container=”true” zoom=”10″ height=”300px” hue=”#022bc1″ drag=”true” zoom_control= “true” drag=”true” ][google_map_marker lat=”33.665318″ lng=”-84.036311″][/google_map]
AND When I use Cornerstone, as I am forced to now (no problem) I just don’t see the map even though everything is correct until I go out of Cornerstone.
January 18, 2017 at 3:42 am #1334759Looks like you’ve set some API restriction. Please check. If you’re not sure how restriction works, please select none (see attachment).
Have you tried adding the shortcode in a Cornerstone Text element? The height should still work. You just need to add a new attribute
api_key
so it won’t generate an error. The shortcode will look like this:[google_map api_key="YOUR_API_KEY" height="300px"]
Thanks.
January 18, 2017 at 1:13 pm #1335467The GOOGLE MAP API I ADDED and am using IS set to “none” (no restrictions—and has been)
1.) My First Google maps in X Theme was not in CornerStone at all, but just through WP “edit page” and X theme short codes.
2.) Later I used CornerStone and the Map Element. It is quite similar to the text Element.
3.) Now I use the Google Map Element in Cornerstone since it allows parameters for API. ZOOM, LNG, LAT etc… (by far the best)
#1 and #2 didn’t work at all—-I got no map tall or short. (I also tried a plain text element as well…same result)
The “height” parameter in the Google Map element in CornerStone has no impact on the map height.
This does, but who knows what else I broke: See attachment…
.x-map .x-map-inner {
padding-bottom: 38% !important;
}Zoom still works fine, width is ok—but this is not overly elegant.
January 18, 2017 at 6:53 pm #1335982<div id=”x-google-map-1″ class=”x-map x-google-map center-text” data-x-element=”google_map” data-x-params=”
-
{"lat":"37.3382082","lng":"-121.8863286","drag":true,"zoom":"12","zoomControl":true,"hue":"#f278a0"}
“>
All the parms are passed exempt the height? (LNG, LAT, ZOOM, DRAG, HUE—but not height…??
I suspect my CSS will break multiple maps (one size only) 🙂
January 18, 2017 at 7:18 pm #1335999Hi there,
There should be no height, it’s calculated on existing width. Example, if the map aspect ration is 16:9, and its initial width is 960px, then the height will be calculated for 540px. And when it’s displayed on mobile that has 767px width, then height will become 431px.
You don’t want your map change width but fixed in height. Unless you really intended to display it differently on each device view. Should it? I could provide extra CSS 🙂
Thanks!
January 18, 2017 at 7:41 pm #1336015In which case the height parameter in the Google Map Element (Cornerstone) really has no meaning there? No problem, I can provide my own CSS where/when the customer asks for it.
Thank you very much. I don’t mean to be a pain, I just thought I was missing somthing as usual.
Thanks,
Charlie
January 18, 2017 at 8:44 pm #1336113This gives me what I want in this case, but is it all wrong?
/* Map Height—no clue */
@media only screen and (max-width: 767px) {
body {
.x-map .x-map-inner {
padding-bottom: 51% !important;
}
}.x-map .x-map-inner {
padding-bottom: 38% !important;
}The aspect stays correct regardless of screen width (if you aren’t overly particular) and begins at the desired height. I know there is a better way!
January 19, 2017 at 2:20 am #1336348Hi there,
I’m not sure about your question, but yes, it has no height option. And you’re also correct with the CSS. Padding define the height, and since it’s percentage value, then it maintains aspect ratio. Percentage value doesn’t work in height, unless it has a parent container to inherit the height.
Thanks.
January 19, 2017 at 11:14 am #1336882I am using Cornerstone 1.3.3 (Google Map Element) (see attachment)
This is my confusion…
Maybe I’m Just doing it wrong, or maybe i’m using the wrong version
-
AuthorPosts