-
Bug
-
Resolution: Low Engagement
-
Medium
-
3.4.9, 4.2, 4.2.1, 5.8.17, 5.9.4, 5.9.5
-
4
-
Severity 2 - Major
-
3
-
User macros appear to be ignoring the default value, this leaves an undefined value that is that is passed verbatim in the html.
For example, the line
-
- @param width:title=Width|type=string|default=600|desc=Width in pixels
plus this invocation (note: width not set)
{iframetest:source=http://www.evernote.com|height=500}produces this code
<p><iframe width="$paramwidth" height="500" frameborder="0" scrolling="no" marginheight="0" marginwidth="0" src="http://www.evernote.com"></iframe>
<br /><small><a href="http://www.evernote.com">View full page</a></small></p>
</div>
"paramwidth" has passed through to the html as unknown
I'll document the full example iin a comment.
- is duplicated by
-
-
- Closed
-
- is related to
-
-
- Closed
-
- was cloned as
-
-
- Closed
-
- links to
[CONFSERVER-23704] Default user macro parameters ignored
Support team confirms that this an issue under Confluence 5.8.17, 5.9.4, and 5.9.5. Please reopen the ticket.
I am seeing the same issue in 5.9.4. Default values are being ignored. It is annoying for string values, but for booleans, they always evaluate as true, making them useless. Macros that worked in 5.4.4, fail now.
Jonathan Simonoff
added a comment - It appears that this bug was cloned into a different bug (one about custom macros, only involving booleans). However, this one does not appear to actually be resolved – default values appear to be ignored in 5.5. My problem is with a string value in a user macro, not a boolean.
Jonathan Simonoff
added a comment - It appears that this bug was cloned into a different bug (one about custom macros, only involving booleans). However, this one does not appear to actually be resolved – default values appear to be ignored in 5.5. My problem is with a string value in a user macro, not a boolean. Scott, see Charles Hall's workaround above. This gets some defaults in via the back door.
Having the same issue in Confluence 5.4 as well. Specifically (as Andrew said above) that it works when the user enters a value different than the default but when values are entered that match the default, there is no variable/parameter substitution, $paramname is outputted to the HTML.
Defeats the purpose of having default values.
Rand McKinney
added a comment - Running into it with 5.3.1 as well. I find it surprising (and disappointing) that a "critical" bug has been open for over TWO YEARS!
Rand McKinney
added a comment - Running into it with 5.3.1 as well. I find it surprising (and disappointing) that a "critical" bug has been open for over TWO YEARS!
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center