
|
If you were logged in you would be able to see more operations.
|
|
|
uPortal
Created: 28/Oct/04 08:14 AM
Updated: 05/Mar/08 07:59 AM
|
|
| Component/s: |
Aggregated Layouts
|
| Affects Version/s: |
2.5.0 M1,
2.6.0 M1,
2.5.1 RC1,
2.5.0 RC1,
2.5.0 RC3,
2.5.0 RC2,
2.5.0 GA,
2.5.1 RC2,
2.5.2 RC1,
2.5.1 RC3,
2.5.1 GA,
2.5.3 RC1,
2.5.2 GA,
2.5.3 RC2,
2.5.3 RC3,
2.5.3 GA,
2.6.0 RC1,
2.6.0 RC2,
2.5.3.1,
2.6.0 GA
|
| Fix Version/s: |
2.5.4,
3.0.0-M5,
2.6.1 RC1
|
|
|
with uPortal 2.3 and 2.4 :
If I make a mistake in a pushfragment, for example :
<restriction path="local" name="priority" value="20000-10000"/>
instead of
<restriction path="local" name="priority" value="10000-20000"/>
(fragment developers in fragments.xml)
ant pubfragments accepts the file, the value "20000-10000" is written in
up_layout_restrictions table.
Then, the users layout managment is disorganized, even if I repair my mistake in
fragment.xml and republish it.
I think pubfragments must control fragment coherence before publishing in database.
|
|
Description
|
with uPortal 2.3 and 2.4 :
If I make a mistake in a pushfragment, for example :
<restriction path="local" name="priority" value="20000-10000"/>
instead of
<restriction path="local" name="priority" value="10000-20000"/>
(fragment developers in fragments.xml)
ant pubfragments accepts the file, the value "20000-10000" is written in
up_layout_restrictions table.
Then, the users layout managment is disorganized, even if I repair my mistake in
fragment.xml and republish it.
I think pubfragments must control fragment coherence before publishing in database. |
Show » |
|
Patch to check priorities
Added following block of code to check if valid priorities were entered in
fragments.xml:
String priority = ai.getValue("value");
StringTokenizer st = new StringTokenizer(priority, "-");
if (st.countTokens() == 2){
String minPriority = st.nextToken();
String maxPriority = st.nextToken();
if (maxPriority.compareTo(minPriority) < 0){ System.out.println("ERROR: Invalid priority. Check priorities to ensure they are valid."); System.exit(1);}
}