PHP good first issues

AI Summary: This is a placeholder issue designed for new contributors. It's marked as a 'Good First Issue' and requires a single, concrete change to be described and implemented, with clear acceptance criteria and contribution steps provided.

AI Summary: Users are reporting that tiles are not loading or only loading partially across multiple hosting providers. The errors observed include `net::ERR_HTTP2_PROTOCOL_ERROR` and `500 (Internal Server Error)` for failed tiles. The issue is occurring on version 1.0.2, and the reporter is curious if it persists in v2.

AI Summary: This issue aims to standardize the terminology used for people interacting with a GatherPress site. It proposes specific definitions for terms like 'viewer', 'visitor', 'attendee', 'guest', 'member', and 'reader' to ensure consistency and clarity in both code and user-facing copy. The goal is to eliminate ambiguity and refine the language used to describe different user roles and actions.

AI Summary: This issue requests the addition of LibreSign's Digital Public Good (DPG) recognition to the project's README and App Store description. The goal is to inform users and potential contributors about this official listing, linking to the DPG registry entry.

AI Summary: The website is missing rel=canonical tags, which negatively impacts SEO by allowing search engines to index duplicate pages with different URL parameters. The proposed solution is to add these tags to the header, leveraging the existing logic for generating clean URLs.

AI Summary: Google is not displaying the homepage's meta description because it is too long (224 characters) and formatted as keyword lists, leading Google to generate its own snippet. The issue proposes shortening the description to under 155 characters and rephrasing it into a readable sentence, also addressing the `<title>` tag.

AI Summary: This issue proposes moving the course lock/unlock functionality from the course listing view to the individual course detail view. The goal is to allow users to manage course locking within the context of a specific course, rather than from a general list.

AI Summary: The `npm test` command in the presence-api project does not correctly configure the testing environment for multisite functionality. This results in a significant portion of the test suite (95 tests) being silently skipped, leading to a false sense of security for developers working on multisite-specific features. The issue proposes adding a new npm script to explicitly run tests with multisite enabled.

AI Summary: End-to-end tests are failing due to frequent calls to wordpress.org for WP-CLI commands. This happens because the test environment is configured to use the latest WordPress core without caching, causing timeouts on slow network responses. The issue is exacerbated by the lack of retries in the Playwright configuration, leading to job failures even for unrelated code changes.

AI Summary: This is a placeholder issue designed for new contributors to make a simple, concrete change. The specific task is not yet defined, but it's intended to be straightforward and focused, with clear acceptance criteria and contribution steps. The goal is to guide beginners through the process of contributing to the project.

AI Summary: This issue identifies a bug in the network site-status filtering logic where only one of the three filters is effectively applied. The other two filters are unreachable because they rely on the output of the first filter, which is processed later in the request lifecycle. The proposed solution involves consolidating the filtering logic to the single effective filter and removing redundant checks.

AI Summary: This issue proposes adding the current week's identifier to the sticky header of a calendar or scheduling interface. The goal is to provide users with continuous context about the week they are viewing as they scroll through days. The exact implementation for integrating the week into the fixed header needs to be determined.

AI Summary: This issue proposes replacing a jarring red alert icon indicating recent updates with a more informative 'Last Updated' timestamp. The goal is to provide users with precise update information without causing alarm or confusion, similar to how timestamps are displayed in other parts of the application. The primary challenge is determining the optimal placement for this new timestamp within the Event Detail interface.

AI Summary: This issue reports a bug where gradeables without a due date are incorrectly displaying a due date in notifications and emails. The expected behavior is that these notifications should not include any date information when no due date is set for the gradeable.

AI Summary: The Nextcloud News app incorrectly displays only the last author listed in an Atom 1.0 feed entry. It should either show all authors or, at a minimum, the first author to accurately reflect the feed's content.

AI Summary: The current Docker upgrade process via `./namingo update` only refreshes and restarts images, not a full Namingo Registry version upgrade. A complete upgrade requires fetching new release files, running migrations, pulling and reconciling new Docker images, and performing health checks.

AI Summary: This issue proposes automating the generation of the request signature screenshot by adding a script to `package.json` that utilizes Playwright. The script will log in, navigate to the Request Signatures page, expand the settings, and capture a screenshot of the upload interface before any document is uploaded, replacing the existing image file.

AI Summary: The user wants a clearer visual indicator, specifically bolding, for the currently selected duration (Day, Week, Month) on the calendar control. This change aims to improve usability by making it immediately obvious which view the user is currently in without needing to click or hover.

AI Summary: When a search in the 'My Materials' section yields no results, the headers for the search results are still displayed. The user suggests hiding these headers or displaying a 'no records found' message instead for a cleaner user experience. This is a visual presentation issue related to empty search states.

AI Summary: This issue proposes visually highlighting the current day within the 'Week at a Glance' view. The suggested approach is to use a different font color and bold text to make today's day easily identifiable while scrolling.

AI Summary: The recent addition of links from Rainbow Grades back to Submitty gradeables has resulted in duplicate link icons appearing in both instructor and student views. The expected behavior is for only a single link icon to be displayed.

AI Summary: The current error message for prerequisite gradeables incorrectly implies that a student must achieve an exact score, rather than a minimum score. The issue requests a clarification in the message to accurately reflect that a score of '6 or more' is required, not just '6 points'.

AI Summary: The "Dates" panel on the "Edit Gradeable" page incorrectly prevents instructors from setting a "grades released" date when the "due date" is set to "no". This is problematic for scenarios like scanned PDF submissions where a due date is irrelevant, but instructors still want to control when grades are released.

AI Summary: An end-to-end test for the 'Active Posts' widget is experiencing flakiness. The test intermittently fails because the focus retention logic incorrectly identifies a post link as 'inactive' instead of simply unfocused, leading to the element being removed from the re-rendered list.

AI Summary: The release zip for the presence-api project incorrectly includes `codecov.yml` and a Jest test file. This is because the `.distignore` file, intended to exclude these files from the distribution, is not correctly configured to recognize them. The fix involves updating `.distignore` to properly exclude these unnecessary files.

AI Summary: This issue proposes to expand the default list of supported languages for the Content Translation feature. Currently, the list is small and hardcoded, though extensible via a filter. The core question is whether the existing list is sufficient or if more languages should be included by default.

AI Summary: This issue proposes integrating the Content Translation experiment with the existing WordPress Guidelines/Knowledge system. Currently, Content Translation does not leverage site-wide or block-specific guidelines, which could be beneficial for providing translation glossaries and other copy-related instructions to the LLM. The solution involves enhancing Content Translation to declare support for guideline categories like Site, Copy, and Additional.

AI Summary: This issue proposes updating LibreSign to use JSignPdf 3.x, which involves migrating to a new version of the `jsignpdf-php` wrapper. The update requires changes to how JSignPdf is installed, its package structure, and a thorough review of existing signing options and tests to ensure compatibility with the new JSignPdf version.

AI Summary: This issue requires updating a PHP wrapper to support JSignPdf version 3.x, as the current wrapper was built for version 2.x. The update involves comparing CLI commands and outputs between versions, verifying and updating parsed outputs and version detection, ensuring safe escaping of shell arguments, and adding/updating unit and integration tests.