Module development and code questions

The request is a bit difficult to explain, I hope I can do it
I have 3 content types
- Applicant Master
- Master Data Holders (Anagrafica Titolari)
- Movements.

In Applicant Master I have an entity reference field (field_titolare) linked to the Owner Master.

I have set up Private Forums on my site, creating forum containers for each group. We have a requirement to allow authenticated non-group members to view/create/edit forum topics for groups that are not private (group visibility set to Public). By default, private forums restrict access to forum topics to group members only. I tried to implement custom visibility (like this), but still, a non-group member gets the Access Denied page.

I am working on an extremely Ajax dependent form, and am running into some issues that I cannot seem to resolve. I have a form that has it's entire submit handler handled via ajax (It can either be a single step or multi-step, either doesn't matter), however whenever I submit the form and there are validation errors, the validation message appears at the top of the form, but the form does not auto-focus to the validation message. Instead, it stays focused on the 'triggering element' (Which is the submit button), even with disable-refocus set to true.

Hi guys,

I have some issues with:

Drupal\devel_generate\Routing\DevelGenerateRoutes::$DevelGenerateManager is deprecated in Drupal\devel_generate\Routing\DevelGenerateRoutes->__construct() 

Deprecated function: Creation of dynamic property Drupal\views\ManyToOneHelper::$handler is deprecated in Drupal\views\ManyToOneHelper->__construct() 

Deprecated function: Use of "static" in callables is deprecated in Drupal\Core\Asset\AssetResolver->getCssAssets() 

Hello community,

I need a very urgent help. I was trying to deploy my code into prod server, I installed better exposed filter and Preserve Changed Timestamp modules.   In local system pushed all the related changes of composer.json and composer.lock along with some additional custom module code changes . This changes worked well in dev server , in QA server and even Stage server as well. But in production it got failed. I got below error.

We are currently experiencing garbled characters in the subject of emails sent from our Drupal site.
Garbled characters occur when we enter the email subject in Japanese characters with more than 257 bytes.

To clarify this issue, I have the following questions about email subject specifications when using contribute module "webform".

・Is there a specification for email subjects?
・Is there an upper limit on the number of characters or bytes that can be set for an email subject?

I'd appreciate it if you'd cooperate with me.