Hi Tinah (not sure if I should use Tina, please forgive me if I am using it wrong).
Thanks for the input.
The betas we just released are pretty much release candidates. Talking about the products involved in your sample examples, I can share that:
- CRED went over our own internal testing, it was completed, and it passed, so we do not expect to make any further change to it unless we find a significant reason.
- Views and Layouts are more than half way in our second testing layer, after passign a first one without any major issue; again we do not expect to find any relevant issue.
We take testing quite seriously, although of course there might be problems (because no software is perfect). We also appreciate quite a lot all the feedback that you and our users in general provide, because sometimes we make changes and mistakes we overlook or we simply do not see the small side effects they produce. One of our key goals is to always keep backwards compatibility, and I want to apologize for the problems we might have caused related to this, like the issue this ticket was created from, about custom JavaScript simply being ignored in some CRED forms.
Now, to your specific issue here.
I tested the three scenarios that you describe, and although I think I tried to verbatim follow the steps, I could not reproduce the issue of getting a blank page. Before moving on, and for the sake of completeness, let me describe i detail what I did.
-- Layout --
I created a layout, and added to it only a Visual Editor cell. Inside that cell, I added the same content that you provide:
* the shortcode to display the featured image.
* the shortcode to display the page title.
* the shortcode to display the raw page content.
-- Test page I --
I created a new page, assigned it to use the layout created above (note that I assigned the layour here, when creating the page, and not in the layour editor page).
As page content, I added only a shortcode for a CRED user form to create a new user, that I had created beforehand. It creates subscribers.
I published the page, and in the frontend it displays fine. I tested with a "vanilla" theme, TwentySixteen, and also with Toolset Starter as a Layouts integrated theme. As I said, in both cases it worked fine, being the only difference that when using the integrated theme, the layout rendered the whole page, while when using the non-integrated theme, the layout was rendered just taking the place of the post content.
-- Test page II --
I created a new page, assigned it to use the layout created above.
As page content, I added:
- a shortcode to display a Content Template, that I had created beforehand (and displays the post title using a Views shortcode).
- a shortcode to display a CRED form to create new posts of a given post type, that I also created beforehand.
Again, and after testing with a Layouts integrated and non-integrated theme, this worked fine for me: the Content Template and the CRED form were correctly displayed, and I could submit a new post.
-- Test page III --
I created a new page, assigned it to use the layout created above.
As the page content, I added just a View shortcode for a View I created beforehand. That View lists posts of a given post type, and the View loop is wrapping each item in a Content Template. That Content Template contains a CRED shortcode to display a form to edit posts in that post type listed by the View.
For the third time, and after testing with a Layouts integrated and non-integrated theme, this worked fine for me: the View looped over the right posts of that post type, the Content Template used for each item in the loop also displayed properly, and the CRED forms were correctly displayed for each looped post, and I could edit them.
-------------------
Getting a blank page usually means an error happened, usually a PHP fatal error due to some function being called with wrong arguments, using a function that is not defined, or something like that. Those errors leave a trace in error logs. If you are testing those betas in a staging site, you should be able to take a look at such logs.
We need to see, or at least get more details, about what might be wrong here. We should rule out some basic things, like Toolset versions being mixed (we released betas for almost all out plugins, and that means that when updating one plugin to its beta version you should update them all - you should not mix the latest stable versions for some plugins with beta versions for others, for example), but ultimately we should be able to find the root cause of this.
Thanks in advance.
