- This topic has 6 replies, 3 voices, and was last updated 5 months, 1 week ago by hgg.
April 16, 2020 at 7:50 am #58754hggMember
after updating to the new version 8.0.26 no markers are shown on our development environment.
more information will follow (private)
Hans-GerdApril 16, 2020 at 12:14 pm #58771PerryModerator
We have fixed this as a matter of urgency in Pro 8.0.27 which will go to release within the next 24 hours.
I did try to apply a hot fix on your site however it appears that my account has been revoked,
Please update to 8.0.27 as soon as it becomes available.
– PerryApril 16, 2020 at 2:29 pm #58779pegasus1134Participant
Had the same issue. I have updated to 8.0.27. I see the markers now but not custom markers. Only the generic red marker is seen. Not even able to edit and change it to custom markers. Please fix it ASAP!April 16, 2020 at 2:46 pm #58782hggMemberThis reply has been marked as private.April 16, 2020 at 2:55 pm #58785boatsRusMember
Cannot edit maps, see Chrome error
Attachments:You must be logged in to view attached files.April 17, 2020 at 2:18 pm #58804PerryModerator
It appears that at least one of these sites is attempting to load the language JSON using the /en/ part of the URL which leads to a redirect followed by a 404.
We’ll add a fallback for this whilst we look into the issue, with a view to deploy that early next week, I do apologise for any inconvenience caused.
Unfortunately it’s not possible for us to provide a quick fix for this due to the code structure, however please rest assured we will patch this as a matter of urgency as soon as we possibly can.
– PerryApril 17, 2020 at 8:54 pm #58813boatsRusMember
In my case, this was fixed by correcting the json file name, check our chrome console output to see what the problem is.April 18, 2020 at 7:37 pm #58815hggMember
no problem at all: I keep the earlier version on the live website for now.
Hans-GerdApril 19, 2020 at 12:50 pm #58820PerryModerator
I can see there is a mismatch in case for the Finnish JSON file which we have now corrected at our end.
Hans, I can see that this issue relates specifically to OpenLayers, we are working to fix this issue for the next patch.
– PerryApril 20, 2020 at 7:50 am #58821hggMember
thanks for info.
No problem at all – for now I keep the earlier version on the Live website.
- You must be logged in to reply to this topic.