robwent

There is no manifest file showing on your site.

In the plugin settings, at the bottom of the page – does it say that the manifest file exists with a link to it?

Your site looks like it has other plugins compressing and optimising the output, so you should clear the cache from all of those plugins.

Maybe turn off all caching and then check. Clear cache and turn them back on if it’s working.

I think this is browser behaviour which cannot be altered. EG only chrome adds the ‘add to homescreen’ popup, Firefox adds an icon to the url bar.

If you look in the addons menu item there is a campaign tracking addon. You can add a parameter there which will add ?urm=WHATEVER to the pwa homepage so you can see in Google analytics campaigns how many people open the homepage of the pwa.

The start page is added in the manifest file so I’m not sure this is possible.
The manifest is cached and the same for all users.

You’re probably using a filter to strip yoast comments out of the head of the site which is now interfering with the new json schema.

Either remove or adjust it.

https://www.robertwent.com/blog/remove-yoast-html-comments-in-version-11-0/

There is a note on the plugin homepage that this is currently not possible and may be added in the future.

Confirmed.

Many thanks!

Probably easiest to only load it when the shortcode has been called?

Also, I don’t think v2 has been deprecated yet? But if you had v2 keys set then they now seem to have been removed.
So people who previously had a working recaptcha, now just show [recaptcha] and have no protection.

I found a similar issue with the pods framework and a patch here: https://github.com/pods-framework/pods/commit/a7544b727b6cce3ea18c7565d334141ab56389ef

So I just modified the file with a similar fix: https://gist.github.com/robwent/3cd0726388dfb6071066c4e0f433632c

And now it’s working again.

ah ok, can’t help then sorry.

I would suggest opening a new topic with details of the issue.

@cim

I think I got an answer in another thread.

I put the firewall back into learning mode and then the command worked.

When the learning mode turned off it continued to work.

You would do the same as for any other field in ACF so best to read through the documentation for the main plugin.

If you are using a theme made by someone else then you need to create a child theme, so your changes aren’t overwritten when updating.

I think after learning mode it’s now working.

At least the cron emails just show php header information, no blocks ??

I think this can be marked as resolved.

Thank you!

Thanks Tim,

I’m still here ??

I set the firewall to learning mode a couple of days ago.

The cron command doesn’t get blocked.

I thought I had set the learning mode to end the following day but it was a week.
So I just changed it again to end tomorrow to see if it’s ok after that.

Is there no other way to whitelist things like this?

It seems like putting the firewall into learning mode effectively disables it?

Turning off extended protection doesn’t make any difference. The problem is the same.

I’m seeing the same issue when trying to run the relevanssi index command through wp-cli.

https://www.relevanssi.com/user-manual/wp-cli/

I ran it originally through ssh to test and it ran fine, so I then set up a cron to run every 2 hours and the cron email from cpanel says it was blocked by wordfence.

https://gist.github.com/robwent/faf6e133bea51405cb91b520014efc9e

Runs as the same user I was using through ssh.

EDIT: I should add that I have extended protection enabled which I assume may be part of the problem.

• This reply was modified 6 years, 2 months ago by robwent. Reason: More info