History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: SCAFF-108
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Critical Critical
Assignee: David Peterson
Reporter: Yuri Ziryukin
Votes: 1
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
Confluence Extension: Scaffolding Plugin

Scaffolding conflicts with {dynamictable} and {dynamictasklist} macros in IE

Created: 27/Mar/07 05:58 PM   Updated: 17/Mar/08 03:48 AM
Component/s: {table-data}, {text-data}
Affects Version/s: 2.3-dr4
Fix Version/s: 2.7-dr9

Time Tracking:
Not Specified

File Attachments: None
Image Attachments:

1. Firefox.JPG
(90 kb)

2. IE.JPG
(93 kb)
Environment: Confluence 2.4.3 Standalone
Issue Links:
Relates


 Description  « Hide
Scaffolding macros like {text-data} and {table-data} conflict with macros {dynamictable} and {dynamictasklist} in Internet Explorer. However in Firefox everything is fine.
As soon as our company use IE, this is a serious issue for us.
Attached are two screens. How it looks like in Firefox and in IE. In IE the contents of scaffolding macros is completely lost immediately when you add either {dynamictable} or {dynamictasklist} to the same page. In addition, once I go to the edit mode in IE with, I get Javascript errors.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Yuri Ziryukin - 27/Mar/07 06:04 PM
By the way, if there's no {dynamictable} and {dynamictasklist} macros in the same page with scaffolding macros, then the latter ones work ok. No problems displaying and editing tables in IE.

Marc Adams - 08/Apr/07 10:48 PM
These two issues seem to be related.

Britt Treece - 03/May/07 08:31 PM
This issue also shows in Scaffolding 2.3-dr5

Riyaz Shaikh - 28/Nov/07 05:34 AM
Please provide me code of this screen shots.
I am trying to solve this Issue.

David Peterson - 22/Jan/08 06:24 AM
The problem here seems to be that the {dynamictable} and friends create <form> elements, which, when editing a scaffold page will be inside the 'edit scaffold' form. The simplest solution I can think of is for Scaffolding to pre-process the rendered page and remove any extra <form> elements before sending it to the browser. Of course, this won't work if the form is injected with JavaScript, but it should solve most problems I believe.

David Peterson - 01/Mar/08 01:23 AM
The current solution is to remove any <form> elements in the page before sending it back to the browser. This means that it looks like the dynamic task list will still work, but it may have bugs if you try. However, the scaffold data will at least now save correctly.