You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Nathan Bubna (JIRA)" <de...@velocity.apache.org> on 2007/05/17 16:21:16 UTC
[jira] Resolved: (VELOCITY-550) Velocimacros defined in a page are
also access by other pages
[ https://issues.apache.org/jira/browse/VELOCITY-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-550.
-----------------------------------
Resolution: Invalid
Please don't ask questions in JIRA. It is a place to file bug reports and feature requests. If you think you may have found a bug but aren't sure, ask about it on the user list first. This helps us deal with things in their appropriate forum and keeps our issue tracker from getting cluttered with questions that aren't actually issues. Thanks!
The relevant macro settings are documented here:
http://velocity.apache.org/engine/devel/developer-guide.html#velocity_configuration_keys_and_values
If you need help with configuration, i'd be happy to answer your questions on the user@velocity.apache.org list.
> Velocimacros defined in a page are also access by other pages
> -------------------------------------------------------------
>
> Key: VELOCITY-550
> URL: https://issues.apache.org/jira/browse/VELOCITY-550
> Project: Velocity
> Issue Type: Bug
> Components: Website
> Reporter: Chon-Ji
> Priority: Minor
>
> Hi, I have this weird problem in my velocity pages. I have two different modules on my website, both have a macro (with the same name) defined. For example, I have a macro #settable on module 1 and another #settable on module 2. They have the same name but the content differs slightly from each other. My problem is that soemtimes module1 access the #settable2 or vice versa.
> It never crossed my mind that having the same name would be a problem since they are on different pages. I thought that macro definition should only be local and not global. I was only able to solve it by using this configuration
> velocimacro.permissions.allow.inline.local.scope = true
> However this may affect other pages, is there another way to address this problem?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org