PHP good first issues

The "My Content" navbar dropdowns are not closing correctly due to a CSS hover rule that conflicts with Bootstrap's collapse toggle. This causes the dropdown to open on hover and remain open even when the toggle is clicked. The proposed fix is to remove the conflicting CSS hover rules so that the dropdown is solely controlled by the Bootstrap toggle.

This issue requests a native Burmese speaker to contribute missing translations for the Symfony framework. The contributor needs to follow specific style guidelines, work on the `6.4` branch, and update translation files for the Form, Security, and Validator components.

This issue aims to refactor the LibreSign engine contracts to better support future external signing capabilities. It involves modifying the `SignEngineFactory` to return a more generalized interface, separating certificate-dependent methods, and ensuring existing signing flows remain unaffected. The goal is to prepare the codebase for scenarios where LibreSign won't directly manage private keys.

This issue highlights an inconsistency in how different translation providers handle requests for all translations when no specific domains are provided. The `ProviderInterface::read` method lacks clear documentation on this behavior, leading to unexpected results like empty translation bags or incorrectly named files for commands like `translation:pull`. The goal is to standardize this behavior through documentation and potential provider updates.

This issue aims to migrate simple consumers away from the deprecated `ValidateHelper` class. The task involves replacing `ValidateHelper` with specific, focused validators in `FileController`, `PageController`, and `AccountController`. For `FileController` and `PageController`, `ValidateHelper` will be replaced by `SigningRequestValidator`. `AccountController` will have `ValidateHelper` removed entirely as it's unused. The goal is to maintain existing behavior while simplifying validation logic.

A user is experiencing issues with the Mattermost integration in Leantime, where no notifications are being sent to their Mattermost channel despite correct webhook configuration and successful webhook testing. They have tried manually running the scheduler without success and are seeking guidance on how to enable or troubleshoot these notifications.

This issue requests the addition of a "registration subsection" column to the "manage students" and "manage graders" pages, as it's currently missing from the column selection options. Additionally, it suggests making the "edit student" and "user id" columns always visible, as hiding them is considered an oversight.

The standalone example in the README.md file for Laminas Cache is broken because it fails to provide the necessary `ConfigProvider` for the memory adapter to the `ConfigAggregator`. This results in a `ServiceNotFoundException` when trying to retrieve the memory adapter.

PHP_CodeSniffer (phpcs) is failing to detect and flag trailing whitespace in PHP files, which is currently only caught by `git diff --check`. This issue requires investigating the `phpcs.xml` configuration to ensure the appropriate sniffs for whitespace are enabled and correctly configured to enforce trailing whitespace rules.

A bug exists where the dialog for editing material lists does not close after successfully deleting a material list. This leaves the user in an unexpected state, with the dialog still open and the underlying view not updating correctly. The issue is specifically observed in the material view, unlike the camp administration section where the functionality works as intended.

This feature request proposes updating the `google/protobuf` library from version 3.15.8 to at least 3.22.0. The current version causes deprecation errors in PHP 8.1 and 8.2 related to dynamic properties and return type compatibility. The proposed update resolves these issues and ensures compatibility with newer PHP versions.

A bug in FreshRSS version 1.30.0 causes the scroll position to be reset on every article toggle when the "Stick the article to the top when opened" setting is disabled. This regression, originating from a previous change, makes it difficult to navigate articles by constantly shifting the view. The issue is exacerbated when articles are displayed collapsed or when jumping to the next article after marking one as read.

This issue involves migrating remaining service and middleware consumers away from a deprecated `ValidateHelper` class. The task requires replacing calls to `ValidateHelper` with direct calls to newly introduced, focused validator classes, ensuring no change in validation behavior. Specific services like `RequestSignatureService`, `AccountService`, and `SignFileService` are listed with their respective validator replacements and method mappings.

This issue requires refactoring two methods in the `Duplicate_Payment_Prevention_Service` class. The methods currently return inconsistent types (array or void/null) and perform unintended side effects like modifying session data. The goal is to make these methods return boolean values indicating their check results and move side actions to the calling code.

The user is experiencing issues with OnlyOffice co-editing within Nextcloud. While users can see each other's mouse cursors, no actual text or data is synchronized between them. Additionally, printing documents results in empty PDF files.

This issue proposes the removal of a custom project content type from the icsa.uiowa.edu website. The content has already been migrated to pages, and the content type is no longer in use, making its removal a straightforward cleanup task.

This issue requests the redirection of two archived performing arts websites (theatrelobby.studio.uiowa.edu and virtualdance.studio.uiowa.edu) to new, active pages. After confirming the redirects are functioning correctly, the original sites will be removed.

The AI plugin incorrectly flags speech-only or image-only connectors as invalid because its validation logic only checks for text generation capabilities. This leads to a misleading error message for users who have correctly configured non-text connectors.

This issue proposes to store translation caches in a dedicated cache pool within the symfony-bundle. The goal is to simplify the process of invalidating and warming up translation caches, especially when translations are updated in production via cron jobs. The current implementation uses some 'hacky' workarounds that could be improved with this approach.

This issue requests the addition of a new method to the client library that allows users to list AI request logs. This new method will mirror the functionality of the Crowdin API's "List AI Request Logs" endpoint, enabling users to audit AI usage and costs through the SDK. It includes a comprehensive list of optional query filters and response fields for detailed logging.

This issue requests the addition of support for the Crowdin Application Consents API, which allows managing consent decisions for applications on crowdin.com. It involves implementing methods for listing, adding, editing, and deleting application consents, including handling specific request parameters and response models.

This issue requests the addition of new organization-level concordance search endpoints to the client library. These new endpoints will allow searching across all accessible glossaries and translation memories, expanding upon the existing project-scoped functionality. The implementation involves adding two new methods corresponding to the Crowdin API's glossary and TM concordance search endpoints.

This issue requests the addition of an informational message to the LibreSign interface when a user is asked to sign a document that does not have a visible signature field. The message should explain that a digital signature will still be applied and can be validated, addressing potential user confusion about the incomplete-looking interface. The implementation should reuse an existing helper function to detect this state and display the message using `NcNoteCard` in `Sign.vue` before the main signing action.

This issue proposes adding unit tests for the Product Categories List block in the WordPress editor. The goal is to ensure that the inspector controls, which allow users to customize the block's appearance (e.g., changing to a dropdown, adding images, or product counts), function as expected and are properly tested to prevent regressions.

The MaxDepth annotation in Symfony's Serializer is not correctly limiting recursion when dealing with relationships between multiple different classes. It appears to only stop at the specified depth if the same class is encountered repeatedly or if a circular reference is found, failing to handle diverse class hierarchies as intended.

This issue proposes adding a "sudo mode" security feature to Symfony core, which requires users to re-enter their password before performing critical actions. While some believe it's a valuable addition, others argue it's simple enough for individual developers to implement, sparking a discussion on its inclusion.

This issue requests the addition of support for left and right arrow keys in Symfony Console's QuestionHelper. The user has identified relevant code changes and a new Cursor class that might facilitate this feature, and is willing to contribute a Pull Request.

This issue describes a bug in Symfony's Dependency Injection component where the `ifString` condition within `beforeNormalization` does not execute when applied to the root node of a configuration tree. This prevents expected preprocessing logic from running, leading to incorrect configuration processing, especially when the root configuration is initially a string.

This issue reports a security vulnerability where the `schemes='https'` annotation on a Symfony route is not enforced by default. Users can bypass the HTTPS requirement for the login check endpoint by manually changing the URL from HTTPS to HTTP, even though the route is explicitly configured to require a secure connection. The workaround involves adding a specific `requires_channel: https` rule in the `security.yml` configuration.

This issue proposes a feature enhancement for Symfony Forms to better handle the `empty_data` option when dealing with PHP 7's strict typing. The current behavior can lead to `TypeError` exceptions when a form field is submitted with no data, as PHP 7 expects specific types (like strings) and `null` is passed instead. The goal is to allow Symfony to intelligently guess or provide default `empty_data` values to prevent these errors.