Background: Substance use is a high-impact biopsychosocial problem in Chile, where 21% of adults have experienced a severe alcohol use episode. In the past year, the prevalence rates were 12.5% for marijuana, 0.8% for cocaine, and 0.4% for cocaine base paste. Cannabis prevalence in Chile is higher than the global (4.2%) and South American (3.58%) averages. Cocaine prevalence in Chile is lower than in South America (1.62%) but higher than the global average (0.42%). No international reports are available for cocaine base paste. Mental health and substance use programs in Chilean primary care involve psychologists and social workers. Solution-focused brief interventions (SFBIs) are based on solution-focused brief therapy, a strengths-based and person-centered approach in which practitioners adopt a stance of “not being the expert,” respecting clients’ needs and perspectives. Objective: This #Study aims to determine whether the SFBI implemented by psychosocial teams (psychologists and social workers) for individuals with alcohol and other drug use in primary health care centers leads to better outcomes than usual care. Methods: We will conduct a randomized controlled clinical trial (ClinicalTrials.gov registration pending) comparing a 3-session SFBI (experimental group) with a single session of brief counselling as usual care (control group) in primary care. Interventions will be delivered in person by a psychologist or social worker. A total of 320 participants are expected to be recruited during preventive routine checkups using the Alcohol, Smoking, and Substance Involvement Screening Test. Participants reporting intermediate- to high-risk substance use on this screening tool will be randomly assigned to each group. #Research assistants will administer instruments at baseline and at 3-, 6-, and 9-month follow-ups and will be blinded to the assigned treatments. The primary outcome assessed will be substance use patterns, while secondary outcomes include background information, depressive symptoms, anxiety symptoms, and motivation for treatment. Statistical analyses, including t tests, ANOVA, and Fisher exact tests will be conducted depending on variable type and normality. A qualitative component to assess acceptability and pertinence will include focus groups with participants and practitioners, followed by a content analysis. Results: Funding for this #Study started in April 2024. As of the submission date of this #Protocol, 55 practitioners from 9 primary health care centers have been trained in SFBIs. Recruitment began in February 2025, with 73 participants enrolled and 23 who dropped out. Recruitment will continue until December 2026. No analyses have been conducted to date. Findings are expected to be published during the second half of 2028. Conclusions: This #Study strengthens primary care by integrating targeted psychosocial interventions for substance use into existing programs, thereby enhancing real-world applicability. If effective, the intervention could be adopted into routine care and inform public policy on mental health and substance use. Trial Registration:

LE QUOTIDIEN : Pourquoi étiez-vous en grève ce lundi 10 novembre ?DR SÉBASTIEN THIRIAT : Parce qu’il y a une mise en danger de l’ensemble de la radiologie française ! Cela touche aussi bien les tarifs des actes d’imagerie dans le privé que dans...

UCL Discovery is UCL's open access repository, showcasing and providing access to UCL research outputs from all UCL disciplines.

In a comprehensive guide, Diana Czuchry from Evolving Web breaks down how to audit and manage web components for consistent, scalable, and accessible websites. From eliminating redundant patterns to documenting purpose and usage, the article outlines...

to paper

to paper

Did you follow these instructions? (It doesn’t seem like it?) Multisite configuration with Docker > > hooks: > after_postgres: > - exec: sudo -u postgres createdb b_discourse || exit 0 > - exec: > stdin: | > grant all privileges on database b_discourse to discourse; > cmd: sudo -u postgres psql b_discourse > raise_on_fail: false > > - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "alter schema public owner to discourse;"' > - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists hstore;"' > - exec: /bin/bash -c 'sudo -u postgres psql b_discourse <<< "create extension if not exists pg_trgm;"' > ....... > Stew_Pid: > Will simply changing owner to discourse fix it? It’s a pretty good bet, but make sure that you’ve got stuff like in the multisite install topic. If your sites are working now then I too would encourage you to do a clean multisite install and backup/restore the databases over. You can copy all the other stuff as described in Move a Discourse site to another VPS with rsync

v3.5.2 → v3.5.2 v3.6.0.beta2 → v3.6.0.beta2 This thread got me to this point: Upgrade failed. Database stopped. (multisite install) I now have database access issues: 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse LOG: provided user name (postgres) and authenticated user name (discourse) do not match 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse FATAL: Peer authentication failed for user "postgres" 2025-11-02 17:13:51.212 UTC [1975] postgre...

v3.5.2 → v3.5.2 v3.6.0.beta2 → v3.6.0.beta2 This thread got me to this point: Upgrade failed. Database stopped. (multisite install) I now have database access issues: 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse LOG: provided user name (postgres) and authenticated user name (discourse) do not match 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse FATAL: Peer authentication failed for user "postgres" 2025-11-02 17:13:51.212 UTC [1975] postgre...

v3.5.2 → v3.5.2 v3.6.0.beta2 → v3.6.0.beta2 This thread got me to this point: Upgrade failed. Database stopped. (multisite install) I now have database access issues: 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse LOG: provided user name (postgres) and authenticated user name (discourse) do not match 2025-11-02 17:13:51.212 UTC [1975] postgres@c_discourse FATAL: Peer authentication failed for user "postgres" 2025-11-02 17:13:51.212 UTC [1975] postgre...

Origin