Ask a Question related to Macromedia Contribute General Discussion, Design and Development.
-
tomviolin #1
Repeating region label obscures content
I have created a template in which I have a table that has a header row
that is non-repeating, followed immediately by rows that are repeating.
The header is editable.
The problem is that the on-screen indicator of the repeating region
(Repeat: RegionName), which starts just below the header, obscures the
header. This makes it very difficult to edit the content of that
header row, since the characters are all behind the repeating region
label.
I've looked and looked, and it does not appear that there is any way to
temporarily turn off the on-screen template region labels in
Contribute, analogous to Ctrl-Shift-I in Dreamweaver, so that's not an
option.
Is this just a "feature" I'll just have to swallow?
tomviolin Guest
-
Contribute Repeating Region Glitches
I'm having a problem with Contribute Repeating Regions that I've not found dicussed/documented anywhere. This is NOT the problem documented... -
Repeating region error
When using the up and down arrows to move an element of a repeating region, I get the following error in Dreamweaver: While executing onLoad in... -
Repeating Region Won't Repeat--Permissions?
I'm having a problem with a repeating region that refuses to repeat. When I try to click the "+" button in the repeating region via Contribute, I... -
Repeating region bug/problem
I have a repeating region right aligned within a cell that is on the right side of the page (the table is 100% width). Upon going into edit mode I... -
Repeating Region
Hello all, I have a repeating region for a navigation bar. (Link | Link | Link) The repeating region looks like this: <REPEAT BEGIN><EDITABLE... -
tomviolin #2
Re: Repeating region label obscures content
I worked around this issue by adding an extra cell between the header
and the repeating cells, and creating an editable region in that cell
called "LeaveEmpty". This editable region was obscured by the
repeating region label, but so what. The important region was left
unobscured. As long as the user actually does leave the "LeaveEmpty"
region empty, the cell takes up no room (since, for this table,
cellpadding=0 and cellspacing=0 and border=0).
Now, if a user clicks on "LeaveEmpty" and types into it, that's a
slight issue, but if they can't follow such explicit direction, too bad.
tomviolin Guest



Reply With Quote

