[#CONF-4862] Use a page's content ID as the filename when exporting as HTML

Confluence

Use a page's content ID as the filename when exporting as HTML

Created: 06/Dec/05 09:39 PM Updated: 26/Dec/06 06:02 PM

Component/s:

Export Page / Space

Affects Version/s:

2.0.2

Fix Version/s:

2.3

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

CONF-6764 Zip files do not support non-latin character sets

~~CONF-2595~~ International characters in Export space

~~CONF-2023~~ Page titles may contain characters not permitted by the filesystem, breaking exports

~~CONF-6943~~ HTML space export fails with pages containing double quotes in title

~~CONF-4321~~ Exported HTML page filenames are corrupted when an umlaut is present

~~CONF-5389~~ Question mark in page name prevents export of a space

~~CONF-7318~~ Exported HTML spaces are not working correctly when titles of pages includes a regional character (ěščřž)

Part

This issue is incorporated by:

~~CONF-4861~~ Review the writing/export of files to disk using content IDs, instead of filenames

Reference

This issue relates to:

~~CONF-5642~~ Incorrect html links in Export Space

~~CONF-5128~~ Export of Pages as Word file handles German Umlaute incorrectly

~~CONF-4321~~ Exported HTML page filenames are corrupted when an umlaut is present

Participants:	Agnes Ro [Atlassian], Hernan Cunico, Jeremy Higgs and Normand Brousseau
Since last comment:	2 years, 11 weeks, 5 days ago
Resolution Date:	11/Sep/06 10:32 PM
Labels:

Description

« Hide

When we export a page as HTML, if there is a unicode/high-bit character in the page title, there will be problems writing it to disk and being linked to properly. Instead, we should refer (and name) the pages using their content ID instead.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Hernan Cunico added a comment - 15/Dec/05 10:43 PM

This issue relates to ~~CONF-4958~~

[ Permlink | « Hide ]

Normand Brousseau added a comment - 11/Sep/06 08:08 AM

Referring the pages with their IDs would indeed solve the problem; however, when we use the 'Create link' feature of the RTF editor, the default used as a link name is the page name, and not the page or content ID. Furthermore, such default allow link names to be updated whenever the destination page name is modified, which makes for significant AND dynamic link names. How could we possibly use IDs for links without losing the advantages of built-in defaults and GUI features?

[ Permlink | « Hide ]

Agnes Ro [Atlassian] added a comment - 11/Sep/06 10:32 PM

Fixed.
If the page title is not "safe", then the page id is used for the html filename in the export.