Jen H. (a11n)

Hi @riojaner2!

Thanks so much for your patience as we work through a bit of a support backlog. Since your site is hosted on WordPress.com, you have access to direct support where we can look into this using our internal tools. The ww.wp.xz.cn plugin forum is best suited for self-hosted Jetpack sites, and we’re limited in what we can do from here. Please contact us through your WordPress.com dashboard.

From there, we can check our system for what might be going on with your subscriber.

Thanks a bunch!

Hello @yachtchefjobs! Thanks so much for your patience as we work through a bit of a support backlog.

Please don’t give up! You’ve made solid progress here. Getting the right Google Maps APIs enabled (Places, Geocoding, and Maps JavaScript) was the trickiest part, and it sounds like that’s done.

The “referer restrictions” error you hit earlier happens when an API key with HTTP referrer restrictions is used for server-side requests like geocoding, so removing those restrictions was the right fix.

For the map on your Find a Job page, the zoom level, world view, and job pins are all controlled by your Jobify theme, not by WP Job Manager. WPJM core handles geocoding (converting a location into latitude/longitude coordinates), but the visual map display is a theme feature. Jobify’s support team would likely be the ones to help with those settings.

On the geocoding custom fields: WPJM stores these as hidden post meta (geolocation_lat, geolocation_long, geolocation_city, etc.) on each job listing. They won’t appear as visible fields in the job editor by default, so what you saw is actually expected behavior. To confirm they’re being saved, check the Custom Fields section at the bottom of a job listing in WP Admin. You may need to enable it via Screen Options at the top of the page.

So to recap, your API setup seems good and geocoding should be working behind the scenes. The remaining piece, getting the map to display the way you want, is something Jobify’s support can help with.

If you have any other questions about WPJM itself, feel free to reach out to us.

Hey @bahus, thanks for letting us know! Let us know when you need us in the future. 🙂

Hey @ajdiseker – thanks for reaching out about this. While I can’t definitively confirm that this explains what you’re noticing, I do see that Jetpack is currently not properly connected to your site. I’m seeing the following error in our connection debugger:

cURL error 28: Operation timed out after 30002 milliseconds with 0 bytes received

Usually this points to a problem on your host’s end of things, like poorly resourced servers or something blocking you from connecting to the WordPress.com (Jetpack) servers. Please make contact with your host’s customer support and ask them to do the following:

1. Allowlist connections to and from *.wordpress.com.
2. Allowlist the following IP ranges: https://jetpack.com/support/hosting-faq/

Once you’ve done that, please try reconnecting Jetpack. If you’re properly connected, you’ll see Everything looks great! here.

Reconnecting to Jetpack won’t restore any lost stats data (Jetpack has to be connected to be able to gather visitor info), but you should see a return to your typical numbers in the coming days. Please let us know if you don’t, and we can take a closer look. 🙂

Cheers!

Hello @todga! Thanks for that. I noticed in your original post here that you mentioned “The widget can be above or below on the Post Page.” Does this mean you don’t want the widget in a default widget area like a sidebar, header, or footer?

Generally speaking, we’re Jetpack experts, not GeneratePress experts, so I’ll need to offer pretty high-level guidance here. While Jetpack can control where a widget shows, GeneratePress controls where widget areas exist. So, depending on where you want the widget to show, you may first need to set up or enable a widget area in that spot in GeneratePress (assuming it doesn’t already exist), since our widget visibility only works on content in a registered widget area. It looks like GeneratePress has a beautiful visual guide for hooks to modify the theme here, but I’d recommend reaching out to their support for definitive guidance on this.

Does this help?

Thank you, @aurelierm! We will be in touch. Since we’ll be corresponding via email, I’ll go ahead and mark this thread as closed.

Cheers!

Hello @joannewilliamsfuel – thanks for sharing that screenshot and describing your issue.

This error is caused by a faulty plugin, theme, or perhaps an update that went wrong – not directly related to Jetpack CRM. You would have received an email from WordPress to your WP Admin administrator email address with instructions on what to do next. Your host’s customer support will be the best place to contact for help with this if the email you received doesn’t help you get it resolved.

Once your site is back up, please reach out here and let us know if you need any additional assistance with Jetpack CRM. 🙂

Good luck!

Hey @almendron – thanks so much for following up, and thanks especially for your willingness to figure this out with us! We’ll stand by for more information from you, in case there’s something we need to pass onto our engineering team.

Cheers!