* fix(meta): ensure that `insert_after` is always considered when sorting fields
* test: add nosemgrep to comment
Co-authored-by: Dany Roberts <danyrt@wahni.com>
This has never worked since 2016... which can mean two things:
- No one really uses this.
- If I fix this now suddenly people will find different behaviour in
naming because `name_case` is selected in some doctypes (but never
tested)
* feat: add video conferencing (via google meet) for events syncing with google calendar
* fix: unset add_video_conferencing if sync_with_google_calendar not enabled
* fix: remove conference data if add_video_conferencing disabled during update
* fix: restrict add conferencing if event_category in Event, Meeting and Other
* fix: save meet link while pulling from calendar
updated response API Response comment with conference details
show google calendar section if pulled from google calendar
* feat: show link to join video conference with google meet
* fix(style): linter errors
* fix(style): linter errors
* fix: set conferenceDataVersion 1 only if google meet conferencing enabled
remove google meet link from event needs both conferenceData as null and conferenceDataVersion 1
* Update frappe/desk/doctype/event/event.py
show add_video_conferencing for events of all categories
Co-authored-by: Ritwik Puri <ritwikpuri5678@gmail.com>
* Update frappe/desk/doctype/event/event.json
show add_video_conferencing for events of all categories
Co-authored-by: Ritwik Puri <ritwikpuri5678@gmail.com>
* fix: handle empty ends_on, use starts_on
Co-authored-by: Ritwik Puri <ritwikpuri5678@gmail.com>
* fix: do not update Event modified time on db set meet link
Co-authored-by: Ritwik Puri <ritwikpuri5678@gmail.com>
* fix: add email field event participants table
set email from linked contact
google calendar event to use event participant email as attendees
* fix: attendees not cleared from google calendar event
* fix(style): linter suggestions
* fix: make email field non-read only, called set_participants_email from before_save hook
* test: update new no of fields in event doctype in test_fetch_to_customize
Co-authored-by: Ritwik Puri <ritwikpuri5678@gmail.com>
* feat: review link for Custom, build and NavBar
* feat: review link for Custom, build and NavBar
* feat: review link for Custom, build and NavBar
* feat: review link for Custom, build and NavBar
* feat: review link for Custom, build and NavBar
* feat: review link for Custom, build and NavBar
* chore: linter json
* fix: replace Block Module By Module Profile
* chore: cypress test
* chore: reset package.json to develop
* refactor: workspace link, system logs section
- removed workspace listview link, visiting list view isn't required for
practically all the tasks
- Frappe Logs -> System Logs
[skip ci]
Co-authored-by: Ankush Menat <ankush@frappe.io>
When this checkbox is checked, while uploading docs using fileuploader
the default visibility will be set to "public".
At present all uploaded attachments are private, however in following
cases it makes sense to set default as public:
1. Blog post
2. Item catalog
3. Website item
Considering this we decided to add this configurtion so developers can
specify sane default while user still has control over it using
"Customize form"
Enabled this for "blog post" doctype
Unrelatd change: consistent "form settings" section on DocType and customize
form
