There are two bugs that stream editors should deal with until they get fixed.

1) There was a short period when editing a reach caused the reach length to disappear. Ryan fixed this problem, but many recently edited reaches are probably missing the length now. Stream teamers need to check their pages and add the distance back in if that information is missing.

2) On some reaches with rapids listed on the rapids tab and photos associated with rapids, the alignment has gotten very goofy. Basically photos and descriptions are out of alignment with the names of the rapids.

This bug appears when you have a photo for a rapid, but the rapid description is very short. The photo aligns to the right and the next few names of rapids slide up next to the photo on the left.

There is a simple work around. Start with the first photo that is shifted to the right and add enough rapids description, so that the description takes up more than one line on the final display. The description editing box is very narrow, so the description will have to be 3 or 4 lines there. When the description extends all the way across the page, the photo will be aligned properly all the way back to the left, forcing the subsequent rapids names to display properly below. Proceed to the next misaligned photo and write a longer description for that one also. Do the same for all the misaligned photos.



Edited 1 time(s). Last edit at 11/05/2009 06:35PM by pmartzen.

A couple of comments about the 'work around' --

1) You need to make sure the description for the rapids is two lines (or more) when the rapids page is viewed in the regular browser. The pop-up WYSIWYG editor box (where you actually enter the description) will likely need to be at least three lines long in order for the resulting description to fill one line on the browser screen.

2) EACH and EVERY rapids down the list needs to have a description longer than one line (screen width), or the same problem will again arise.

Rob Smage
AW member since 1992, volunteer since 2000, Midwest Regional StreamTeam Leader

Fixed the first problem dealing with reach length.

Can someone guide me to an example of the second?

Ryan

This one was written up as a trouble ticket: [www.americanwhitewater.org]

Two examples were listed in that ticket:
[www.americanwhitewater.org]

[www.americanwhitewater.org]

Rob Smage
AW member since 1992, volunteer since 2000, Midwest Regional StreamTeam Leader

Other reach examples with misaligned rapid photos:
[www.americanwhitewater.org]
[www.americanwhitewater.org]
[www.americanwhitewater.org]
[americanwhitewater.org]