Wpgeodirectory

Hi there!

I’ve reached out to them about this issue three years ago (when TSF was still a baby).

It seems there was an issue with the Location Manager’s proximity search. This is a premium add-on of theirs and not the plugin itself. So, they incorrectly listed the main plugin as incompatible.

I don’t know what the statement should’ve entailed, nor was I able to find any issues with the premium add-on myself. I do think it’s funny that they contradict their following statement four rows down.

So, I think you’re safe to combine the plugins. If, however, you do find issues, then feel free to reach out to us!

Hi, @theukdirectory! I looked at WPGD forums, and it seems that they are currently not experiencing any issues with TSF. Honestly your best bet is trying using latest TSF alongside with latest WPGD and then test your website using Structured Data Testing Tool. Or provide us with link to your website, so we can have a peek at your website ??

Historically speaking, there was an issue nearly 2 years ago with conflicting metadata, meaning both plugins were trying to generate same type of data. There was rather simple solution, that might still apply, check WP Geo Directory forums. More detailed discussion about the incompatibility went on here in WP forums. TSF author, @cybr contacted the guys behind WPGD — however, their conversation is private and it has been almost 2 years since it took place.

Hey, Thanks for getting back to me,

I thought the duplicate metadata might be an issue, but I notice that you can disable TSF on custom post types so I was just going to do that for the WPGD post types, and leave the meta data alone for the directory posts.

• This reply was modified 6 years, 4 months ago by theukdirectory.

That should do the trick! You should check the structured data either way, just to be sure (I provided link above). For others, that might stumble upon this topic, you can disable TSF meddling with WPGD just by checking Places in settings.