Alin (a11n)

Hi @jungle7, @jackmeat,

Thank you so much for the report, and especially for the troubleshooting you’ve already done, it’s a huge help. I’ve raised this internally with our engineers. They’re investigating now and I’ll get back to you as soon as we have news.

In the meantime, if it helps, you can try manual sharing from Jetpack Social to Instagram as a temporary workaround. It’s not ideal, but it might unblock you while we identify the root cause.

Thanks for your patience.

Best,
Alin

Hi @yachtchefjobs,

Alin here from the WP Job Manager support team. Thank you for your patience here.

What’s happening is that Resume Manager’s “Apply With Resume” feature is taking over the Apply button, which is why you’re seeing “Apply using your online resume” instead of the Applications form.

Here’s what to check:

1. Resumes > Settings > Apply With Resume section:

• Uncheck “Force Apply With Resume” (this is the main one – it forces Resume Manager’s apply form and hides the Applications form)
• Uncheck “Force Resume Creation” if it’s enabled
• You can also disable the “Email Based Applications” and “Website Based Applications” toggles in this section if you don’t want the “apply with resume” option at all

2. Job Applications > Settings > Application Forms tab:

• Make sure “Email Application method – Use application form” is enabled
• Make sure “Website URL Application method – Use application form” is enabled

3. On each job listing (Job Data section):

The “Application email/URL” field must contain a valid email address or URL. If this field is empty, the Apply button has nothing to work with and the Applications form won’t appear.

After making these changes, test by opening a job listing in an incognito window and clicking Apply. You should see the Applications form with the file upload and cover letter fields.

Regarding your second goal – having a simple candidate profile that employers can pay to view – Resume Manager can handle that side of things. It’s a separate setup topic, so once your apply flow is sorted, feel free to open a new thread and we can point you to the relevant docs.

One thing to note: this ww.wp.xz.cn forum officially supports the free WP Job Manager core plugin. For detailed support with paid add-ons like Applications and Resume Manager, you can also reach us at wpjobmanager.com/contact/ where the full support team can look at your specific setup.

Best regards,
Alin

Hi @alessandropreviti,

Thank you again for the extremely thorough investigation, I went through everything carefully and also reproduced some of the XML-RPC tests from my side.

At this point, the issue is much clearer.

The main problem is not Facebook itself or Jetpack Social specifically, but the underlying Jetpack connection with WordPress.com.

Your site currently shows as connected in wp-admin, however the Jetpack connection is not healthy. The reason is that authenticated POST requests to the XML-RPC endpoint are being blocked by the hosting server.

In practice:

• GET requests to xmlrpc.php?for=jetpack work correctly
• but POST requests return 401 Unauthorized
• because of this, Jetpack cannot complete authenticated communication with the site
• and features that depend on that communication, including Jetpack Social and Activity Log, fail

Your diagnostics were actually very accurate and consistent with what I’m seeing from the Jetpack side as well.

Regarding your question about the alternate connection method: it can help some Jetpack features work in restricted environments, and that is likely why the site still appears as “connected” in wp-admin. However, in your case, the server is still blocking the authenticated XML-RPC communication required for a healthy Jetpack connection, so Jetpack Social cannot complete the connection process successfully.

So unfortunately, based on the tests and server responses, this does not appear to be something we can fully fix from the Jetpack side alone while the hosting restrictions remain in place.

At this point, the realistic options would be:

• ask the host whether they can specifically allow Jetpack/WordPress.com authenticated communication,
• migrate to a host that supports standard WordPress XML-RPC/Jetpack communication,
• or use a different social sharing solution that does not rely on the Jetpack connection architecture.

I know this is probably not the answer you hoped for, especially after all the time you spent debugging this, but your investigation was genuinely very helpful in identifying the root cause here.

Hi @yachtchefjobs,

Looks like you got this sorted, but in case it helps anyone else landing here:

The Job Alert email is built from the Alert Email Content field at Job Manager → Settings → Job Alerts, the same place where you set the colors. It does not go through the standard email header template, so adding a logo is done directly in that field.

Custom code falls outside what we can support on the forum, but a developer can help you add an image tag at the top of that field, pointing to your logo hosted on your site.

Alin

Hi @amwosi,

Thank you for your patience while we looked into this.

Unfortunately, this is a known limitation that isn’t specific to Jetpack, it affects all sharing plugins. Over the past several years, Facebook has progressively restricted access to share count data through changes to their API. As a result, Facebook share counts no longer display reliably on any third-party sharing buttons.

That’s why none of the plugins you’ve tried have been able to show the count, the data simply isn’t made available by Facebook the way it used to be.

We understand this is frustrating, especially since it worked before. Unfortunately, this is entirely on Facebook’s end and there’s nothing we can do to restore it.

Since there’s no action we can take on our side, I’ll go ahead and mark this thread as closed. However, if you have any other questions or need help with anything else, please don’t hesitate to open a new thread, we’re happy to help.

Best regards!

Hi there,

Thank you for sharing your positive experience with WP Super Cache! It’s great to hear that it’s significantly improved your website’s performance. For those looking for advanced caching options, WP Super Cache is indeed a powerful and free solution. If anyone needs guidance on setting it up, they can refer to the WP Super Cache setup guide.

Thank you!

Hi @sjyounis,

No need to worry here, those files are not malicious.

They’re normal cache files generated by WP Super Cache. These files can include parts of requests made to your site (such as URLs or query strings).

When Wordfence scans those cached files, it may flag certain patterns as malicious, even though they are just stored request data and not actual malware on your site.

This behavior has been confirmed in similar cases and is generally considered a false positive in this context (see here).

If you want to double-check:

• Run a full Wordfence scan, if only cache files are flagged, you’re safe
• Make sure everything is up to date (plugins, theme, WordPress)

To stop the alerts:
You can exclude the cache folder from scans:

• wp-content/cache/supercache/*
• Or simply ignore those results after a scan.

If you see anything flagged outside the cache folder, feel free to share it here and we’ll take a closer look.

Best,
Alin