/
Prev/Next buttons are always enabled [5.0.3-B2]

Prev/Next buttons are always enabled [5.0.3-B2]

Owned by Alex
Last updated: Sep 05, 2015

Imported From: http://groups.google.com/group/in-portal-bugs/browse_thread/thread/7c1945ce50a2f492#

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 button 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)

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>

That new "ReadOnly" status will be for internal use only.

Related Tasks

INP-571 - Getting issue details... STATUS