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

Feature Request: Choose whether to sync All-Day events #104

Closed
phw198 opened this issue May 13, 2017 · 8 comments
Closed

Feature Request: Choose whether to sync All-Day events #104

phw198 opened this issue May 13, 2017 · 8 comments
Assignees
Labels
codeplex discussion Originally raised as a discussion on CodePlex enhancement New feature resolved Working hotfix available
Milestone

Comments

@phw198
Copy link
Owner

phw198 commented May 13, 2017

This discussion was imported from CodePlex

aejaygoehring wrote at 2015-10-29 17:01:

I don't know how it is for everyone else, but at my place of work my calendar is pretty constantly inundated with All-Day requests from people saying they will be Work at Home or Out of Office. I try to keep my calendar trimmed of them, but it made me realize...

I really don't want any All-Day meeting synced to my Google Calendar. I've never had an All-Day item that was useful and needed to be referenced later in the other Calendar. I really just need the regular meeting during the day so I get reminders and can pull up the descriptions.

Does a setting for this exist already (I've looked around, but I could have missed it)? If not, could it be considered?
@phw198 phw198 added codeplex discussion Originally raised as a discussion on CodePlex cp-closed labels May 13, 2017
@phw198 phw198 removed the cp-closed label Jul 11, 2017
@phw198 phw198 added the enhancement New feature label Aug 9, 2017
@euinor
Copy link

euinor commented Feb 1, 2021

Hi, any news on this enhancement? It would be nice to not sync all day events.
Also, I would like to only sync accepted events - I have many events in my calendar set as 'tentative' so I am aware of them but are unlikely to attend. I don't need to sync these.

Edit: similar to #825 (as all day or tentative events are usually 'free').
Workaround: categorise all day/tentative events and exclude that category.
Edit2: workaround doesn't work 100% as you cannot categorise individual occurrences in a series, whereas you can be tentative on one occurrence in a series.

@phw198 phw198 changed the title Feature Request? Choosing whether to sync All-Day events. Feature Request: Choose whether to sync All-Day events Jul 24, 2022
@phw198 phw198 added this to Under Development in Enhancement Pipeline Jul 15, 2023
@phw198 phw198 self-assigned this Jul 15, 2023
@phw198
Copy link
Owner Author

phw198 commented Jul 16, 2023

📦 This should now be available with hotfix v2.10.0.5.zip (see instructions for applying).

image

If you give it a go, please let me know how it goes!

@phw198 phw198 moved this from Under Development to User Acceptance Testing in Enhancement Pipeline Jul 16, 2023
@phw198 phw198 added the resolved Working hotfix available label Jul 16, 2023
@euinor
Copy link

euinor commented Jul 17, 2023

Tested it (with exclude-all-day-items ticked and that-are-free unticked) and it works as expected. Thanks!

@phw198 phw198 moved this from User Acceptance Testing to Waiting Release in Enhancement Pipeline Jul 20, 2023
@phw198 phw198 added this to the v2.10.1 milestone Jul 22, 2023
@euinor
Copy link

euinor commented Jul 24, 2023

I did notice applying this hotfix turned off 'start on login'. I don't know if it was a coincidence. Is there a log I can send to you?

@phw198
Copy link
Owner Author

phw198 commented Jul 24, 2023

That's odd - do you still have the log file from the day when you applied the hotfix and first started OGCS?

What version of OGCS were you running beforehand?

@euinor
Copy link

euinor commented Jul 25, 2023

I was running v2.9.7.0.
Links below are OGcalsync.log.2023-07-17, which is the last log with v2.9.7.0
and OGcalsync.log.2023-07-20, which is the next log recorded and is says version v2.10.0.5
(hopefully the links work...)
2023-07-17
2023-07-20

@phw198
Copy link
Owner Author

phw198 commented Jul 26, 2023

From your first log file, it looks like the setting was false even under 2.9.7, so I think you just noticed it when you patched to v2.10.0.5

StartOnStartup: False; AllUsers: False; DelayedStartup: 300

Hard to know if it was a bug if we don't really know when it happened...

@euinor
Copy link

euinor commented Jul 28, 2023

From your first log file, it looks like the setting was false even under 2.9.7, so I think you just noticed it when you patched to v2.10.0.5

StartOnStartup: False; AllUsers: False; DelayedStartup: 300

Hard to know if it was a bug if we don't really know when it happened...

I hadn't changed the version in a while and it was running fine before. So if the flag was changed before I upgraded, then it must have been something I did. Chalk it up to user error for now - I'll make a ticket if it comes up again.

@phw198 phw198 closed this as completed in e9b5c36 Jul 30, 2023
Enhancement Pipeline automation moved this from Waiting Release to Delivered Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
codeplex discussion Originally raised as a discussion on CodePlex enhancement New feature resolved Working hotfix available
Projects
Enhancement Pipeline
  
Delivered
Development

No branches or pull requests

2 participants