Beta2: Columns and customization, small issues found

[franticape]

Hi guys,

1. I’m testing the new beta version on a new project. I’m feeling a bit lost with the new layout so i wanted to know if by any chance it’s normal that the columns can be resized in the live editor? i read that your turned off some of the features there in the meantime but is this part of the things you turned off?

2. I also noticed that the small breadcrumb-like navigation bar was removed and i don’t know if this is intentional. if it is, where would the buttons like “customize” or the options on the element (like the different sections in the quote element “citation” “marks”, etc) be now? i can’t see them and i’m not sure if this is intended since you removed some stuff temporarily or if it’s a bug.

I like the features, and the editor feeld blazing fast right now (but i think that will change since there are several things that are disabled and i bet the live editor is a bit of a resource hog) and it feels “cleaner” now, but that’s also because many of the options are gone now,

3. Props for the dev console which gives very very useful information!

4. The tooltip on some of the elements takes too much to appear and feels like it’s broken: https://www.loom.com/share/a8e4e3f64e2d46beb688ac560ff9ec87

5. I get a few errors when i open the JS inspector but i’m not sure what they are breaking because everything seems to work:

 In: /wp-content/themes/pro/cornerstone/assets/dist/js/app.2a8a3dd.js
 Uncaught Error: Cannot apply patch, path doesn't resolve: 58419442-ab78-4544-b4c0-8a4da12b4484/image_width
 
 Uncaught Error: Cannot apply patch, path doesn't resolve: 58419442-ab78-4544-b4c0-8a4da12b4484/image_height


 IN: /wp-includes/js/dist/vendor/react-dom.min.js?ver=16.9.0
 Uncaught ReferenceError: prev is not defined
     at onUpdate (app.2a8a3dd.js:106)
     at onClick (app.2a8a3dd.js:106)
     at Object.Vh (react-dom.min.js?ver=16.9.0:163)
     at Uh (react-dom.min.js?ver=16.9.0:14)
     at Xh (react-dom.min.js?ver=16.9.0:14)
     at af (react-dom.min.js?ver=16.9.0:14)
     at Yh (react-dom.min.js?ver=16.9.0:164)
     at nd (react-dom.min.js?ver=16.9.0:15)
     at nc (react-dom.min.js?ver=16.9.0:15)
     at Of (react-dom.min.js?ver=16.9.0:38)

I’d have to check the debug.log for this last one.

Know i’m working in Minimal, with only PRO installed at the moment (literally, there aren’t other plugins yet)

[franticape]

A lot has changed here, and i have no idea where to post in the beta channel anymore, can you move it and let me know where it is so i can avoid this mistake again plase?

[tristup]

Hi @elpanda13

Thanks for reaching out.
We are still testing the upcoming version of the theme i.e 4.0.0-beta2 and will release once it passes all the test. Till then, I would like to request you to stick to stable released verion of the theme, please check the version compatibility page for the supported version.

Thanks

[franticape]

Guys, please read the entire thread.

I know this is a beta issue and in fact i left another message asking you to kindly send this to the beta channel because for some reason i can’t anymore (i have been a beta tester for years, however i had to “skip” the last one because of work and since then you changed the forum and everything and i can’t seem to post anymore in the beta channel)

The first comment was actually my feedback while beta testing the theme! it’s not a complain or anything

[alexander]

Hey @elpanda13! Hope you’ve been well. Thanks for sharing your feedback here. Sorry it’s been off my radar for a few days but now I’ve moved this topic into the beta forum. Sorry if it’s a bit confusing but you just need to start from the beta forum (https://theme.co/forum/c/beta/37) before opening a new topic.

1. We only disabled some performance optimizations for the preview. So yes, columns should definitely still be resizable but only the new Column element (still not on classic rows/columns).

2. The element navigation (controls and breadcrumbs) should always be in view after an element has been inspected. It can be dragged to the top/bottom of the screen.

3. Thanks! Glad you like it.

4. The delay is actually intentional because we didn’t want the tooltips to be constantly coming in and out triggered by normal mouse movements. It could be something we adjust to come in faster.

5. Thanks for passing along those errors! I’m pretty sure this this is something we’ve fixed but hasn’t been released yet.

All that being said, you should still be able to build pages like normal with the beta without any missing features. Once we get this next patch pushed up (beta3) let me know if it solves those for you.

[franticape]

Awesome and thanks for the beta tip, i was sure i had opened the reply from the beta channel but apparently i was wrong because i can see now that it works ( i created this as a result and it worked: Test (This should go to the beta channel) ) .

I’m Inspecting now the header and footer to see if i spot something else. it would be interesting to see how the entire editor will perform once it’s done.

Would you be able to tell me if there has been any performance improvements in this new release? i’m asking this because sometimes i build pretty codeless and medium pages (so not super short in length or elements, with maybe a few sections, 5-10 rows and 15 elements, for example) and they then open SUPER slow.

I’m talking about pages on sandboxes (i always test them first to see if the problem comes from the server, or th setup of the site where the real page is), so on a clean environment, and i’m not entirely sure how to debug these types of errors/issues.

Thanks in advance for the answer!

[alexander]

If you mean between this release and the previous official one, A big improvement in general is reducing our javascript dependency footprint significantly (over 30% reduction).

If you mean in the beta right now: As for initial load times, that does happen to be a place we’ve disabled optimizations. We should be able to increase that load time.