Hi Amit
We have made some progress in identifying the problem, but I'm afraid it's not exactly good news.
The content in between the opening and closing wpv-conditional shortcodes needs to be searched using regular expressions to allow for the fact that nested conditional shortcodes may be included.
PHP7 introduced new restrictions and errors with regular expressions that weren't present in PHP5.
Lengthy content inside the conditional shortcodes can trigger these errors (specifically, a PREG_JIT_STACKLIMIT_ERROR).
The regular expressions have been reviewed and there is no scope for optimising them further to prevent such an error. Our developers are trying to identify other possible solutions, but at the moment don't have one.
The content of your conditionals is so lengthy because they wrap around the verbose fusion shortcodes.
To me it seems there are two possible solutions you can use right now.
One is to move the conditional shortcodes inside fusion builder rather than outside as you have it now. So where you have content inside a row that you want to conditionally display, more the condition inside the text module that outputs the content itself. (This is actually the expected use.)
That will output all of the rows, some of which will simply be empty according to the conditions.
Alternatively, the second option would be to create unassigned Content Templates for the individual sections, which you can design with Fusion Builder, and then edit the master template and continue to use the conditional shortcodes before and insert these templates in between the shortcodes so that they contain just a wpv-post body shortcode rather than the lengthy fusion shortcodes that they currently do.
Sorry for the extra work this implies, but it is something that the changes in PHP7 necessitate when working with conditionals that wrap lengthy blocks of content.
Let me know how you get on.
