Beta 6.0 - Initial feedback

Howdy, @Misho! As always, the feedback is certainly appreciated and we take everyone’s thoughts into consideration. Here are my thoughts on these things at the moment:

  1. One of the realities of adding more flexibility to the document structure over time (as people have requested) is the mixing of “Layout” Elements with “Standard” Elements. At this time, without completely rethinking some things, I’m not sure there’s much we can do in the Outline itself as this is simply the nature of working with multi-dimensional documents. Something I personally do in various builds is prefix / suffix things with a naming system that makes sense to me. For example, I might do something like “(SEC)”, “(ROW)”, “(COL)”, “(GRD)”, “(CLL)”, “(DIV)”, as a convention to give me more oversight from the Outline pane itself. As part of this Beta cycle, one of the biggest changes we’ve made to help with identifying Elements is on the Inspector pane itself. By default, the name of the Element is used in the title, but if you rename the Element, the “Inspector” title at the top of the Workspace is replaced with {{element_type}}. For example, if you had a Button that you built out of a Grid with multiple Cells inside it, you could rename that Element “My Button” and right above it you will now see “Grid” to help you understand which Element you’re on. I know this isn’t on the Outline pane, but a naming system that makes the most sense to you paired with some of these other updates I think are a very clean way to do this. Other apps like Figma for prototyping basically do this…they offload much of the understanding of what you’re working with to the label itself, encouraging users to use a slash syntax to group and identify content easily (e.g. “Button / Primary,” “Button / Secondary,” et cetera).
  2. We understand that this adds an extra click at the top-level; however, it also lends more consistency throughout the whole document. Now, clicking to add an Element is always the same outcome presenting you with the whole library to work with. Unfortunately, if you have a lot of Favorites as you mentioned, it might push down the new “Layout” group introduced in Beta 2, but this is a reality of surfacing those individual items. Additionally, the search field is highlighted by default, allowing you to start typing and find any Element and surface it even if it is quite far down the list. Finally, adding Sections are the outlier…I understand that at the top-level it is likely common to need them, but far and away once you move beyond that level, you’re working with everything else (Sections aren’t even allowed nested). Once you have one Section on the page, it is also possible to duplicate another and use that as a starting point. So I think all of the tradeoffs considered here and the consistency this experience provides, we will likely be keeping things as is for now as a big part of this update is trying to bring more consistency to how things are done and have less outliers.

Thanks!

1 Like

All right, I understand. We’ll get used to the changes. :slight_smile:

I noticed a small issue in Beta 2:

When clicking “Add Element” in an area between sections, if that happens towards the middle of the list, the window opens upwards and the search gets cut off. (Chrome + Windows).

image

This happens only with two positions in the middle of the list. The rest forces the window to open upwards or downwards and it is all OK.

Hey, @Misho! So you’re saying the search is getting cut off by the browser window itself, correct? I can see that this does indeed happen for me a little bit depending on my page layout and where I click on the “Add Element” button. This isn’t entirely unavoidable due to the variable nature of different users’ screens, setups, et cetera. One thing you could try is adding the following to your UI CSS file:

:root {
  --d-picker-modal-is-elements-max-height:    360px !important;
}

This will allow you to reduce the max-height of the Elements picker modal. The default is 400px, so something like 360px may reduce it just enough on your device to keep the search from getting cut off and have a little more wiggle room going up / down.

Thanks!

Thank you @kory, I’ll try that.

I just run into a much bigger issue: I created a staging copy of https://www.optika-kobacic.hr/, to test the Beta 2 out.

Here is a WooCommerce category layout: https://www.optika-kobacic.hr/katalog/naocale/dioptrijske/

This is how it looks on Beta 2: https://www.staging11.optika-kobacic.hr/katalog/naocale/dioptrijske/

Basically, there is no Pro Layout. That’s the default WC archive.

I am not sure if the fact that Permalinks Manager Pro was used to get logical URL’s is the problem, but this isn’t happening in the current Pro version.

I’m adding the secure note with access to both websites.

Thanks!

EDIT: I just tried on a different website. All Layouts got the default WP sidebar. Then I deleted the Beta and put Pro 5.0.8 back, but the entire website was broken, including the homepage. I had to restore from the backup to get the site back.

Here’s another one:

Please try clicking the top navigation item called “Brendovi” on this website:

An off canvas shows up, with this design:

image

On Beta 2, it looks like this:

image

Thanks!

@kory, I forgot to confirm that the issue with the observer was resolved in Beta 2. I can edit pages on all Installs. :+1:

1 Like

@Misho, thanks for sharing all of this.

  1. With regards to the WooCommerce layout not getting carried over, I have tested this out myself and can confirm I am experiencing the same issue. I have an old test site on the previous version of Pro and it had a Blog, Post, Shop, and Product Layout all built out and assigned. When I upgraded that test site to Beta 2, I can see that my Blog and Post Layouts are carried over, but my WooCommerce ones are not. So something is happening specifically to those post types, and we will look into what is causing it. My Blog and Post Layouts carried over fine and are outputting as I had them previously.
  2. For your navigation, was this an Off Canvas area with perhaps the Navigation Stacked or Navigation Layered Elements used within? I built out a test trying to mimic something similar, and while I did not have a seemingly complete loss of styling as you did here, I did get a few mixed up issues with my icons in particular when using those inside the Element. Everything else seems to be fine (even my close button retained it’s styling). If you could give a few more details here, that would be helpful so I could try and recreate your situation as closely as possible).
  3. Thank you for confirming on the “Edit Page” observer issue…I will mark you off there!
1 Like

Thank you @kory!

  1. The navigation is an Off-canvas element with the Navigation Inline added to it. It is just vertically oriented.

Got it, thank you!

1 Like

Hi @kory continuing on the original thread, if it is a problem to add a preference setting to display Copy/Paste JSON in the context menu, then it would be great if the Tools > Elements section was at the top inside the Dev Toolkit. This would make sense since it is such a useful and often used option.

Howdy, @Misho! I have noted this down, but at the moment we are working through other line-items to ensure stability with the main release features. Thanks!

Juas a quick (late) note that WooCommerce layouts are still broken in Beta 3 for me, in case you already worked on this. Thanks!

The more I build with B3 the more I agree that this one (small) nuance is a bit of a headache.

95% of the time I want a section as my initial container in the outline, now I need to consider > scroll > select all to do something that was mindless before. Surely there is some sort of middle ground here … :slight_smile:

1 Like

@Misho, if you visit Cornerstone at all, do your layouts fix themselves? You shouldn’t need to save. If so this migration will correctly happen in the next release without having to visit cornerstone. If not can you send me a secure note?

@DoncoMarketing, thanks for sharing. We hear you on this, and while I’m not sure if any changes will be made here at the moment, I have noted it down.

Hi @kory!

Hmm, many layouts are not even listed, so I cannot visit Cornerstone. If I go through the list, some layouts are visible but those do not fix themselves.

Looks like the layouts assigned to taxonomies and custom post types are gone.

One specific thing about this website is that many of the URL’s are altered by the “Permalinks Manager”. That however, never made any trouble to Pro.

Links are in the private note.

Thank you!

Thanks, @Misho. I’ve noted this down to be looked into.

1 Like

Hi @kory , I Just made a fresh staging instance and all I did was adding Beta 3 to it. I also activated the Child theme because in the final production that will be needed. Child theme doesn’t seem to do any difference.

Thanks!

Thanks for that, @Misho! Still haven’t had a chance to look into this one yet, but this will all be helpful when we get there!

Hey @Misho we are looking into your layout issues. I noticed on Brands the condition value is gone for Product Taxonomy. Do you have the same issue? To clarify /katalog/naocale/dioptrijske/ should be using layout Product Categories? Is there any way you could secure note me a MySQL dump file? I have suspicions it’s a localization error, but I will know for certain this week.

1 Like

Hi @charlie!

Thanks!

Yes, that’s a Product Category. It has non-standard URL because I wanted logical breadcrumbs for the visitors so I used the Permalinks Manager Pro plugin.

You can find the MySQL dumps of both the production and the staging website in the secure note. I noticed that the staging copy has double the size of the production file. Perhaps that’s some Siteground thing with staging instances.

Thanks again!

1 Like