Maybe that’s a silly question but I was wondering what would need to be the configuration of a VPS to be able to edit some videos … | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1843857&goto=newpost
Tag: configuration
forms – How to create a new parent section on the Configuration page?
When one navigates to Manage » Configuration, the page is divded into sections which (in the “Seven” theme at least) shows up in individual boxes. These sections have headings like “People”, “Content authoring”, “Development”, etc.
I am able to create a settings form and place this inside any of the existing sections on the configuration page by associating it with the parent
key in hello_world.links.menu.yml
.
Example:
hello_world.greeting_form:
title: 'Salutation settings'
description: 'Configure the salutation message.'
route_name: hello_world.greeting_form
parent: system.admin_config_development
This places a link to the settings form for the “Hello World” module in the “Development” section.
However, neihter this, nor any other of the pre-existing sections, are suitable for my use case.
I want to create a new section named “Experimental”, place along the others on the “Configuration” page. And make this the parent of my menu link. How do I do that?
configuration – apt – reinstall with all default config files
Your privacy
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
8 – How do I hide security update notifications for a user with the “Administer site configuration” permission?
Drupal Answers is a question and answer site for Drupal developers and administrators. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
Asked
Viewed
24 times
How do I hide security update notifications for a user with the Administer site configuration permission?
Akhil Alosious is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
3
default

8 – Import single view configuration fail – layout_builder__layout will not exists after import
I have Drupal 8.9.13 and I want to export/import single views configuration to other Drupal 8.9.13. I can select single view to export, but when I import it I get the next error:
The configuration core.entity_view_display.node.page.default depends on the configuration of field.field.node.page.layout_builder__layout that will not exists after import.
This is one of the views I want to import. The problem happens with all views:
uuid: xxxxx
langcode: es
status: true
dependencies:
config:
- field.storage.user.field_documento
- user.role.administrator
module:
- mycustommodule
- file
- rest
- serialization
- user
id: custom_user_files
label: 'User files'
module: views
description: 'REST Export user files'
tag: ''
base_table: file_managed
base_field: fid
display:
default:
display_plugin: default
id: default
display_title: Master
position: 0
display_options:
access:
type: role
options:
role:
administrator: administrator
cache:
type: tag
options: { }
query:
type: views_query
options:
disable_sql_rewrite: false
distinct: false
replica: false
query_comment: ''
query_tags: { }
exposed_form:
type: basic
options:
submit_button: Apply
reset_button: false
reset_button_label: Reset
exposed_sorts_label: 'Sort by'
expose_sort_order: true
sort_asc_label: Asc
sort_desc_label: Desc
pager:
type: mini
options:
items_per_page: 10
offset: 0
id: 0
total_pages: null
expose:
items_per_page: false
items_per_page_label: 'Items per page'
items_per_page_options: '5, 10, 25, 50'
items_per_page_options_all: false
items_per_page_options_all_label: '- All -'
offset: false
offset_label: Offset
tags:
previous: ‹‹
next: ››
style:
type: serializer
row:
type: fields
options:
inline: { }
separator: ''
hide_empty: false
default_field_elements: true
fields:
filename:
id: filename
table: file_managed
field: filename
relationship: none
group_type: group
admin_label: ''
label: ''
exclude: false
alter:
alter_text: false
text: ''
make_link: false
path: ''
absolute: false
external: false
replace_spaces: false
path_case: none
trim_whitespace: false
alt: ''
rel: ''
link_class: ''
prefix: ''
suffix: ''
target: ''
nl2br: false
max_length: 0
word_boundary: false
ellipsis: false
more_link: false
more_link_text: ''
more_link_path: ''
strip_tags: false
trim: false
preserve_tags: ''
html: false
element_type: ''
element_class: ''
element_label_type: ''
element_label_class: ''
element_label_colon: false
element_wrapper_type: ''
element_wrapper_class: ''
element_default_classes: true
empty: ''
hide_empty: false
empty_zero: false
hide_alter_empty: true
click_sort_column: value
type: file_filemime
settings:
link_to_entity: 0
group_column: value
group_columns: { }
group_rows: true
delta_limit: 0
delta_offset: 0
delta_reversed: false
delta_first_last: false
multi_type: separator
separator: ', '
field_api_classes: false
entity_type: file
entity_field: filename
plugin_id: field
field_documento:
id: field_documento
table: user__field_documento
field: field_documento
relationship: reverse_field_documento_user
group_type: group
admin_label: ''
label: ''
exclude: false
alter:
alter_text: false
text: ''
make_link: false
path: ''
absolute: false
external: false
replace_spaces: false
path_case: none
trim_whitespace: false
alt: ''
rel: ''
link_class: ''
prefix: ''
suffix: ''
target: ''
nl2br: false
max_length: 0
word_boundary: true
ellipsis: true
more_link: false
more_link_text: ''
more_link_path: ''
strip_tags: false
trim: false
preserve_tags: ''
html: false
element_type: ''
element_class: ''
element_label_type: ''
element_label_class: ''
element_label_colon: false
element_wrapper_type: ''
element_wrapper_class: ''
element_default_classes: true
empty: ''
hide_empty: false
empty_zero: false
hide_alter_empty: true
click_sort_column: target_id
type: astec_fichero_base64
settings: { }
group_column: ''
group_columns: { }
group_rows: true
delta_limit: 0
delta_offset: 0
delta_reversed: false
delta_first_last: false
multi_type: separator
separator: ', '
field_api_classes: false
plugin_id: field
fid:
id: fid
table: file_managed
field: fid
relationship: none
group_type: group
admin_label: ''
label: ''
exclude: false
alter:
alter_text: false
text: ''
make_link: false
path: ''
absolute: false
external: false
replace_spaces: false
path_case: none
trim_whitespace: false
alt: ''
rel: ''
link_class: ''
prefix: ''
suffix: ''
target: ''
nl2br: false
max_length: 0
word_boundary: true
ellipsis: true
more_link: false
more_link_text: ''
more_link_path: ''
strip_tags: false
trim: false
preserve_tags: ''
html: false
element_type: ''
element_class: ''
element_label_type: ''
element_label_class: ''
element_label_colon: false
element_wrapper_type: ''
element_wrapper_class: ''
element_default_classes: true
empty: ''
hide_empty: false
empty_zero: false
hide_alter_empty: true
click_sort_column: value
type: number_integer
settings:
thousand_separator: ''
prefix_suffix: false
group_column: value
group_columns: { }
group_rows: true
delta_limit: 0
delta_offset: 0
delta_reversed: false
delta_first_last: false
multi_type: separator
separator: ', '
field_api_classes: false
entity_type: file
entity_field: fid
plugin_id: field
filters: { }
sorts: { }
header: { }
footer: { }
empty: { }
relationships:
reverse_field_documento_user:
id: reverse_field_documento_user
table: file_managed
field: reverse_field_documento_user
relationship: none
group_type: group
admin_label: field_documento
required: true
entity_type: file
plugin_id: entity_reverse
arguments:
uuid:
id: uuid
table: users
field: uuid
relationship: reverse_field_documento_user
group_type: group
admin_label: ''
default_action: default
exception:
value: all
title_enable: false
title: All
title_enable: false
title: ''
default_argument_type: query_parameter
default_argument_options:
query_param: uuid
fallback: ''
multiple: and
default_argument_skip_url: false
summary_options:
base_path: ''
count: true
items_per_page: 25
override: false
summary:
sort_order: asc
number_of_records: 0
format: default_summary
specify_validation: false
validate:
type: none
fail: 'not found'
validate_options: { }
glossary: false
limit: 0
case: none
path_case: none
transform_dash: false
break_phrase: false
entity_type: user
entity_field: uuid
plugin_id: string
display_extenders: { }
cache_metadata:
max-age: -1
contexts:
- 'languages:language_content'
- 'languages:language_interface'
- request_format
- url
- url.query_args
- user.roles
tags:
- 'config:field.storage.user.field_documento'
rest_export_1:
display_plugin: rest_export
id: rest_export_1
display_title: 'REST export'
position: 1
display_options:
display_extenders: { }
path: custom-user-files
pager:
type: none
options:
offset: 0
style:
type: serializer
options:
formats:
json: json
row:
type: data_field
options:
field_options:
filename:
alias: ''
raw_output: true
field_documento:
alias: ''
raw_output: false
fid:
alias: ''
raw_output: true
uuid:
alias: ''
raw_output: true
auth:
- basic_auth
- key_auth
- cookie
cache_metadata:
max-age: -1
contexts:
- 'languages:language_content'
- 'languages:language_interface'
- request_format
- url
- user.roles
tags:
- 'config:field.storage.user.field_documento'
I don’t use layout builder templates. field_documento is a field in the user profile. How could I solve this issue?.
Android Studio IDE: I want to prevent the last executed Gradle task from being default run configuration
I have a custom gradle task that clean, build and copy the output apk to a certain location to release the apk to my customers.
However, every time I run the custom gradle task, the run configuration of Android Studio IDE is changed to that gradle task.
For example,
This is changed as the following picture after running the task.
(In this picture I use gradle clean for example)
Thus, if I forgot to change back the configuration to default app module and ‘run (Shift + F10 in Windows)’, the task is running again unexpectedly and it struck me.
After an hour of googling, I couldn’t found a solution for this. Is there a way to prevent this behavior?
SQl Server log shipping monitor security configuration and update problems
I’m setting up log shipping between instances A and B with the instance C as a monitor. The shipping itself is working fine but I’m somehow unable to make the monitoring work. The log shipping status on C is not up to date – the reports show that no backups and restores are performed. The respective reports on A and B are perfectly up to date, showing that everything is OK. The problem is pretty much obviously in the monitor connections configuration/permissions.
SQL Agents on A and B run as NT ServiceSQLSERVERAGENT.
The SA accounts on A, B and C are disabled.
- using impersonation with A and B machine domain accounts added to sysadmins on C – doesn’t help
- using custom SQL logins which are also sysadmins on A, B and C – doesn’t help and also keeps switching to SA login in the monitor connection window as well as in the linked server configuration on A and B
What can be the root cause? Is using SA account a requirement?
TIA
rooting – Is there a way to backup Samsung’s OneUI configuration?
I recently set up the home screen and app drawer of my Samsung Galaxy A70. The apps in my app drawer are organised into folders, some apps are hidden and some default apps are disabled. My home screen is completely empty.
I would like to switch to a new Samsung phone and automate the process of setting up the home screen and app drawer. Is there a way to backup my OneUI configuration? Can I find the OneUI configuration files (or something similar) somewhere on my phone? I am open to rooting the phone.
configuration – SQL Server Network Packet Size
During the analysis of network traffic from Citrix clients to our database server, we noticed that we had a lot of RESUBMIT
s occuring during the transport of TCP packets. The packets were being split and resubmitted.
To determine the MTU size in our network I set off the following command:
ping 10.28.212.22 -l 4096 -f
Ah yes, for those interested: The -f
parameter tells ping to not fragment the ping packet, if it would have to be split up and then resubmitted.
I then started reducing the -l
parameter value until I received the following message:
PS C:temp> ping 10.28.212.22 -l 1474 -f
Ping wird ausgefhrt fr 10.28.212.22 mit 1474 Bytes Daten:
Paket msste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket msste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket msste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Paket msste fragmentiert werden, DF-Flag ist jedoch gesetzt.
Ping-Statistik fr 10.28.212.22:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),
PS C:temp> ping 10.28.212.22 -l 1472 -f
Ping wird ausgefhrt fr 10.28.212.22 mit 1472 Bytes Daten:
Antwort von 10.28.212.22: Bytes=1472 Zeit=3ms TTL=123
Antwort von 10.28.212.22: Bytes=1472 Zeit=2ms TTL=123
Antwort von 10.28.212.22: Bytes=1472 Zeit=2ms TTL=123
Antwort von 10.28.212.22: Bytes=1472 Zeit=2ms TTL=123
Ping-Statistik fr 10.28.212.22:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 2ms, Maximum = 3ms, Mittelwert = 2ms
Because the ping
packet itself has a header of 28 bytes, the value 1472
which was successfully returned from the ping command, corresponds with our network’s MTU size of 1500 bytes.
1472 + 28 = 1500
A SQL Server instance has an advanced configuration setting named network packet size, which has a default value of 4096 (bytes). Microsoft recommends that one do not alter this parameter unless one is an experienced databases administrator or certified SQL Server professional:
This option is an advanced option and should be changed only by an experienced database administrator or certified SQL Server professional.
Reference: Configure the network packet size Server Configuration Option (Microsoft | SQL Docs)
Sadly, the document does not go into any detail and does not provide much insight as to whether or not one should alter this parameter if one is encountering lots of RESUBMIT
s of network packets. I do consider myself a seasoned DBA, but I have never had to deal with this issue. At one time in past, this value used to be 512.
I have read the previous question:
…but it doesn’t provide a definite answer.
On further reading I came across the TDS protocol which has this bit of information in the introduction:
The Tabular Data Stream (TDS) protocol is an application layer request/response protocol that facilitates interaction with a database server and provides for the following:
- Authentication and channel encryption negotiation.
- Specification of requests in SQL (including Bulk Insert).
- Invocation of a stored procedure or user-defined function, also known as a remote procedure call (RPC).
- The return of data.
- Transaction manager requests.
Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative.
Reference: 1 Introduction (Microsoft | Docs)
Well why TDS? Apparently, this is how the data is transported back to the client via the TDS protocol.
Please don’t ask which OSI layer this is on. It should be layer 7 as it is an application layer…
The TDS “packet” has a header of 8 bytes.
Based on what I have read and the situation at hand, should I …
- Set the network packet size parameter to
1500
? - Set the network packet size parameter to
1492
? (TDS packet size – TDS header) - Set the network packet size parameter to a different value?
- Leave the network packet size at
4096
?
I do understand that splitting the data into smaller chunks can have a negative impact on performance, but the network stack will be (and is) doing that anyway.
In a perfect world I would allow Jumbo packets to flow freely between clients and databases servers or between application servers and database servers, but that is not possible (as in: allowed) in our environment.
big sur – How to set or change the desktop background in configuration profile in Big Sur
Ask Different is a question and answer site for power users of Apple hardware and software. It only takes a minute to sign up.
Sign up to join this community
Anybody can ask a question
Anybody can answer
The best answers are voted up and rise to the top
