Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S sdswas.events
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Barcelona Dust Regional Center (BDRC)
  • sdswas.events
  • Issues
  • #68
Closed
Open
Issue created May 17, 2021 by mconde@mcondeMaintainer

BUG: For Upcoming events/webinars and News, consider Plone field "publishing date"

I propose to use it only in 2 lists: "Upcoming events and webinars" and "News"

Implementing this issue for all the content types that we have would require to test all the views where they appear. Also note that allowing editors to use the publication date and expiration date slows down the DB search performed to fetch the results of the list where the contents appear. So the less the better.

Edited Jul 06, 2021 by mconde
Assignee
Assign to
Time tracking