Anonymous | Login | Signup for a new account | 2024-05-02 17:19 CDT |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Dependency Graph | [ View Issue ] [ Relation Graph ] [ Horizontal ] | |||
|
||||
|
Viewing Issue Simple Details | |||||
ID | Category | Type | Reproducibility | Date Submitted | Last Update |
0000721 | [In-Portal CMS] Admin Interfaces | bug report | always | 2010-05-01 13:24 | 2010-05-11 02:59 |
Reporter | alex | View Status | public | ||
Assigned To | alex | ||||
Priority | normal | Resolution | fixed | ||
Status | closed | ||||
Summary | 0000721: Prev/Next buttons are always enabled | ||||
Description |
On 5.0.3-B2 release Prev/Next buttons are always enabled, even, when there is not prev. button available. How to reproduce: * select 2 sections in structure & data * click edit button * now you see 1st selected section -> click next * now you see 2nd selected section -> click next * now you see broken page without any section This is all because of fix, that disabled toolbar buttons until page is fully loaded and then enabled them. There are two ways to fix this: 1. call prev/next buttton js via $(document).ready event 2. don't disable toolbar buttons until page is fully loaded, but just make them readonly (new state, that will act like disabled, but button won't be grayed out) That new "ReadOnly" status will be for internal use only. |
||||
Additional Information |
This is button code sample: <inp2:m_if check="poll_IsSingle"> a_toolbar.HideButton('prev'); a_toolbar.HideButton('next'); a_toolbar.HideButton('sep1'); <inp2:m_else/> <inp2:m_if check="poll_IsLast"> a_toolbar.DisableButton('next'); </inp2:m_if> <inp2:m_if check="poll_IsFirst"> a_toolbar.DisableButton('prev'); </inp2:m_if> </inp2:m_if> |
Main | My View | View Issues | Change Log | Roadmap | Docs | Wiki | Repositories |
Web Development by Intechnic In-Portal Open Source CMS |