Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.0.BETA, EE-3.3.0.GA_P02
-
Fix Version/s: 4.0, EE-3.3.0.GA_P03
-
Component/s: ACE-Components
-
Labels:None
-
Environment:Any
-
ICEsoft Forum Reference:
Description
It was reported in the forum and by product support that Google Maps controls weren't showing for all components using the Google Maps API.
It's almost 100% sure that this is an issue on the Google side, since these components haven't been modified recently.
The cause seems to be the use of the edge/latest API version, which is the default when not specifying a specific version. So, in order to avoid this kind of issues in the future, here are two options. We can follow either of them or both.
1) Use an earlier, more stable gmap API version by default. Let's say 3.11, as the forum poster suggested (latest version is 3.18 at the moment).
2) Add a context parameter that we read in the GMapResourceHandler.java where users can specify a particular API version to use. The default would be to use no parameter at all, which is interpreted as the edge version.
It's almost 100% sure that this is an issue on the Google side, since these components haven't been modified recently.
The cause seems to be the use of the edge/latest API version, which is the default when not specifying a specific version. So, in order to avoid this kind of issues in the future, here are two options. We can follow either of them or both.
1) Use an earlier, more stable gmap API version by default. Let's say 3.11, as the forum poster suggested (latest version is 3.18 at the moment).
2) Add a context parameter that we read in the GMapResourceHandler.java where users can specify a particular API version to use. The default would be to use no parameter at all, which is interpreted as the edge version.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion