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
I'm receiving an issue with a previous release on Google...
Andrew Fletcher
The "keystore password was incorrect" error in keytool indicates that the...
Andrew Fletcher
How to generate a new private key and submit it to Google Play for signing your...
Andrew Fletcher
A summary of Node package commands Short cut commands npm install...
Andrew Fletcher
Issues with sign in key... When attempting to upload a APK package, I'm getting the following response Your Android App Bundle is signed with the wrong key. Ensure that your App Bundle is signed with the correct signing key and try again. Your app bundle is expected to be signed with the certificate with fingerprint: SHA1: 87:EF:1D:19:B4:A7:72:79:1E:49:26:5B:F2:28:DE:11:DA:3D:26:B6 but the certificate used to sign the app bundle that you uploaded has fingerprint: SHA1:...
Andrew Fletcher
Recently I have been investigating one of my Linux server's speed using the...
Andrew Fletcher
The migrate process saves the status of each running migration in the...
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....