Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 913
    • Issues 913
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #618

Closed
Open
Opened Dec 20, 2018 by k054@k054

Recurring Events with file custom fields contain a bad link to the original file

This same issue was reported in https://issues.civicrm.org/jira/browse/CRM-20029 and I guess it was fixed at some point, but it's back.

Description copied from there:

When an event with a custom file field is copied by creating a recurring event the new event has a new file id but the id points to the same file on the server as the original event pointed to. The link contained in the new event is broken. If either event is edited and the file is deleted, the original file link becomes broken. The attached file should be copied on the server when the event is copied so that each event has its own file.

Edited Mar 21, 2019 by m robi
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#618