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
21
results
Andrew Fletcher
•
A recent attempt to run an update composer (regular activity for many of us), I had a memory limit issue. This was surprising because the memory setting via Plesk is set to 2G. Yet through Terminal it was showing only 128MB. What gives??
The error I was seeing:
PHP Fatal error: Allowed memory size of 1610612736 bytes exhausted (tried to allocate 32 bytes) in phar:///usr/lib64/plesk-9.0/composer.phar/src/Composer/DependencyResolver/Pool.php on line...
Andrew Fletcher
•
Updating Drupal from 8.7.10 to 8.8.x or 8.9.x has seen a significant change...
Andrew Fletcher
•
As outlined in an earlier article composer php version, when installing the...
Andrew Fletcher
•
Running a common composer command, post an upgrade on the server to Centos 7 and...
Andrew Fletcher
•
I had an issue where logging in from the app disconnected. The error that...
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...