I used to run a zap where any new YouTube video posted in my channel would automatically create a WordPress post. I don’t know what happened in the last month. But that zap doesn’t work and gives me an error when I try to reconnect WordPress.
So I switched to IFTTT to automate posts. But I get the same problem – WordPress connection is not getting established.
I am not able to understand what is the possible root cause of the problem because the XMLRPC file is in the root folder. Can anyone please help me understand why is this happening?
]]>ifttt.com
to post my articles to my blogger, but i need a direct link to RSS (XML file) not the /feedwww.website.com
/rss.xmli can’t find a solution.
]]>A week and a bit ago I was having issues with IFTT on my blog. I have an applet to post new posts on social media. IFTT had disabled the applet as it was unable to connect to my blog.
I disabled a setting in Cloudflare blocking bots, and turned Wordfence to learning mode. Both of these things solved the issue and the IFTT applet worked.
Now Wordfence has come out of learning mode and the issue is happening again.
Would there be a rule that is interfering with IFTT?
Thanks
]]>I have tried everything I can think of in working to solve this issue. Anyone know what causes this? I notice that it only happens with my wordpress blog, not my Blogger.com blog, or Tumblr.
I reached out to IFTTT support and even Linden Tibbets, its CEO. No response. The alternatives to IFTTT that I know of are really not that because they’re tied to the YouTube API. So, if one hits a “quota” the new video-posts on your WordPress stop, or don’t happen. That’s not the case with ITFFF.
Plus, I have the pro version, and yet can’t get support. Any ideas?
]]>This I know because I deactivated every single plug-in on my WP installation, the only plug in active was Next Gen Gallery.
When it is active Zapier.com, ifttt.com can not logged in.
When I turn off and deactivates Next Gen Gallery then suddenly it starts working and Zapier.com, ifttt.com is able to log in.
This I repeated to be sure several times turning Next Gen Gallery off and on.
My Next Gen Gallery Version 3.8.0
]]># BEGIN rlrssslReallySimpleSSL rsssl_version[3.2.9]
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{HTTPS} !=on [NC]
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/
# The following condition added to make ifttt connection work
RewriteCond %{REQUEST_URI} !^/xmlrpc.php
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R=301,L]
</IfModule>
# END rlrssslReallySimpleSSL
I hope this makes sense. I also suspect that other services using XML-RPC may well fail for the same reason! Perhaps you could consider adding this to the plugin at some stage in the future?
]]>