[#CONF-10454] Default Space Content does not support macro - Atlassian JIRA

Confluence

Default Space Content does not support macro

Created: 15/Jan/08 09:01 PM Updated: 20/Apr/09 03:24 PM Resolved: 28/Oct/08 02:34 AM

Component/s:

Administration

Affects Version/s:

2.7

Fix Version/s:

2.10

Time Tracking:

Not Specified

File Attachments:

None

Image Attachments:

1. homepagenotfound.PNG
(130 kB)

Issue Links:

Duplicate

This issue duplicates:

~~CONF-10363~~ Default space content feature doesn't support macros.

Participants:	Andy Brook, David Hergert, David Peterson, Don Willis [Atlassian], Mathias Kimpl, Paul Curren [Atlassian] and Roy Hartono [Atlassian]
Since last comment:	1 year, 14 weeks, 6 days ago
Internal Complexity:	2
Internal Value:	6
Labels:
Regular Expression:	com\.atlassian\.confluence\.spaces\.listeners\.InitialSpaceContentListener\.getDefaultHomePageContent.InitialSpaceContentListener\.java:\d*.\s

Description

« Hide

At the moment Dashboard > Administration > Default Space Content does not have the ability to process macro.
Hence if a user tries to insert a macro, say noformat macro and save it, the next time a new space is created will lead to Home (Page Not Found) for that space.

And gives the following exception:

java.lang.IllegalArgumentException: can't parse argument number noformat
	at java.text.MessageFormat.makeFormat(MessageFormat.java:1339)
	at java.text.MessageFormat.applyPattern(MessageFormat.java:458)
	at java.text.MessageFormat.<init>(MessageFormat.java:350)
	at java.text.MessageFormat.format(MessageFormat.java:811)
	at com.atlassian.confluence.spaces.listeners.InitialSpaceContentListener.getDefaultHomePageContent(InitialSpaceContentListener.java:121)
	at com.atlassian.confluence.spaces.listeners.InitialSpaceContentListener.createHomePage(InitialSpaceContentListener.java:89)
	at com.atlassian.confluence.spaces.listeners.InitialSpaceContentListener.handleSpaceCreate(InitialSpaceContentListener.java:62)
	at com.atlassian.confluence.spaces.listeners.InitialSpaceContentListener.handleEvent(InitialSpaceContentListener.java:49)
	at com.atlassian.event.DefaultEventManager.sendEventTo(DefaultEventManager.java:185)
	at com.atlassian.event.DefaultEventManager.onApplicationEvent(DefaultEventManager.java:74)

The same error will also happen if the user forget to close the curly bracket.
There should be a message in the Default Space Content page that states adding macro is not supported at the moment. Or we can have a validation that checks whether or not the content is valid.

Sort Order:

[ Permalink | « Hide ]

Andy Brook added a comment - 16/Jan/08 03:45 AM

For me this was totally unexpected. This would be an ideal way to provide some basic introductory information, the odd info macro would certainly give new users some idea of what was possible with Confluence. A plain text welcome page is really not a good introduction for Confluence users...

[ Permalink | « Hide ]

Mathias Kimpl added a comment - 09/May/08 04:36 AM

I tried to workaround the problem in experimenting a little bit and comment out the brackets ({) in the default space content. But, this error also appears if i uncomment the macros. You can see the full "Default Space Content" code i made the test with:

Dieser Inhalt wurde automatisch angelegt. Bitte editiere diese Seite im Wiki Markup Editor, um die führenden Backslash (*\\*) im Template zu entfernen.

\{zone-template-instance:kb:ProjectHomepageModern}

I guess this is trange, because it shouldnt render the macro and therefore working as normal text

[ Permalink | « Hide ]

David Hergert added a comment - 07/Jul/08 10:35 PM

This is also an extremely annoying bug for us as well. I recently put a "section" and a "column" macro in the personal space default content, and all the users that tried creating a personal space are getting page not found, and so do not have a page for their personal space. So they have to go in and create a page and set it as the default for their personal space, or delete their personal space all together.

Please correct this, or at least throw an error when you try to put macros in the default content. I had 15+ users create 'broken' personal spaces before I stumbled upon the problem. They didn't know what to expect and so did not report it.

[ Permalink | « Hide ]

David Peterson added a comment - 14/Oct/08 01:42 AM

Yeah, this would seem to be a pretty straightforward issue to resolve...

[ Permalink | « Hide ]

Paul Curren [Atlassian] added a comment - 23/Oct/08 11:12 PM

The default initial content we want to be able to use in Confluence requires macros.

[ Permalink | « Hide ]

Paul Curren [Atlassian] added a comment - 28/Oct/08 02:34 AM

Fixed as part CONF-13472 which this defect was blocking