tallhat

had this too. anyone know WHY (thanks for the workaround fix though. worked for me too).

is that the only option? I’m not looking for a full translation, just the ability to change the text of that one field. it would be great if you could make the placeholder text of the key fields customisable in the settings of the GiveWP plug-in rather than needing a whole translation layer on top.

thanks

Fantastic – this is working now! Thanks for the speedy fix, great stuff.

I did send screenshots a week ago to the contact form. I can’t share a link as it’s a dev site, and anyway we’ve reverted to 3.5.1 for now, so that wouldn’t really help.

hi there, thanks. Have tried 3.6.1 but still a similar issue. it’s either ignoring the Shortcode settings (for number of logos across) OR the width/height calculations are wrong now. 3.5.1 is ok but all the higher versions i’ve tried have given the same problem. I’m not saying the heights are ‘hard-coded’ clearly they are calculated on the fly, but something is wrong in the new versions. I’ll send a couple of screenshots to your contact link.

But as an example, in the GS logo code I have this difference for the logo wrapper divs (“gs_logo_single–wrapper” class):
3.5.1: “style=”height: 117px;””
3.6.1: “style=”height: 156.391px;””

and the ONLY difference is the GS logo plug-in version, nothing else in the site changed.

Hi there, thanks for the response. I have managed to get the 3.5.1 version off my backup, so am ok for now using this version. I tried 3.6.0 this morning, but this doesn’t solve the issue (the changelog for 3.6.0 doesn’t mention this sizing issue it just says “[Improved]: Compatibility Checking With Pro Version.”).

I can’t give a link i’m afraid as a) it’s a private dev site and b) i’ve rolled back to 3.5.1 so it doesn’t show the issue anyway.

it’s definitely something to do with the style=”height: 48px” code mentioned above. 3.5.1 doesn’t inject hardcoded px heights like that (it seems to use widths and percentages)

Hi, why does this say resolved when there is no answer? Thanks

hi there. sorry i missed this one. could you clarify what is meant by “Ask them to check with the AJAX responded after dragging & drop the items”. what does that mean exactly? what should they DO? thanks. (have you come across this issue before?)

sorry, yes it was a WPML issue. WPML 4.5.8 fixes this

hi, don’t spend too much time on this. i’ve just seen it MIGHT be a WPML issue – their latest 4.6.8 changelog says “Fixed an issue that caused that same taxonomy terms to be assigned to the last queried object.” which sounds like it might be involved. let me try and upgrade WPML first and i’ll report back here.

the first link is what i see with [spotmap map-overlays=openseamap] in my WP.
the second is what i see at https://map.openseamap.org/ with seamarks ticked in the dropdown.

have sent you an email now. thanks

harbours would be a great start (and might give me a pointer on how to edit the maps.json file to play with other layers). marine profile would be amazing if possible, and even marine traffic would be interesting for our project.

one thing. i used [spotmap map-overlays=openseamap] and i note the SEAMARKS (which are referenced in the maps.json) file still don’t show up on my map.

compare
https://bigbluekayak.com/basemap.jpg
with https://bigbluekayak.com/basemap-seamarks.jpg

can i send you a link privately?

hi again, any advice on turning on the other openseamap layers? have been looking at the maps.json file but can’t figure out how to turn on harbours, depth profile layers etc.

thank you. am so close! our project launches in the next couple of weeks.

thank you. yes the base map looks right, but on https://map.openseamap.org/ i can turn on other layers like water depth, marine traffic, depth profile etc. – am i able to do that via the shortcode? (if so how). thanks!

hi, i haven’t changed the default values before. i’m able to edit and save the ‘Feed’ tab settings, but not the last ‘Defaults’ tab settings.
Shortcode displays ok, and i can change the HEIGHT setting in there actually so it’s not the end of the world, i can work around.
one thing, i am using PHP8.1x on my server, don’t know if that might be an issue

thank you. (did you see my other post recently? re opensea)