Skip to main content
11
results
Andrew Fletcher
Currently, I have a situation where I have two repositories.  The first is where I've held the code since the beginning.  The second has come on board recently and is the client repo.  However, rather than shut the original down, I want to keep both running with the same code.  How do I synchronise them so that they contain the same thing? Configure a remote that points to the upstream repository in Git to sync changes you make in a fork with the original repository....
Andrew Fletcher
When attempting to do a git push, are you getting the following...
Andrew Fletcher
This code is from Drupal 9 back-end for a React front-end via REST API. Working...
Andrew Fletcher
In this woalk through I am going to use GitHub.  However, the steps are...
Andrew Fletcher
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
Working in Laravel, I needed to loop through an array and know whether the current loop was odd or even row.  To do this add the expression to your Twig file: {% set direction = loop.index0 is odd ? 'left' : 'right' %}In the call above, the variable direction is set to either left or right depending on the value of the position of the loop row (loop.index0).  I then used the left or right value in a div class adding to a series of tailwind css definitions.  Such...
Andrew Fletcher
Setting up the mail configuration in October CMS is a quick progress....
Andrew Fletcher
Common commands Themes and plugins have similar command lines.  So rather...
Andrew Fletcher
At times while developing in October CMS, you will perform a step that kills the...
Andrew Fletcher
Using October CMS to migrate your site and update the tables with the plugins...
Andrew Fletcher
As a process I apply patches locally first, then using git upload the update(s) to a development site on the server.  Once the testing has been completed, the final step to apply the patch to the production site.   Using Terminal or your preferred shell program, navigate to the correct directory.  Then run this command using the name of the patch file (example.patch): patch < example.patchHowever, if you are patching Drupal core then remember to patch from the root directory...