developer resources
Codebales holds an ever growing number of solutions to problems that we have experienced in our day to day code writing
Selected filter
11
results
Andrew Fletcher
•
Updating NPM packages using npm update and I'm seeing the following response
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@fortawesome%2fpro-light-svg-icons - Not found
npm ERR! 404
npm ERR! 404 '@fortawesome/pro-light-svg-icons@^5.11.2' is not in this registry.
npm ERR! 404
@fortawesome:registry=https://npm.fontawesome.com/
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run...
Andrew Fletcher
•
After cloning a site, next you will want to import the config file. Which...
Andrew Fletcher
•
Currently, I have a situation where I have two repositories. The first is...
Andrew Fletcher
•
When attempting to do a git push, are you getting the following...
Andrew Fletcher
•
In this woalk through I am going to use GitHub. However, the steps are...
Andrew Fletcher
•
If you are using theme_get_settings, such as:
$value = trim(theme_get_setting('my_setting'));
Then in your code editor you will also be seeing undefined function 'theme_get_setting'. This function has been deprecated for some time.
Instead, you need to use
Passing the theme.manager and theme.initialization services to theme_handler constructor as optional parameters is deprecated. These parameters are also mandatory.
$theme_handler = \Drupal::service('theme_handler');Get...
Andrew Fletcher
•
Wanting to create a new repository on GitHub, add in a few of the available...
Andrew Fletcher
•
Images
For some time, when looking for images online for your app or site I have...
Andrew Fletcher
•
iOS localization on the fly
If you have added languages to your app......
Andrew Fletcher
•
Localization is the process of showing other languages in your app and is...
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...