Tags: ChurchCRM/CRM
Tags
New Locale - Telugu (#7194) # Description & Issue number it closes <!-- Please include a summary of the changes and the related issue. Please also include relevant motivation and context. --> - New Locale - Telugu - Download from POEditor (17% complete) - Ensure all plugins work (most are disabled for this locale) ## Screenshots (if appropriate) <!-- Before and after -->    ## How to test the changes? ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # How Has This Been Tested? <!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration --> # Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules
Bug fix: Number of Groups in Group list doesn't match with Groups cou… ( #7168) …nt in Dashboard # Description & Issue number it closes #3985 ## Screenshots (if appropriate) ### Before #### Dashboard says 17 groups. <img width="1188" alt="Screenshot 2024-09-27 at 4 20 05 PM" src="https://github.com/user-attachments/assets/523e8989-29ef-4711-896a-6cd9a69f889c"> #### Group list says 23 entries. <img width="1404" alt="Screenshot 2024-09-27 at 4 20 18 PM" src="https://github.com/user-attachments/assets/ce74a7b7-a19e-4fee-997d-c836ba7b111d"> ### After <img width="990" alt="Screenshot 2024-09-27 at 10 59 50 AM" src="https://github.com/user-attachments/assets/8f16ce69-a348-4b40-8cf6-06aee048ff2a"> <img width="1174" alt="Screenshot 2024-09-27 at 11 00 02 AM" src="https://github.com/user-attachments/assets/d62ef9e3-b8ab-4f73-ba8a-1b94a7e23fae"> <img width="1164" alt="Screenshot 2024-09-27 at 11 00 13 AM" src="https://github.com/user-attachments/assets/85b4515d-02c9-4839-b403-1ecaf6d66a54"> ## How to test the changes? Number of groups in the `Dashboard` and `Group List` should be the same like the above screenshots. ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update # How Has This Been Tested? Docker # Checklist: - [X] My code follows the style guidelines of this project - [X] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [X] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published in downstream modules
Bump ckeditor4 from 4.24.0 to 4.25.0 (#7117) Bumps [ckeditor4](https://github.com/ckeditor/ckeditor4-releases) from 4.24.0 to 4.25.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ckeditor/ckeditor4-releases/blob/master/CHANGES.md">ckeditor4's changelog</a>.</em></p> <blockquote> <p>⚠️ ️️ <strong>CKEditor 4 (the open source edition) is no longer maintained.</strong>⚠️ </p> <p>If you would like to keep access to future CKEditor 4 security patches, check the <a href="https://ckeditor.com/ckeditor-4-support/">Extended Support Model</a>, which guarantees <strong>security updates and critical bug fixes until December 2026</strong>. Alternatively, <a href="https://ckeditor.com/docs/ckeditor5/latest/updating/ckeditor4/migration-from-ckeditor-4.html">upgrade to CKEditor 5</a>.</p> <h2>CKEditor 4.25.0-lts</h2> <p>⚠️ ️️ Please note that this release is a part of <a href="https://ckeditor.com/ckeditor-4-support/">CKEditor 4 Extended Support Model</a>, only available to customers who decided to acquire the LTS (Long Term Support) version of the editor. <strong>All editor versions below 4.25.0-lts can no longer be considered as secure!</strong>⚠️ </p> <p><strong>Security Updates:</strong></p> <ul> <li> <p>Fixed reflected cross-site scripting (XSS) vulnerability in <a href="https://ckeditor.com/cke4/addon/codesnippetgeshi">Code Snippet GeSHi</a> plugin reported by <a href="https://github.com/Hebing123">Jiasheng He</a> from Qihoo 360.</p> <p>Issue summary: The vulnerability allowed a reflected XSS attack by exploiting a flaw in the <a href="https://github.com/GeSHi/geshi-1.0">GeSHi syntax highlighter library</a> hosted by the victim. The GeSHi library was included as a vendor dependency in CKEditor 4 source files. In a specific scenario, an attacker could craft a malicious script that could be executed by sending a request to the GeSHi library hosted on a PHP web server. See <a href="https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-7r32-vfj5-c2jv">GHA</a> for more details.</p> </li> <li> <p>Fixed low-risk cross-site scripting (XSS) vulnerability linked to potential domain takeover</p> <p>Issue summery: A theoretical vulnerability has been identified in CKEditor 4.22 (and above). In a highly unlikely scenario where an attacker gains control over the <a href="https://cke4.ckeditor.com">https://cke4.ckeditor.com</a> domain, they could potentially execute an attack on CKEditor 4 instances. Although the vulnerability is purely hypothetical, we have addressed it in CKEditor 4.25.0-lts to ensure compliance with security best practices. See <a href="https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-6v96-m24v-f58j">GHA</a> for more details.</p> </li> </ul> <p>You can read more details in the relevant security advisories. <a href="https://github.com/ckeditor/ckeditor4-releases/blob/master/security@cksource.com">Contact us</a> if you have more questions.</p> <p><strong>An upgrade is highly recommended!</strong></p> <p>Updated dependencies:</p> <ul> <li> <p><strong>CodeMirror</strong> (used only in the <a href="https://ckeditor.com/docs/ckeditor4/latest/features/toolbar.html#toolbar-configurator">Toolbar Configurator</a> in samples) has been updated to v5.65.17 for improved stability and performance.</p> </li> <li> <p><strong>Highlight.js</strong> (used by the <a href="https://ckeditor.com/cke4/addon/codesnippet">Code Snippet</a> plugin) has been updated to v11.9.0, introducing <strong>two breaking changes</strong>:</p> <ul> <li>dropped support for Internet Explorer,</li> <li>updated list of the supported themes – some of the themes are no longer officially supported, others may have their names changed (e.g. <code>monokai_sublime</code> is now <code>monokai-sublime</code>). Please verify the value of your <a href="https://ckeditor.com/docs/ckeditor4/latest/api/CKEDITOR_config.html#cfg-codeSnippet_theme"><code>config.codeSnippet_theme</code></a> configuration option and adjust theme names as needed. The list of available themes can be checked in the <code>plugins/codesnippet/lib/highlight/styles</code> directory.</li> </ul> </li> </ul> <h2>CKEditor 4.24.0-lts</h2> <p>⚠️ ️️ Please note that this release is a part of <a href="https://ckeditor.com/ckeditor-4-support/">CKEditor 4 Extended Support Model</a>, only available to customers who decided to acquire the LTS (Long Term Support) version of the editor. <strong>All editor versions below 4.24.0-lts can no longer be considered as secure!</strong>⚠️ </p> <p><strong>Security Updates:</strong></p> <ul> <li> <p>Fixed cross-site scripting (XSS) vulnerability caused by incorrect CDATA detection reported by <a href="https://cz.linkedin.com/in/michal-fryba">Michal Frýba</a>, <a href="https://www.alefnula.com/">ALEF NULA</a>.</p> <p>Issue summary: The vulnerability allowed to inject malformed HTML content bypassing Advanced Content Filtering mechanism, which could result in executing JavaScript code. See <a href="https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-fq6h-4g8v-qqvm">GHA</a> for more details.</p> </li> <li> <p>Fixed cross-site scripting (XSS) vulnerability in AJAX sample reported by Rafael Pedrero, see <a href="https://www.incibe.es/en/incibe-cert/notices/aviso/cross-site-scripting-vulnerability-cksource-ckeditor">INCIBE</a> report.</p> <p>Issue summary: The vulnerability allowed to execute JavaScript code by abusing the AJAX sample. See <a href="https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-wh5w-82f3-wrxh">GHA</a> for more details.</p> </li> <li> <p>Cross-site scripting (XSS) vulnerability in samples with enabled the preview feature reported by <a href="https://www.linkedin.com/in/marcin-wyczechowski-0a823795/">Marcin Wyczechowski</a> & <a href="https://www.linkedin.com/in/micha%C5%82-majchrowicz-mwsc/">Michał Majchrowicz</a> <a href="https://afine.com/">AFINE Team</a>.</p> <p>Issue summary: The vulnerability allowed to execute JavaScript code by abusing the misconfigured preview feature. See <a href="https://github.com/ckeditor/ckeditor4/security/advisories/GHSA-mw2c-vx6j-mg76">GHA</a> for more details.</p> </li> </ul> <p>You can read more details in the relevant security advisories. <a href="https://github.com/ckeditor/ckeditor4-releases/blob/master/security@cksource.com">Contact us</a> if you have more questions.</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/ckeditor/ckeditor4-releases/commits">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any 7171 more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/ChurchCRM/CRM/network/alerts). </details>
PreviousNext