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

Auto-refresh #31

Closed
2 tasks
georgehrke opened this issue Sep 17, 2016 · 16 comments · Fixed by #6152 · May be fixed by #2917
Closed
2 tasks

Auto-refresh #31

georgehrke opened this issue Sep 17, 2016 · 16 comments · Fixed by #6152 · May be fixed by #2917
Assignees
Labels
2. developing Work in progress enhancement New feature request skill:frontend Issues and PRs that require JavaScript/Vue/styling development skills

Comments

@georgehrke
Copy link
Member

georgehrke commented Sep 17, 2016

We should implement this in two steps:

  • periodically check for updates of event in known calendars
  • periodically check for new or updated calendars

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@georgehrke georgehrke added 1. to develop Accepted and waiting to be taken care of enhancement New feature request skill:frontend Issues and PRs that require JavaScript/Vue/styling development skills good first issue Small tasks with clear documentation about how and in which place you need to fix things in. labels Sep 17, 2016
@georgehrke georgehrke added this to the 1.5-current milestone Sep 17, 2016
@georgehrke georgehrke added 2. developing Work in progress and removed 1. to develop Accepted and waiting to be taken care of labels Oct 22, 2016
@georgehrke georgehrke self-assigned this Oct 22, 2016
@georgehrke
Copy link
Member Author

requires #209

@georgehrke georgehrke modified the milestones: 1.6.0-next, 1.5.0-current Jan 16, 2017
@georgehrke georgehrke removed the good first issue Small tasks with clear documentation about how and in which place you need to fix things in. label Mar 25, 2017
@georgehrke
Copy link
Member Author

Let's implement #40 first.

Otherwise stuff like keeping events being edited locked will be a huge pain.

@georgehrke georgehrke modified the milestones: 1.7.0-next, 1.6.0-current May 17, 2017
@georgehrke georgehrke added 1. to develop Accepted and waiting to be taken care of and removed 2. developing Work in progress labels Nov 5, 2018
@cl4x
Copy link

cl4x commented Jul 11, 2019

no news on this features? in 1.7.0 the autorefresh do not work

@georgehrke
Copy link
Member Author

in 1.7.0 the autorefresh do not work

Not surprising, since this issue is still open 😉

Please check the information on the right. It contains all the information you need:
A1E77917-B021-414C-96EC-E55A044874C6

@cl4x
Copy link

cl4x commented Jul 11, 2019

ok sorry, i have see this
immagine

@vchrizz
Copy link

vchrizz commented Nov 1, 2019

using following workaround until this issue is fixed:
in file core/templates/layout.user.php add after <title>

                <?php
			// if loaded app is calendar, add html meta tag to refresh page every 60 seconds
			if ($_['appid']=='calendar') {
				print '<meta http-equiv="refresh" content="60">';
			}
		?>

@georgehrke
Copy link
Member Author

I would strongly advise anyone against using that workaround, because it just reloads the calendar app every 60 seconds, no matter whether you are just creating / editing an event or not. Definitely not a solution.

@vchrizz
Copy link

vchrizz commented Nov 1, 2019

correct, thanks for pointing that out, i should have mentioned that!
as i do not use the app via webbrowser, but manage my events via smartphone (synced from another calendar app), this is not a problem in my case.
for explanation: i use a tablet on a wall to display the nextcloud calendar (in a webbrowser) and for that it is not practical to be forced to manually refresh the page to see the recent calendar status.
(if 60 seconds is too fast, you may also set it to some higher value like 300 seconds for a refresh every 5 minutes)

@dev-zero
Copy link

dev-zero commented Mar 6, 2020

Will the tasks app automatically profit from the implementation in the calendar app or should I open a separate feature request there if I would like to see automatically refreshed task lists?

@georgehrke
Copy link
Member Author

@dev-zero No, this issue is only about the calendar app. The tasks app will need to implement this separately.

@georgehrke georgehrke mentioned this issue Apr 17, 2020
3 tasks
@georgehrke georgehrke modified the milestones: 2.1.0, 2.2.0 Sep 4, 2020
azul added a commit that referenced this issue Feb 26, 2021
Fetch the open calendars every 20 seconds
and check if they have changed since they were loaded.

If a calendar changed remove all it's data from the store
and thereby effectively trigger a reload.

This is a fairly brute force approach as it drops all known data
rather than fetching only the data that changed via the caldav sync API.

However Caldav sync is yet to be implemented. (nextcloud/cdav-library#9)
So this serves as a workaround for the time being.

See #31.

Signed-off-by: Azul <[email protected]>
azul added a commit that referenced this issue Feb 26, 2021
* Add new calendars to the list as they show up.
* Reload non-public calendars if they are updated on the server.

Fixes #31.

This works but it is not an optimal solution:
* If a calendar changes it reloads the current view
  no matter wether anyting in the view changed or not.
* If a calendar changes it drops all cached events
  even if they did not change.
* If an event is added to the calendar or moved
  this calendar will also be reloaded because the new event
  changed the syncToken on the server.
* If a calendar changed
  it will be added to the bottom of the list of calendars.

I would be fine with most of these but the last one needs to be fixed.

Signed-off-by: Azul <[email protected]>
@ChristophWurst ChristophWurst modified the milestones: 2.2.0, 2.3.0 Mar 24, 2021
@ChristophWurst ChristophWurst modified the milestones: v2.3.0, v2.4.0 Jun 24, 2021
@ChristophWurst ChristophWurst modified the milestones: v2.4.0, v2.4.1 Nov 25, 2021
@tcitworld tcitworld removed this from the v2.4.1 milestone Dec 17, 2021
@AlbertUnruh

This comment was marked as spam.

@st3iny st3iny assigned st3iny and unassigned georgehrke Jul 10, 2024
@st3iny st3iny added 2. developing Work in progress and removed 1. to develop Accepted and waiting to be taken care of labels Jul 10, 2024
@st3iny st3iny moved this to 🏗️ In progress in 💌 📅 👥 Groupware team Jul 10, 2024
@jancborchardt jancborchardt moved this to 🏗️ At engineering in 🖍 Design team Jul 11, 2024
@github-project-automation github-project-automation bot moved this from 🏗️ At engineering to 🎉 Done in 🖍 Design team Jul 15, 2024
@github-project-automation github-project-automation bot moved this from 🏗️ In progress to ☑️ Done in 💌 📅 👥 Groupware team Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2. developing Work in progress enhancement New feature request skill:frontend Issues and PRs that require JavaScript/Vue/styling development skills
Projects
Archived in project