Hi @farbfotobigfan, thanks for getting in touch.
Do you receive blocks for this plugin in Wordfence’s Live Traffic page? If you do, clicking the “eye” icon to expand should show you an exact reason why Wordfence thought it was unsafe. You can choose to allowlist the action(s) from here, which is designed for false-positives that you know are safe actions from a plugin you installed.
If you don’t see these specific blocks and are instead experiencing functionality problems, it could be worth putting Wordfence back into Learning Mode. From the Wordfence Dashboard click on Manage WAF. Then you will see Basic Firewall Options > Web Application Firewall Status. Change the option to Learning Mode. Now perform the actions with WP/LR Sync that were causing issues. This will help Wordfence learn that these actions are normal and it will allow them in the future. After you have finished performing the actions, switch the WAF from Learning Mode back to Enabled and Protecting. Now test to see if these actions work correctly.
As a side-note, the REST API can be disabled with other plugins but not through Wordfence or WordPress natively so I don’t expect that to be part of the issue you’re seeing unless you’ve purposely disabled it previously in this way.
Let me know how you get on!
Peter.
Hi Peter
Thanks a lot for your detailled reply. Alas I did not succeed until now.
It appears after looking into live traffic of Wordfence that the connection does not reach WordPress. In Lightroom the following window always appears:
“This collection cannot be actualized.
A internal mistake has occured: wplr.lrplugin/WPLRSyncExportServiceProvider.lua:661: attempt to compare number with nil”
Any idea?
That sound very clingonic to me and I’m waiting for support from the developper.
Greetings!D.
Hi @farbfotobigfan,
With the sync issues page you’ve linked me, have you already tried allowlisting the /?wplr-sync-api query string in Wordfence using Wordfence > All Options > Allowlisted URLs? You would need to ADD:
- URL: /
- Param Type: Query String
- Param Name: wplr-sync-api
If the above doesn’t help, unfortunately I’ve not encountered the issue with this plugin combined with Wordfence before to give any insight into what may have worked for other customers. The “compare number with nil” error seems to be coming from the WP/LR plugin but the cause of an invalid value can sometimes be due to a failed operation elsewhere which is where Learning Mode or allowlisting the URL above manually as per their instructions may help.
We would always be interested to hear from the plugin developers if they believe Wordfence is blocking something that is unresolvable from their end or using our existing options, as we have worked with other developers in this way before.
Thanks again,
Peter.
