Hey there all. Quick heads up. I’ve identified a bug with Form Pro relating to when I depreciated the older version of the stack a few updates ago in order to add a few of the much requested features. I thought I’d fixed the bug in the last update a couple of days ago (v1.2.6) but it turned out it was a larger bug than I’d realized.
In short the bug is this – the newer version of the stack has a new Stack Identifier setting it apart from the legacy stack. All of the child stacks have a limiter that makes sure they’re inserted into the correct parent stack. Unfortunately the new version of the stack is pulling in the legacy version’s child stacks, which leads to users not being able to rearrange the child stacks (the various field types) within the parent Form Pro stack. The form itself should still work fine, it just won’t let you change the field order or placement, etc.
That said I have a fix I’m working on currently. It shouldn’t be too hard to implement. But there is a downside, unfortunately. Once this fix is released, if you’ve built a form using Form Pro since the v1.2.2 update you will need to rebuild your form again to allow you to rearrange your field types. This is because all of the child stacks will now be receiving new IDs in the coming update. There is nothing I can do about this unfortunately. For this I apologize.
As I said, I’m currently in the process of working on this fix. I hope to get it out today or tomorrow if possible, but I want to try and do some testing to ensure it all works as I anticipate. Once the update releases, just be sure to read the release notes as you will likely need to quit and restart RapidWeaver to make sure the internal child stacks with their new IDs are recognized.
If you have questions about this specific bug, please let me know.