Bug 86614 - Wrong description for PUBLISH_SOURCE (publish-to-fs-source) in com.arsdigita.cms.publishToFile.Initializer.java
Summary: Wrong description for PUBLISH_SOURCE (publish-to-fs-source) in com.arsdigita....
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: documentation
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bryan Che
QA Contact: Jon Orris
: 86611 86612 86613 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2003-03-26 14:39 UTC by Christine VACHER
Modified: 2007-04-18 16:52 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-06-02 20:25:38 UTC

Attachments (Terms of Use)

Description Christine VACHER 2003-03-26 14:39:29 UTC
Description for PUBLISH_SOURCE in
com.arsdigita.cms.publishToFile.Initializer.java reads:
PUBLISH_SOURCE, "The base and port that must appear after 'localhost' to allow
reading " +"content to be published.  Example: If source of published items are
read at " +"'http://localhost:8713/acs' the PublishSource would be '8713/acs'"

This is wrong. A value of "8713/acs" does not work.
com.arsdigita.cms.publishToFile.PublishToFile.java requires a valid URL ending
with '/':
throw new InitializationException("Invalid URL specified for publishSource. " +"
Must be like: 'http://localhost:port/base', " +
throw new InitializationException("PublishSource sourceBase must end in '/'");

Comment 1 Christine VACHER 2003-03-26 14:42:26 UTC
*** Bug 86611 has been marked as a duplicate of this bug. ***

Comment 2 Christine VACHER 2003-03-26 14:43:46 UTC
*** Bug 86612 has been marked as a duplicate of this bug. ***

Comment 3 Christine VACHER 2003-03-26 14:44:36 UTC
*** Bug 86613 has been marked as a duplicate of this bug. ***

Comment 4 Richard Li 2003-04-15 19:06:36 UTC
Bryan, can you investigate and verify?

Comment 5 Bryan Che 2003-04-15 20:53:58 UTC
Yes, there needs to be a "/" at the end.

Comment 6 Richard Li 2003-06-02 20:25:38 UTC
Fixed on the tip. Sorry for taking so long.

Note You need to log in before you can comment on or make changes to this bug.