MrEd Posted September 30, 2014 Posted September 30, 2014 Hello, I am not sure if I am the first one to find this bug, but... How to reproduce: Create field FieldsetTabOpen (lets name test_tab) Create field Page (lets name test), choose Multiple pages, and type PageListSelectMultiple Add the fields to template: test_tab test test_tab_END The field "test" is not sortable. The reason is because the InputfieldPageListSelectMultiple.init is called before the tabs are rendered. My very quick workaround was to move the init method call into setTimeout, but I am not sure if this the correct choice. wire/modules/Inputfield/InputfieldPageListSelect/InputfieldPageListSelectMultiple.module:88 now looks like the line below. "setTimeout(function() { InputfieldPageListSelectMultiple.init($('#{$this->id}_items')); }, 200);" .
netcarver Posted September 30, 2014 Posted September 30, 2014 Hi MrEd, Thanks for posting this to the forum! Could you raise an issue on the ProcessWire github repository for this please? You'll need to add a little more information though - like what version of PW this applies to. Thank you and hope this gets resolved for you soon.
MrEd Posted September 30, 2014 Author Posted September 30, 2014 Hello, I have registered it there. https://github.com/ryancramerdesign/ProcessWire/issues/701 1
netcarver Posted September 30, 2014 Posted September 30, 2014 Great, thank you. This will definitely get noticed by Ryan now.
KentBrockman Posted September 30, 2014 Posted September 30, 2014 https://processwire.com/talk/topic/6119-bug-verified-sort-bug-with-pagelistselectmultiple-in-pw-240/
MrEd Posted October 1, 2014 Author Posted October 1, 2014 Yes, this is the same bug. And it is due to inactive tabs. Inactive tabs are not rendered in browsers for some time, so the javascript has not action there. I don't remmember how I solved it in other simillar situation, but in my case here the setTimeout solves the problem (I know it is not the best solution, but deadline makes to think of workarounds )
ryan Posted October 5, 2014 Posted October 5, 2014 This issue was fixed in PW 2.4 dev awhile back, so should already be fixed in PW 2.5. Though let me know if you continue to see it in PW 2.5.
Soma Posted October 5, 2014 Posted October 5, 2014 Maybe we should make bug and issue reports have PW version mandatory or we just ignore them.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now