Pro 6.0 rc1 - various issues / bugs

Beta
#1

Hi there, I’m in the process of building a new site from scratch and keeping track of issues I see as I go along.

  1. The shortcuts for goto-colors and goto-fonts are not working. They bring focus to the globals tab in the sidebar, but do not switch to the colors or fonts control group tab respectively.
  2. Dragging elements into a column seems to be having strange behaviour. When dragging it in, the preview box shows up, and trying to place it at the top or in between some elements does not place it in place. Instead it is inserted at the bottom or seemingly arbitrarily.

  1. I cannot override element templates. I have made some changes and saved the template, overwriting the previous one, but when dragging the template back into the builder, it is still showing the old params and content in the element.

  1. Live editing of text parameter: would it be possible to add an option for text / text area parameters to indicate that these are live-editable controls, allowing the user to edit them in the live preview?
#2
  1. A minor QoL issue, but with a new build, the default size for all dialogue boxes seems a bit small, and so far I have made every single box larger immediately. I appreciate that the user-set sizes are then cached for the next time, but just a minor change might make it that tiny bit nicer for new users (or indeed multi-time users building their n’th site in Pro!)

image
image952×916 149 KB

#3
  1. When editing a choose parameter on a component that already has a value set, if you change the value of the currently selected choice, it breaks out of the choose control and puts the cursor focus in the box. Demonstration in this video:

#4
  1. Drag and drop issue from a drop zone slot of a component. Might be related to 2 above. When dragging into or out of a component’s drop zone slot, the contents of the slot disappear altogether, or are replaced with the pending element texture. This makes it very hard to drag and drop things into a component drop zone slot, and also makes re-ordering the elements within it very tricky.

#5

#1 Noted
#2, #7 We might be changing the drag and drop library to fix some of these drag issues. For #7 though we can make sure that when you are dragging you see the dropzone.
#3 we added a context menu there. So if you find your template, right click, copy, and then on the element you can do “paste style”.
#4 I like that idea. I’ll see what kinda of indicator we can do.
#5 We can up the default size.
#6 Noted

#6

#4 anything green or with the text icon should be editable in the live preview. A text parameter would be Dynamic Content so I don’t think that could be edited in the live preview. Did that answer your question?

#7

Hey @charlie thanks for the responses.

For #3, I’m not sure if that fixes the issue. The issue I was facing was that when I save an element as the same name as a previous template and choose to overwrite the previous template, the (in theory) new template being dragged directly from the Templates section of the elements list is still actually showing the old template element. To hopefully put it more simply, the overwrite existing template option is not working, and the old template remains in place. This means the old template is still present even when being dragged fresh into the builder.

Regarding #4, I guess my ideal situation would be something similar to the option to Enable slot for... but for enabling editing in preview. In this instance, for example, I have a Headline element that I have saved as a Component, which allows me to drastically reduce the number of controls available to the user on the front end. The text content for this Headline is then controlled via a Parameter, which is very handy. However, as the parameter is then being pulled into the text_content control of the Headline element, it loses the live preview editing of a regular Headline element. I’m wondering if there could be a similar function to the Enable slot for... that would cover Enable live preview editing for...? In the old and now out of date Element API, this was achieved by indicating the specific CSS class name of the editable text container in the options => inline section of the cs_register_element function, but I’ve no idea if that is easily transferrable to something accessible via the new Parameters or Manage Element settings.

In the meantime, thanks for all you are doing to make Pro better and better every day!

#8

Thanks for the kind words. I’d be nowhere without the great users here.

#3 Okay I’ll take a look and make sure overwriting is working correctly. Do you get the right template when you refresh the page?

#4 I see now. It’s something we can definitely do after launch. We render components differently so at this point we can’t determine if it is editable anymore.

1 Like
#9

#3 Unfortunately refreshing was not working to get the updated template either.

#4 No worries at all, a future feature or even just future consideration is good enough for me!

Cheers

1 Like
#10

#1 This will be fixed in the next release.
#3 been one of those weeks. I forgot we already fixed this for the next release. Please let me know if you have that issue in the next release. Thanks a bunch.

1 Like