JimBob on Freenodemoin
nonom on Freenode:)
brieweb on Freenodewhere does the mydata folder go?
brieweb on FreenodeDo I put it in core/modules?
dougquaid on FreenodeI'm on drupal 8.9 if that matters
hesco1 on FreenodeTesting layout builder on a drupal 8.9.1 installation. When I try to 'Add section' or 'Add block' I am unable to scroll through the options. Have tried this in both firefox and chrome. Only option seems to reduce the font (Cntrl+Shift+-), to a point where I can barely if at all read the options.
hesco1 on Freenodeany ideas how to resolve this, please?
nemo on Freenodewhat I'm mostly looking for is some measure of sanity
nemo on FreenodeI have the cache control set to 15 minutes, and I've waited half an hour and this page has not changed ☹
nemo on Freenode(I figured 29 minutes was worst case regardless of how it was handled)
nemo on FreenodeCache-Control=900, public
nemo on FreenodeWHAT
nemo on Freenode(finally checked cache_page)
nemo on Freenodehowwwwww
nemo on FreenodeCACHE_TEMPORARY for expire, created on the page is now at 2 hours in the past
nemo on Freenodewhy the heck has it not been invalidated
nemo on Freenodeok. trivial solution is no_cache: 'TRUE' in the routing
nemo on Freenodebut probably need to make it smarter than that at some point
hesco1 on Freenodeusing a subtheme of bootstrap, using drush to rebuild-cache at every change, bootstrap_layouts enabled, using display_suite to build a layout, at /layout_builder/configure/section/defaults/node.landing_page.default/1, I have customised the 'Additional attributes' setting to read 'id|my-custom-name', yet I still do not see the custom css selector show up when I use inspect element. Any thoughts on what might
hesco1 on Freenodebe missing here, please?
adamant1[m] on FreenodeHi, I'm having a problem on a server that hosts a lot of drupal / civicrm websites, where for one of the sites, drupal cron keeps running, eating 100% cpu, and then an other process of the same spins up after a while, repeatedly, up to where it gets around 10 or more of them, eats up all 16 CPU threads at 100%, slows the server to a halt, used up 26G of ram and all my swap, almost took down our production server.
adamant1[m] on Freenodeit is a drush process
adamant1[m] on FreenodeWe use drush for drupal cron from a cron job in /etc/cron.d , I have disabled the site from the cron script in /etc/cron.d/ ... I have checked settings.local.php and $config['automated_cron.settings']['interval'] = 0; is already set. I logged in as a drupal admin and checked /admin/config/system/cron and it is also set to never. Where are these runaway drush cron processes coming from, what do I do???
adamant1[m] on FreenodeI can't just stay up all night killing drush processes on a national holiday while my coworkers are sleeping
adamant1[m] on FreenodeWhoops sorry, wrong window.