I’ve now setup a new integration which uses some additional tools (Directus and n8n) to help with this process. The below provides a quick run-through of the process and explanation of this approach.

Advantages

Directus provides a quick way of creating an API around data models. They offer a free cloud version which is perfect for this small-scale integration. It can also be self-hosted in a number of ways, including using Docker which makes it very easy to setup.

Note that you don’t necessarily need Directus – you could use a database (e.g. MySQL) and replace the n8n API calls with database queries instead.

n8n (nodemation) is a powerful automation tool similar to Zapier or Logic Apps. You can build workflows to help you achieve complicated processes using simple building blocks. This also has a Cloud version (paid) or a self-hosted version.

Using the above means that I have far more control over what is going out to Mastodon, and can easily be expand to cover additional platforms e.g. Telegram, Slack or Teams.

• messages can be customised to your liking
• messages can be deleted if a post is updated, and you can resubmit
• you use your own Mastodon account so your profile can be managed fully

The Process

1. In Directus create a Collection called ‘rss_feed_items’ with a field called ‘guid’. This is used to track posts which have already been sent to Mastodon to prevent duplicates
2. In n8n, use a Schedule trigger to run every 5 minutes or so
3. Use the RSS block to fetch the RSS feed for your WordPress blog
4. Use the HTTP block to get a list of existing guids from the Directus API
5. Use the Merge block to keep only new blog posts
6. Use a Code block to prepare the message for Mastodon i.e. get the title, link and convert the categories to hashtags
7. Use the Mastodon block to post the message to Mastodon. This is a third-party block at the moment.
8. Use the HTTP block to call the Directus API and create a record for the guid of the blog post

Using this method, if a blog post is updated, I can just edit my post on Mastodon. It could actually be made more sophisticated by keeping the Mastodon status ID and Mastodon post content in Directus with the GUID, and then if the new content is different to the old n8n can delete the old post and create a new post for you.

Note that on the first run, it will send all the posts that appear on your current RSS feed to Mastodon.

Enjoy!

The post Guide: Using n8n to Send New WordPress Posts to Mastodon appeared first on Cube Websites.

After inspecting the requests with the Firebug Console, I saw that the culprit was the request:

/wp-admin/load-scripts.php?c=0&load%5B%5D=jquery-core,jquery-migrate,utils,plupload&ver=4.2.3

I tried the normal fixes such as checking permissions, updating everything, and even reinstalling WordPress but to no avail.  Then I started looking on Google for a potential fix and found this article which not only provides the solution, but also a detailed explanation of why the error occurs in the first place.

As soon as I made the recommended updates, all the sites started working properly with no issue whatsoever.

Full credit goes to the article author.  Just posting here for my own reference more than anything else!

UPDATE: As the original article no longer exists I’ve posted the instructions below:

It turns out the solution to this is quite simple. Nginx and php-fpm need to run as the same user and the directory /var/lib/nginx needs to be owned by that user. Personally I like to run all my web-related services under a www-data user, but running it under a nginx or apache user is also common. To change the user nginx runs under, edit the main nginx config file usually located at /etc/nginx/nginx.conf:

user www-data;
worker_processes 4;
pid runnginx.pid;

Now to change the user php-fpm runs under we need to edit its config file. On my Amazon Linux system this was located at /etc/php-fpm.d/www.conf while on my old Debian setup it was located at /etc/php5/fpm/pool.d/www.conf. There are two user-related settings in the config file. First, if php-fpm runs as a socket (as opposed to listening on a port), the user and group owner of the socket should be set to the same user as nginx so that nginx can access it to run php files. This is not relevant for our error, but can cause other issues if nginx doesnt have permissions to access the socket. Second, the user and group that the php-fpm process runs under needs to be the same as nginx.

    user  = www-data
    group = www-data
     
    listen = varrunphp5-fpm.sock
    listen.owner = www-data
    listen.group = www-dataL

To change the ownership of the nginx lib directory simply run the command chown -R www-data:www-data /var/lib/nginx as root (sudo will do on most systems). Finally, if we edited any config files, we need to restart the appropriate services for the changes to take effect. On most systems this can be done by running service nginx restart or /etc/init.d/nginx restart as root. For php-fpm the service name is php5-fpm.

The post FIX: WordPress on nginx (ERR_INCOMPLETE_CHUNKED_ENCODING) appeared first on Cube Websites.