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
Installing PHP on OSX and it installed PHP 8.2.x.  However, for my...
Andrew Fletcher
  JSON structure Outlining the structure of the elements common attributes:...
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
Trying to have a chat recently, and Microsoft Teams would not open on MAC OS.  Sometimes it would open without issue.  But today, no play. The email comes through with no issue.  Opens in Safari with no issue.  But the link to open in Microsoft Teams, goes nowhere. Below are the progressive steps that I took to resolve this issue (note that this could take multiple solutions - let's see):   Solution 1: delete cache How to delete the cache of Microsoft Teams on...
Andrew Fletcher
This code is from Drupal 9 back-end for a React front-end via REST API. Working...
Andrew Fletcher
How do you generate a .pem file from an existing .ppk key? Is putty on your...
Andrew Fletcher
The cache system in Drupal 9 delivers the API with the elements required for...
Andrew Fletcher
Installing Varnish to increase the speed of the page load. Install varnish using...
Andrew Fletcher
Clear DNS Cache The DNS (Domain Name Service) cache on your Mac helps browsers locate and connect to web addresses quickly. If your browser Safari or Chrome still fails to load websites, this can be the result of an obsolete DNS cache may be causing the issue. In this instance you want to focus clearing the cache.  Using Terminal or iTerm2 enter the following command: sudo killall -HUP mDNSResponder