Ticket #11406 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Add message to content_published explaining PDF, EPUB, etc. creation delay

Reported by: ew2 Owned by: ew2
Priority: medium Milestone: BugFix - 2010
Component: Authoring Environment Version: Dev
Severity: major Keywords:
Cc: System Area: Authoring
Primary Skill: Templating
Site URL:
Suppress email to reporter: no

Description (last modified by ew2) (diff)

Authors are expecting a Collection PDF, EPUB, etc. to be available for download right after publishing. We need to add a message to content_publish that tells then to wait 24 hrs. before checking for the PDF, etc. Message would read:

PDFs, EPUBs and other downloadable files are not created at publish 
time.  Please wait 24 hours before checking if your content's 
downloadable files are available and correct.

Change History

Changed 7 years ago by ew2

  • status changed from new to assigned

Changed 7 years ago by reedstrm

"not created immediately" perhaps?

Changed 7 years ago by ew2

(In [35328]) Added message about waiting to verify PDFs, etc. Still need to test. Refs #11406

Changed 7 years ago by ew2

  • description modified (diff)

Modified message to read"

PDFs, EPUBs and other downloadable files are not created immediately. Please wait 24
 hours after publishing before checking if your content's downloadable files are 
available and correct.

Changed 7 years ago by ew2

  • status changed from assigned to testing

(In [35329]) Modified message wording. Fixes #11406

Changed 7 years ago by maxwell

  • status changed from testing to awaitinginput

The message shows up in the right place, and looks fine visually in both CNX and Rhaptos, but I'm worried about the content of the message. In my experience, things generally haven't taken more than 1 hour to build. Writing 24 hours is only to cover us in the cases where things fail to build at all, correct? Or do we get huge day-long backlogs when an author publishes several things at once? I worry that saying 24 in all cases will give people the impression that "man, CNX is slow" or that there is some human step involved, and I think it would be fair to more users to somehow convey that in most cases they can reasonably "come back and check again after lunch", but might need to wait "several" hours (how long does the queue really ever get?).

Changed 7 years ago by ew2

  • status changed from awaitinginput to assigned

After discussion this morning in Scrum, I will modify message to specify it could take 1 to 24 hours to generate items in the queue.

Changed 7 years ago by ew2

  • status changed from assigned to working

Changed 7 years ago by ew2

  • status changed from working to testing

(In [35383]) Modified message. Fixes #11406.

Changed 7 years ago by maxwell

  • status changed from testing to closed
  • resolution set to fixed

New message seems much better to me.

Note: See TracTickets for help on using tickets.