Project

Profile

Help

Issue #7838

closed

file publication reports wrong manifest if custom manifest is used

Added by mdellweg about 4 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix
Sprint:
Sprint 88
Quarter:

Description

Reproduce:

  • create a publication with manifest="listing"
  • inspect href of the publication; it will have manifest="PULP_MANIFEST"

Adding manifest as a field on the publication class should solve the problem.

Actions #1

Updated by fao89 about 4 years ago

  • Triaged changed from No to Yes
Actions #2

Updated by lmjachky almost 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to lmjachky
  • Sprint set to Sprint 87
Actions #3

Updated by pulpbot almost 4 years ago

  • Status changed from ASSIGNED to POST
Actions #4

Updated by rchan almost 4 years ago

  • Sprint changed from Sprint 87 to Sprint 88

Added by Lubos Mjachky almost 4 years ago

Revision 3a0cb2ae | View on GitHub

Store manifest in FilePublication

closes #7838

Actions #5

Updated by Anonymous almost 4 years ago

  • Status changed from POST to MODIFIED
Actions #6

Updated by ttereshc over 3 years ago

  • Sprint/Milestone set to 1.6.0
Actions #7

Updated by ttereshc over 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF