Save-button grayed out on multi-page form

[juuser]

Hi again,

I have another problem with my multi-tab form. Save-button is grayed out even when I activate every tab. After pressing Apply, it becomes active. What could cause this?

List / form is the same as in this thread:
http://fabrikar.com/forums/index.php?threads/textarea-text-not-saving.48142/
So if you already go to my site, maybe it's easier to take a look at this problem at the same time.

BR,
Martin

 

[cheesegrits]

Try switching WYSIWYG off in the textarea. I think there's a JS error happening on load in the WYSIWYG handling which is breaking the multi-page code as well.

-- hugh

 

[juuser]

Hi Hugh,

Thanks, I tried that but no change
BR,
Martin

 

[cheesegrits]

Are you trying to use multi-page on a tabbed template? There should be a warning rendered if you try and do that, as the two features are not compatible. There seems to be something in your site template that is hiding warnings. It shows if you append ?fabrikdebug=1 to that form URL.

index.php/tuotteet/asiakkaiden-reklamaatiot/form/23?fabrikdebug=1

-- hugh

 

[juuser]

I think so. I have "Pagination - multi page forms -> Page break" set to "both" for some of the groups on this form. For some reason no warning message, even with unmodified bootstrap_tabs template.
That would have been a wonderful solution for my case, but I think I can re-group my elements and live with that

 

[juuser]

I now noticed that I can leave with that, but my life would be miserable I thought I just re-group my elements, but one group/element is repeatable, so I cannot transfer this to another group.
And it wouldn't look very user-friendly, if I have only one element in a separate tab.

Is there some serious reason why multi page form is not working with tabbed template? For me it seems that it almost works as when I first press "Apply" and after that "Save", record saves fine.

BR,
Martin

 

[cheesegrits]

Is there some serious reason why multi page form is not working with tabbed template?

Yes, because it would be a lot of work, and nobody has stepped up to fund it.

Basically, if there's a "nice to have" feature which benefits everyone (like 90% or more Fabrik users), I'll usually take the time to code it on spec, invest my time, just to make Fabrik better for everyone. But if it's a feature which would only be used by a small percentage of users, it can only happen if there is someone prepared to fund the work. There are only so many hours in a day, and revenue from subs barely pays for the support work they entail. And much as Fabrik is a labor of love, I can't work for free more than a certain number of hours.

-- hugh

 

[juuser]

Thanks Hugh, I totally understand. In spite it seems as it "almost works", there might often be quite a lot of effort to get it into state of "100% works".
If it's not too much trouble, maybe you could send me a PM with approximate cost for that feature. I can see then if it's possible at all for me to fit this in my budget.

For now I'll try to find some alternative solution.

BR,
Martin

 

[cheesegrits]

Sorry, missed your reply. I'll try and find some time to see how much work would be involved.

Sent from my HTC6545LVW using Tapatalk

 

[juuser]

Thanks, I hope you can find the time to make the cost estimation.

BR,
Martin

 

[juuser]

Friendly bump

 

[Sophist]

I wrote a fix for this several years ago but I have a feeling that for various reasons it was never merged.

I am not sure but it may be this commit https://github.com/Fabrik/fabrik/pull/883/commits/062d7448571f4edf2423e953f784eee88b4cd1cd

P.S. From memory I was trying to fix various things in this including validating on Next but not on Prev.

 

[juuser]

Thanks Sophist, I hope it will make Hugh's job easier if he finds time to dig into this.

BR,
Martin

 

[Sophist]

Hugh - please look at merging my PR#1939 before you look at this as it does quite a lot inside form.js.