You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Rüdiger Schulz (JIRA)" <ji...@apache.org> on 2007/05/14 14:56:16 UTC
[jira] Created: (WICKET-564) Problem with Autolinks inside panel
preview code
Problem with Autolinks inside panel preview code
------------------------------------------------
Key: WICKET-564
URL: https://issues.apache.org/jira/browse/WICKET-564
Project: Wicket
Issue Type: Bug
Affects Versions: 1.3
Environment: JDK1.6
Wicket quickstart
Reporter: Rüdiger Schulz
Fix For: 1.3
All my pages are subclassed from a common basepage. That page has a
Panel with login information and some links. On the basepage-markup,
the html of the panel is copied to enable an offline preview for my
webdesigner (he can work on the templates from within Dreamweaver).
The links have a href attribute, so that offline navigation is
possible.
This worked well in 1.2. In 1.3, I get a markup error at the start of the link:
org.apache.wicket.markup.MarkupException: Expected close tag for <div
id="loginInfoPanel0" wicket:id="loginInfoPanel">
The page being reported to have a problem is the subpage (!).
Now when I remove the href from the links in the basepage (!), all
pages render fine, although the links are still there in the
subpage-markups, though outside of wicket:extend.
So, in this case it was not that big of a deal, but I think this
problem might come again. I think it has something to do with
Autolinkresolver trying to generate new links in places where he
shouldn't. Is it possible to disable this?
In fact, I think the problem would occurr even without using base- and
childpages. It's just that the error message on the child page
displays the combined markup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-564) Problem with Autolinks inside panel
preview code
Posted by "Alastair Maw (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alastair Maw updated WICKET-564:
--------------------------------
Fix Version/s: (was: trunk)
1.3.0-rc1
> Problem with Autolinks inside panel preview code
> ------------------------------------------------
>
> Key: WICKET-564
> URL: https://issues.apache.org/jira/browse/WICKET-564
> Project: Wicket
> Issue Type: Bug
> Affects Versions: trunk
> Environment: JDK1.6
> Wicket quickstart
> Reporter: Rüdiger Schulz
> Fix For: 1.3.0-rc1
>
> Attachments: wicket-quickstart-autolink.tar.gz
>
>
> All my pages are subclassed from a common basepage. That page has a
> Panel with login information and some links. On the basepage-markup,
> the html of the panel is copied to enable an offline preview for my
> webdesigner (he can work on the templates from within Dreamweaver).
> The links have a href attribute, so that offline navigation is
> possible.
> This worked well in 1.2. In 1.3, I get a markup error at the start of the link:
> org.apache.wicket.markup.MarkupException: Expected close tag for <div
> id="loginInfoPanel0" wicket:id="loginInfoPanel">
> The page being reported to have a problem is the subpage (!).
> Now when I remove the href from the links in the basepage (!), all
> pages render fine, although the links are still there in the
> subpage-markups, though outside of wicket:extend.
> So, in this case it was not that big of a deal, but I think this
> problem might come again. I think it has something to do with
> Autolinkresolver trying to generate new links in places where he
> shouldn't. Is it possible to disable this?
> In fact, I think the problem would occurr even without using base- and
> childpages. It's just that the error message on the child page
> displays the combined markup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-564) Problem with Autolinks inside panel
preview code
Posted by "Rüdiger Schulz (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rüdiger Schulz updated WICKET-564:
----------------------------------
Attachment: wicket-quickstart-autolink.tar.gz
Quickstart demonstrating the problem.
> Problem with Autolinks inside panel preview code
> ------------------------------------------------
>
> Key: WICKET-564
> URL: https://issues.apache.org/jira/browse/WICKET-564
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3
> Environment: JDK1.6
> Wicket quickstart
> Reporter: Rüdiger Schulz
> Fix For: 1.3
>
> Attachments: wicket-quickstart-autolink.tar.gz
>
>
> All my pages are subclassed from a common basepage. That page has a
> Panel with login information and some links. On the basepage-markup,
> the html of the panel is copied to enable an offline preview for my
> webdesigner (he can work on the templates from within Dreamweaver).
> The links have a href attribute, so that offline navigation is
> possible.
> This worked well in 1.2. In 1.3, I get a markup error at the start of the link:
> org.apache.wicket.markup.MarkupException: Expected close tag for <div
> id="loginInfoPanel0" wicket:id="loginInfoPanel">
> The page being reported to have a problem is the subpage (!).
> Now when I remove the href from the links in the basepage (!), all
> pages render fine, although the links are still there in the
> subpage-markups, though outside of wicket:extend.
> So, in this case it was not that big of a deal, but I think this
> problem might come again. I think it has something to do with
> Autolinkresolver trying to generate new links in places where he
> shouldn't. Is it possible to disable this?
> In fact, I think the problem would occurr even without using base- and
> childpages. It's just that the error message on the child page
> displays the combined markup.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.