[Dylan]

Hi all,

Thank you for your continued time on this and my apologies once again for the trouble experienced.

We are currently attempting to recreate these issues on our side.

Please could I ask you to share your PHP error logs with me via this thread so that we can look into this issue a bit further? (Please mark your reply as a private reply)

This would be a tremendous help in determining the root cause of the issue.

[Dylan]

Hi Benni,

Thank you for getting in touch, we do appreciate your time.

Unfortunately, this feature has not been developed at this stage.

I will raise this with our lead developer to ensure we look into this in the near future.

My apologies for any inconvenience caused by this.

[Dylan]

This reply has been marked as private.

[Dylan]

Hi there,

Our sincerest apologies for the trouble experienced.

I received your email regarding this issue and I have replied to you.

Please do let me know if you have received the email so that we can discuss this further.

I am eager to assist you in resolving this issue.

[Dylan]

Hi Gowtham,

Thank you for getting in touch, we do appreciate your time.

Our apologies for the trouble experienced.

I ran a few tests on your website and it appears you are using an outdated version of the Pro add-on. The issue you are experiencing was a known issue in earlier versions of the Pro add-on.

Could I ask you to confirm your purchase email address for me in a ‘Private Reply’ so that I may email you a new download link along with upgrade instructions?

I look forward to hearing back from you.

[Dylan]

Hi there,

Unfortunately, due to the reasons mentioned in my previous response, we load our bundled PO files instead of the community-driven PO files.

As mentioned I am in the process of discussing the ability to disable this moving forward as a setting within the plugin.

I do apologize for the inconvenience, however, we do not currently have an option to disable this. If you are using a translation management plugin, these do override our text domains in most cases.

The issue has been submitted to our lead developer for consideration moving forward.

[Dylan]

Hi there,

Thank you for taking the time to get in touch, we do appreciate your time.

My apologies for the trouble experienced, I am eager to assist you in getting this resolved.

I ran a few tests on your website and it appears you may be using our XML load method for marker data. Unfortunately, it appears that this is failing within your environment.

Could I ask you to navigate to Maps -> Settings -> Advanced -> And change the option labelled ‘Pull marker data from’ to ‘Database’ -> And save your settings.

Once complete, please clear all caching on your website.

I believe this should resolve the issue with markers not displaying on the front end.

I look forward to hearing back from you.

[Dylan]

Hi there,

Not a problem at all, thank you for taking the time to discuss this with me further.

After looking at our core I can confirm that we do prioritize the language files included with our plugin in ‘/plugins/wp-google-maps/languages’. The reason we do this by default is that our bundled PO files are usually more updated than the versions loaded from WordPress directly.

In cases where our translations are directly updated by WordPress.org Translation Contributors, they often need to be approved by a Translation Editor before being included and deployed. For many languages which are supported by our plugin we do not have Editors who approve them, or approval may take excessively long as it is all community-driven.

When we receive an updated PO file from one of our users directly we have found that these files are often more complete and can be deployed with the next update we release.

I will discuss the possibility of switching to the community-driven language files as a setting moving forward for those interested in making use of this. I will need to discuss this with Perry, the lead developer, as it may require various changes aside from the filter mentioned in your reply.

In the meantime, a possible workaround which I have used in the past is to edit the PO file which ships with our plugin, and store the compiled MO file. Copy these to the wp-content/languages directory so that you have a version of them stored outside of our content folder.

I hope this helps? Once again, thank you for your time, I will discuss the ability to toggle off the use of our bundled translations with Perry tomorrow.

[Dylan]

Hi there,

Thank you for your feedback I do appreciate it. 🙂

I have looked through our release logs and I can confirm that we have not made any major changes to our text-domain recently.

This is quite strange admittedly as this is controlled entirely by the WordPress core. These community files do load separately from our bundled language files in some cases, although they should not.

With that being said, what I believe may be happening here is that some of our string localizing code may be missing a text-domain reference.

I believe WordPress is then loading the standard PO files and storing them in the base languages folder as our custom text-domain is ignored.

We are currently looking into this further, however, it does appear this is the case. If so, we will be releasing an update to resolve the missing references to the text-domain which should restore the standard file loading.

I hope this helps?

[Dylan]

This reply has been marked as private.

[Dylan]

Hi there,

Thank you for your time, we do appreciate it.

Our sincerest apologies for the trouble experienced. We are aware of this issue with our latest update.

We are currently looking into this further to determine the root cause of the issue. We will be working towards a patch which should resolve this in the next few days.

I will provide you with more feedback as soon as possible. Are you open to a temporary solution in the meantime?

Kind Regards,
Dylan Auty

[Dylan]

Hi there,

Thank you for your time, we do appreciate it.

Our PO/MO files are stored in the following directory: wp-content\plugins\wp-google-maps\languages

These PO files are maintained internally by our community and submitted to us directly. Our text-domain is set up to support this structure.

With that being said, in some environments, WordPress will download the publicly maintained language files instead, as found here: https://translate.wordpress.org/projects/wp-plugins/wp-google-maps/

In these cases, the PO files will be stored in the shared language files instead.

I hope this helps clarify?

[Dylan]

Hi there,

Thank you for confirming.

Please add the following JavaScript to your settings area:

WPGMZA.ProStoreLocator.prototype.onFilteringComplete = function(event)
	{
		var params = event.filteringParams;
		var circle = this.circle;
		var marker = this.marker;
		var factor = (this.distanceUnits == WPGMZA.Distance.MILES ? WPGMZA.Distance.KILOMETERS_PER_MILE : 1.0);
		
		WPGMZA.StoreLocator.prototype.onFilteringComplete.apply(this, arguments);
		
		if(marker)
			marker.setVisible(false);
		
		if(circle)
			circle.setVisible(false);
		
		if(params.center && marker)
		{
			marker.setPosition(params.center);
			marker.setVisible(true);
			
			if(marker.map != this.map)
				this.map.addMarker(marker);
		}
		
		if(params.center && params.radius && circle)
		{
			if(circle instanceof WPGMZA.ModernStoreLocatorCircle)
				circle.settings.radiusString = Math.round(params.radius);
			
			circle.setRadius(params.radius * factor);
			circle.setCenter(params.center);
			circle.setVisible(true);
			
			if(circle.map != this.map)
				this.map.addCircle(circle);
		}
	}

This can be added under Maps -> Settings -> Advanced -> Within the Custom JavaScript box.

I hope this helps?

[Dylan]

Hi there,

Thank you for getting in touch, we do appreciate your time.

Please confirm which version of the Pro add-on you are making use of on your site? This can be found under Plugins, by scrolling down to the WP Google Maps Pro add-on and identifying the version number listed here.

Depending on the major version being used on your site, I will provide you with the needed code for the version installed on your side.

I look forward to assisting you with this.

[Dylan]

Hi Randal,

Thank you for getting in touch, we do appreciate your time.

If you are making use of our Gold add-on, you may want to look into using our marker separation tool. This allows you to create a web of markers which become visible when the user clicks on a stack of markers as described.

We have a demonstration of this here: https://www.wpgmaps.com/demo/near-vicinity-markers/

This could then also be used alongside our marker clustering system, also included in the Gold add-on, to give the user an indication that a group exists. A demo of this can be found here: https://www.wpgmaps.com/demo/marker-clustering/

Alternatively, if you are not using the Gold add-on, you may then need to edit the individual markers and change their placement location slightly.

I hope this helps?

[Author]

Posts