Replaced references to the-djmaze/snappymail with nextgen-networks/snappymail/
across the repository, excluding README files.
Per user request:
- README files are left untouched.
- Links containing /issues/ and /pull/ are left as they are (pointing to the-djmaze).
- All other links, including those to /releases/, /wiki/, /discussions/,
/blob/, /tree/, and bare repo URLs, are updated to point to the
new nextgen-networks repository.
- Bare web URLs include a trailing slash.
- .git and git:// URLs are updated to the new organization.
- Screenshots and raw content links are updated.
Co-authored-by: nextgen-networks <21206978+nextgen-networks@users.noreply.github.com>
Replaced bare references to the-djmaze/snappymail with nextgen-networks/snappymail/
and updated .git URLs to the new organization.
Per user request:
- README files are excluded.
- URLs with a trailing slash (e.g. issues, pull requests, releases) are
left pointing to the original repository to preserve historical context.
- Bare web URLs now include the requested trailing slash.
- Existing nextgen-networks bare URLs were updated to include the trailing slash.
Co-authored-by: nextgen-networks <21206978+nextgen-networks@users.noreply.github.com>
Replaced references to https://github.com/the-djmaze/snappymail with
https://github.com/nextgen-networks/snappymail/ across the repository,
excluding README files as requested.
The replacement handles trailing slashes carefully to ensure bare URLs
include the slash while sub-paths (like /issues/ or .git) do not result
in double slashes. Files that already used the new domain were also
updated to ensure consistent trailing slash usage.
Co-authored-by: nextgen-networks <21206978+nextgen-networks@users.noreply.github.com>
I generated this file using AI. It addresses SnappyMail's use of old API
calls to Nextcloud in attaching and saving files to the Nextcloud webDAV
endpoints. I have tested some of the basics with this and it seems to be
working as expected. It now allows saving attachments directly to
Nextcloud, attaching files from Nextcloud to an email, and saving emails as
.eml files. If you see anything that you think should change or if you see
any problems it causes, shoot me an email. Feel free to use this however
you want. I hope it can help keep SnappyMail going forward.
This commit updates the SnappyMail integration app for Nextcloud to support version 32 and the upcoming version 33.
Key changes:
- Updated `info.xml` to allow `max-version="33"`.
- Refactored `AdminSettings`, `Application`, `FetchController`, `PageController`, `Settings` (command), and `InstallStep` to use Dependency Injection instead of the deprecated `\OC::$server` service container.
- Replaced deprecated `OC_User`, `OC_Util` (e.g. `addScript`), and `OC_App` calls with their `OCP` (public API) counterparts or modern equivalents.
- Updated `SnappyMailHelper` to use `\OCP\Server::get()` for static context access where DI is not possible.
- Moved script and style registration from Controllers (using deprecated `Util::addScript`) to templates using `script()` and `style()` helpers.
- Updated `Settings` console command to extend `Symfony\Component\Console\Command\Command` instead of deprecated `OC\Core\Command\Base`.
- Addressed PHP 8.4+ compatibility by adding explicit property types and nullable types where necessary in the integration code.
Co-authored-by: nextgen-networks <21206978+nextgen-networks@users.noreply.github.com>
PHP 8.4 deprecates implicitly nullable parameter types. Parameters with a default value of `null` must now be explicitly marked as nullable (e.g., `?Type $var = null`).
This change updates the vendored `Predis` library in `plugins/cache-redis/` to comply with this requirement. It scans for function signatures like `Type $var = null` and updates them to `?Type $var = null`. This ensures compatibility with PHP 8.4 and PHP 8.5 while maintaining backward compatibility.
Affected files include `Predis` interfaces, connection classes, and command definitions.
Also updated PHPDoc `@method` annotations to reflect nullable types.
With many folders, the line-height is too large.
It is reduced to make the view more compact.
Also, the top margin for the number of unread-folder will
be adapted.
When composing a message in reply to an email, a colon is appended to
the message which is translated, in french colon should always be
prepended by an unbreakable space.
Add a space in the translation sentence to make sure the space appears
before the colon in the interface
