Rob LeVine asked 2 years ago
Victor Font answered 2 years ago
Bobby Clapp answered 2 years ago
Steve Wells
replied 2 years ago Yeah, we never loved the sidebar expanding and contracting depending on the screen you are on. Now when editing a form or view, you will enter full screen mode (same way WordPress post/page editing works).
That means this function will no longer work. We'll add a note to our documentation about that.
Victor Font
replied 2 years ago WordPress post/page editing allows you to display the sidebar and turn off full screen editing. It's annoying and inefficient not to have the sidebar displayed when building a form. If I need to open another tab, we have to stop using Formidable to get to the sidebar, open the other tab, then relaunch Formidable's builder. All removing the sidebar does is create more work and a less efficient workflow. with the sidebar inaccessible, I have to open WordPress, open Formidable in a separate tab and switch back an forth to get work done.
Steve Wells
replied 2 years ago Hey Victor, Thanks for the feedback! We are looking into using the same setting WP uses to disable full page editing. So if you have Full page editing disabled in WP, FF would behave the same way.
If you have another suggestion or idea on a better way to implement this, we'd love to hear your ideas.
Bobby Clapp
replied 2 years ago I think with the dynamic need to mess with forms and views that don't necessarily relate to one another is the issue with FF full screen by default. If you can do what WP does with page editing, but set it to disabled by default, that would be the best case scenario for FF.
Victor Font
replied 2 years ago I agree Bobby. There should be a toggle that uses the same key strokes that the WordPress editor does.
Bobby Clapp
replied 2 years ago Key strokes work, but the visual ability to click a button also obviously.
Steve Wells
replied 2 years ago Gotcha...thanks for the feedback guys. We'll work on improving this.
Dan Zahlis answered 2 years ago
Steve Wells
replied 2 years ago Thanks for submitting a ticket. I'm sure our support team will get this escalated to our dev team to take a closer look and fix any issues.
Please login or Register to submit your answer
<p>Hi Rob. We have WP/FF installed on a server that runs automatic updates on plugins. They updated us from 5.5.7 to 6.0 a few hours ago and we are experiencing some eye-boogers. We use the frm_container_ in our table views to enable edit in place. It has been working perfectly. After the update, the edit column width has been reduced so much that the edit in place is virtually unusable.</p>
I've experience this as well. Need to have a per form custom CSS section as well as a global FF custom CSS. Seems that would have treated us better here.
Good suggestion. That would be nice.
Sorry about the issue with the missing custom CSS. That issue is fixed in 6.0.1. This release focused on moving the styler to the form building process/flow and introduced the templates. We are still planning improvements to the actual style editor. I love the idea of having form-specific or at least style specific custom CSS. We'll see what we can do when we revamp the style editor.
Overall, hope you are enjoying the new release. We are really happy with it.