Skip to content

Add pre and post service buffer time, so that availability gets generated with the required "gaps" depending on the selected service#1746

Draft
hidde-s wants to merge 14 commits into
alextselegidis:developfrom
hidde-s:buffer-between-appointments
Draft

Add pre and post service buffer time, so that availability gets generated with the required "gaps" depending on the selected service#1746
hidde-s wants to merge 14 commits into
alextselegidis:developfrom
hidde-s:buffer-between-appointments

Conversation

@hidde-s

@hidde-s hidde-s commented May 31, 2025

Copy link
Copy Markdown

Hello everyone,

This is the start of a pull request for #1224. I have had it implemented in my main install for a bit now and it's working great. The buffer time is adjustable for each service and is taken into account when customers make new appointments.

I have already made a database migration file (I am not sure how any of this migration stuff works, so please check my work).

What should still be done:

  • Translations for lang('buffer-after') and lang('buffer-before')
  • When adjustments are made to appointments, the buffer time blocks aren't adjusted, neither are they deleted when the appointment is deleted. Maybe a appointment should keep references to it's buffer time blocks.
  • A warning / error should be shown when somebody in the backend moves (or creates a new) appointment where the buffer time is colliding with other unavailabilities or outside work hours.

Any help would be appreciated.

Added buffer properties and now takes them into account when calculating availability
@alextselegidis

Copy link
Copy Markdown
Owner

Hello!

Thanks for submitting this PR.

I will take a closer look and merge acordingly.

Alex Tselegidis, Easy!Appointments Creator
Need a customization? Get a free quote!

@andyg2

andyg2 commented Aug 19, 2025

Copy link
Copy Markdown

Very excited for this PR

@ZzyzXVegas ZzyzXVegas left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello hidde-s,
I made the changes to the files outlined here (manually added the buffer_before and buffer_after columns to the services table), but changes to the services form do not write to the database.
I entered values manually in the database, but they are not seen from the services page.

Any suggestions?

@hidde-s

hidde-s commented Nov 6, 2025

Copy link
Copy Markdown
Author

Weird, but now I am having the same issue when testing this pr.
It's still working in my main install but I can't find any differences. I'll look into it a bit more when I have the time.

@hidde-s

hidde-s commented Dec 21, 2025

Copy link
Copy Markdown
Author

@ZzyzXVegas I'm now no longer having this issue.

  1. I created a new database using the development branch
  2. I then changed to hidde-s:buffer-between-appointments
  3. I then ran php index.php console migrate (https://easyappointments.org/2021/02/15/introducing-cli-support/)
  4. It's working perfectly

Would you mind following these steps (you don't have to use an empty database) and checking again?

dependabot Bot and others added 4 commits February 28, 2026 03:25
Bumps [minimatch](https://github.com/isaacs/minimatch) from 3.1.2 to 3.1.5.
- [Changelog](https://github.com/isaacs/minimatch/blob/main/changelog.md)
- [Commits](isaacs/minimatch@v3.1.2...v3.1.5)

---
updated-dependencies:
- dependency-name: minimatch
  dependency-version: 3.1.5
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…/npm_and_yarn/minimatch-3.1.5

Bump minimatch from 3.1.2 to 3.1.5
Bumps [immutable](https://github.com/immutable-js/immutable-js) from 4.3.5 to 4.3.8.
- [Release notes](https://github.com/immutable-js/immutable-js/releases)
- [Changelog](https://github.com/immutable-js/immutable-js/blob/main/CHANGELOG.md)
- [Commits](immutable-js/immutable-js@v4.3.5...v4.3.8)

---
updated-dependencies:
- dependency-name: immutable
  dependency-version: 4.3.8
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…/npm_and_yarn/immutable-4.3.8

Bump immutable from 4.3.5 to 4.3.8
@1Luc1

1Luc1 commented Mar 12, 2026

Copy link
Copy Markdown

Is it possible to rebase/merge this PR with the develop branche? We like to test this PR on the latest version.

dependabot Bot and others added 7 commits March 19, 2026 17:03
Bumps [phpseclib/phpseclib](https://github.com/phpseclib/phpseclib) from 3.0.43 to 3.0.50.
- [Release notes](https://github.com/phpseclib/phpseclib/releases)
- [Changelog](https://github.com/phpseclib/phpseclib/blob/master/CHANGELOG.md)
- [Commits](phpseclib/phpseclib@3.0.43...3.0.50)

---
updated-dependencies:
- dependency-name: phpseclib/phpseclib
  dependency-version: 3.0.50
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…/composer/phpseclib/phpseclib-3.0.50

Bump phpseclib/phpseclib from 3.0.43 to 3.0.50
Bumps [picomatch](https://github.com/micromatch/picomatch) from 2.3.1 to 2.3.2.
- [Release notes](https://github.com/micromatch/picomatch/releases)
- [Changelog](https://github.com/micromatch/picomatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/picomatch@2.3.1...2.3.2)

---
updated-dependencies:
- dependency-name: picomatch
  dependency-version: 2.3.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
…/npm_and_yarn/picomatch-2.3.2

Bump picomatch from 2.3.1 to 2.3.2
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.

5 participants