How to prevent an ‘Attempt to create a field field_description that does not exist on entity type group’?

When cron runs I see a notice in the dblog. Drupal\Core\Field\FieldException: Attempt to create a field field_description that does not exist on entity type group. in Drupal\field\Entity\FieldConfig->getFieldStorageDefinition() (line 312 of /web/core/modules/field/src/Entity/FieldConfig.php). This appears to be similar to ‘Attempt to create a field body that does not exist on entity type node‘ Some time ago during…

Details

Changing Nginx root to two different top level directories with the same permissions: one gives 403 while the other doesn’t

From reading other StackExchange posts, I figured that the reason I couldn’t use a directory in my home folder as the nginx root had something to do with permissions, possibly from parent directories. So, I decided to check the top level directories(ie, the ones under /) Both /usr/ and /home/ contain identical index.html’s and indentical…

Details

Modify variable into log_format

I have simple config: http { log_format main ‘”rmethod”:”$request_method” “uri”:”$uri” “args”:”$args”; access_log /tmp/nginx_access.log main; … } Problem is that args contains sensitive information. Can I hide some query parameters? For example: $args value is cmd=list&username=qwe&ext=625&sensitive_info=sfsfsd&cred=Black0ps5762 After using regex ^(.*)((?:sensitive_info=.*)&)(.*)$ will form a new variable by capture groups: args = $1$3. Is it possible?

Details