Beta 6.4.0 - New Page, No Cornerstone Structure

[whitemedia]

Hi,

I think I may have come across a bug when creating a new page. The steps I have taken are as follows:

1. New page created in standard WP (Pages > New )
2. Page given a title and saved as draft.
3. Page refreshed and Edit with Cornerstone button clicked.
4. Page opens in Cornerstone.
5. Page Settings template changed to Blank - No Container | Header, Footer.

At this point I would expect to see the usual options of Start from Scratch, Use Template, etc… They do not appear. Also, in the page preview, there are no Cornerstone controls and the WP sidebar is present, which should not be the case with the page template being used. (the below screenshot has the page with “Draft” status.)

One further thing is that if I inspect the Page Outline, there is no option to add a Section, it defaults to Row. (the below screenshot has the page with “Draft” status.)

However, if I Publish the page, the From Scratch, Use Template, etc. options are available, even though the Inspector still shows Add Row as the default option. (the below screenshot has the page with “Published” status.)

Can you replicate this behavior?

Thanks,
Christopher

[charlie]

I’m not able to recreate that behavior on my site. However I can see it on yours. I don’t think this site allows you to see draft pages in general. If you checkout any of the “Preview” links on a draft, it takes you to the custom 404. I left a Test page as well for you. With the 404 plugin disabled the issue persisted, which makes me think there is some routing issue from a plugin, or maybe just a staging issue. Does this issue exist on the live site?

For the fact that “Row” is the default element. I used the same name of the old preference, so this site probably had your preference saved. You can change this in the preferences window as well.

[Misho]

@charlie, I was about to mention the default Row as well. it defaults to Row even on a brand new staging site that was just updated to Beta. The same is on other test sites updated to beta.

[whitemedia]

Thanks for the information about the default Row. I have found the setting to change this.

The template issue was also present on the live site, which is still using 6.3.9. I have found the offending conflict, which was a setting in the plugin “Scalability Pro”. Changing the Archive setting “Remove OR check for private items on front end” back to its default let Cornerstone work as expected and I am now getting the correct templates. Sorry for the red herring on this one! Thanks though for clearing up the default element query.

[Misho]

Yes, that is the setting to change, but the issue is that this must not change automatically upon updating the site. The setting should emulate the old behaviour, and of course, it is a great addition for users to change it.

[DoncoMarketing]

1. Totally agree with @Misho that CS should preserve the former default. Love this as an addition though.

2. This might be a bit of an off-the-wall thought. Not even sure if it is possible but what if there were two options for default containers – one for top level defaults and one for internal defaults.

Top Level Container Default (would always be when no other container is present): as I would still love for this to be “Section” personally.

Internal Container Default (would always be the default when inside of a parent container): as I would love for this to be “Div” personally and then choose row when needed.

[charlie]

I’ll change the preference to a new name to prevent upgrade changes I think y’all are right as well.

2. I can add a request for what I would call Section Container Default, I’m not sure the above would work with Grids. thanks!