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
This code is from Drupal 9 back-end for a React front-end via REST API. Working...
Andrew Fletcher
How do you exclude the current node from a list view? In some situations, for...
Andrew Fletcher
I'm writing these steps primarily for myself as a reference.  However, if...
Andrew Fletcher
I had an issue where logging in from the app disconnected.  The error that...
Andrew Fletcher
Updating Realm and RealmSwift from 5.5.x to 10.0.0 brought in the following error  RealmSwift 10.1: framework not found realm-syncThe greatest clue I came across to solving this issue was on the Realm GitHub issues page for realm-sync error.  However, updating Cocopods wasn't the only step required to correct this issue.  The steps I took were: Update Cocopods to v1.10.0 using sudo gem install cocoapods Deintegrate all of your pods pod deintegrate Install the pods from the...
Andrew Fletcher
Overview To update ejabberd you need to remove it, then re-install with the...
Andrew Fletcher
The starting point is to read through and follow the notes outlined on the...
Andrew Fletcher
To add Erlang repository that also includes the public key for verifying signed...
Andrew Fletcher
Adding a pem file to secure ejabbered on the server for chat connection. Getting...
Andrew Fletcher
To access the ejabberd log files, I found them located at the following directory cd /usr/local/var/log/ejabberdThe following files exist: crash.log ejabberd.log error.log