Skip to main content
11
results
Andrew Fletcher
The error message "Attempting to re-run cron while it is already running" in Drupal typically indicates that another instance of the cron job is still running when the system tries to start a new one. Cron is a process that performs various tasks for Drupal, such as indexing content, checking for updates, and performing other scheduled tasks. Some potential causes and solutions for this issue Long-Running Cron Jobs If a cron job takes longer to complete than the interval between cron runs, it...
Andrew Fletcher
Visual Studio Code (VS Code) allows you to manage extensions using the VS Code...
Andrew Fletcher
A summary of Node package commands Short cut commands npm install...
Andrew Fletcher
Working on a decoupled React / Drupal 9 site. Aim: Adjust the output of curated...
Andrew Fletcher
How to make React calls on a Drupal 9 backend site using the search...
Andrew Fletcher
This code is from Drupal 9 back-end for a React front-end via REST API. Working through the output for recently viewed pages... the code structure: <?php namespace Drupal\custom\Plugin\GetData\paragraph; use Drupal\custom\Plugin\GetData\ContentBase; use Drupal\custom\Plugin\GetData\ParagraphTrait; use Drupal\node\Entity\Node; /** * Provides Recent view pages data. * * @GetData( * id = "recent_view_pages", * title = @Translation("Recent view pages Data"), * ) */ class...
Andrew Fletcher
phpcs issue in Visual Studio Code, I'm receiving this warning in VS...
Andrew Fletcher
Setting up a new project in Docker and VS Code. Using Terminal, go to your...
Andrew Fletcher
Step 1: Install Homebrew Homebrew is the missing package manager for macOS. As...
Andrew Fletcher
Working on a new CentOS 7 server, Node wasn't installed.  You can...
Andrew Fletcher
I started out with a simple task... install Tailwindcss.  What unfolded is something that many of us have experienced time and time again. For anyone that has completed this task before knows that through shell the command is # Using npm npm install tailwindcssHowever, before doing so I wanted to check the version of node on the server and in Plesk.  The shell command node -v was showing v7.10.1 whereas in Plesk v10.16.0.  Not great being a few versions behind....