Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow fetching seen/read messages via scheduler #3931

Merged

Conversation

ohader
Copy link
Contributor

@ohader ohader commented Apr 1, 2024

Usually the schedule:run command invokes freescout:fetch-emails, but only fetches unseen (not read by anybody else, yet). This change allows to configure this behavior and to fetch seen/read messages.

The new option app.fetch_unseen can be configured via .env:

APP_FETCH_UNSEEN=0

Example of a schedule:run execution, using APP_FETCH_UNSEEN=0:

$ php artisan schedule:run
Running scheduled command: '/usr/bin/php8.2' 'artisan' freescout:fetch-monitor > '/dev/null' 2>&1
Running scheduled command: '/usr/bin/php8.2' 'artisan' freescout:check-conv-viewers > '/dev/null' 2>&1
Running scheduled command: '/usr/bin/php8.2' 'artisan' freescout:fetch-emails --identifier=[redacted] --unseen=0 > '/home/[redacted]/storage/logs/fetch-emails.log' 2>&1

Usually the `schedule:run` command invokes `freescout:fetch-emails`,
but only fetches unseen (not read by anybody else, yet). This change
allows to configure this behavior and to fetch seen/read messages.

The new option `app.fetch_unseen` can be configured via `.env`:

```
APP_FETCH_UNSEEN=0
```
@freescout-helpdesk freescout-helpdesk merged commit 356b211 into freescout-help-desk:master Apr 2, 2024
@mattly6
Copy link

mattly6 commented Aug 21, 2024

Hi, is there a way to download both read and unread messages with this change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants