Pro 6.3.1 - Some minor issues

[urchindesign]

Well done on the new release. Wish I could have been more active on the beta but time did not allow it this time.

I work exclusively in Firefox so perhaps some of the issues are Firefox related but nonetheless.

1. The builder tends to become unresponsive at times and then I need to refresh the site (haven’t been able to look into any errors or similar but thought I would let you know.)

2. Adding borders to an element. When I open or add borders it creates a single border for all sides, as soon as I unlink the sides the color defaults to two colours with the interaction colour being undefined.

3. Preview URLs - when switching between tabs, when returning to a previous page the builder forgets the preview URL and I need to assign one again. This is specifically annoying on posts where the site has different posts. It reverts to the top post in the list. Often I will select a specific post as it is different to the others. (It does seem to happen if I switch to a component and then switch back).

4. 404 page preview in the builder - In my site it shows a random background image from one of the articles in the preview. In the front end it seems ok.

[devinelston]

I’m on Safari, and have run into 1 myself a number of times. For me, it seemed to happen when I was switching back and forth with both parameters and css. But I haven’t been able to find specific repro steps yet.

[urchindesign]

To add to point 1 - I experience a range of different things.

1. Cornerstone works but I can’t copy & paste values.
2. Cornerstone works but the preview doesn’t update.
3. Cornerstone works but I can’t type any values into the inputs.
4. Cornerstone is completely unresponsive.

[urchindesign]

Another thing I’ve picked up. Not sure if it is a mistake on my end or if colours are compatiable with responsive settings.

I have a “heading” component with a parameter that allows me to set colours with responsive breakpoints.

“textColor” : {
“label” : “Color”,
“type” : “color-pair”,
“initial” : {
“base” : “{{dc:global:color id=‘Yce6ffmyvmTs3jGvv1’}}”,
“alt” : “{{dc:global:color id=‘Yce6ffmyvmTs3jGvv1’}}”
},
“isVar”:true
}

In the component I’ve assigned everything however when I change the colour based on screensize in the element the element colour is not updating based on the screen size.

This is the component settings:

Here is the element:

Not matter what I do the element remains white and the green does not take effect.

[charlie]

1. For some of the performance issues I wanted to get us on React 18 before we started taking care of them or before React18 stops supporting legacy rendering. Oddly enough, there’s a lot of slow downs from the Scroll to Element feature. You’ll notice it’s very hit or miss and I’ve noticed it’s bogging down the App due to whatever is failing. Anyways, as we get more stable and have less and less missing features I’d like to really speed things up. If you have a particular site that is especially slow, that might me help see what’s going on too. I definitely experience it too though, especially after some long sessions.
2. I’m not sure I’m creating this properly. I never saw undefined when going from linked to unlinked. Do you have a screenshot or video you can share for me?

3. For me, it was saving the preview url, but the actual controls ended up being empty. I’ll take another look at some point and get it in the tracker.
4. I might need to see the site for this one. Could this be another plugin? Is the 404 plugin also installed? WP_DEBUG turned on might give you some answers here too.

[urchindesign]

Border when creating an element.

Click the switch and everything looks fine.

Unlink sides without creating a colour.

This is the same for each sides color.

[urchindesign]

404 page when selecting the 404 preview in the builder. So I think it may be that I’m seeing the image in the background because I can’t select the 404 preview without breaking the page. On the front-end the page works as expected.

And the full error.

And the condition.

Site is unfortunately on my development server in the office.
Not really much in the way of plugins.

[urchindesign]

I’m also experiencing issues with the below.

5. attempting to set responsive settings in parameters. (Could be me though. See post above Pro 6.3.1 - Some minor issues) I am also seeing this where I made a responsive parameter for a max length. The responsive settings show in my parameter element when I add it to the page and I can create the different values for each break point but they don’t seem to have any effect.

6. With CSS Grid, things seem to go haywire when attempting to set my cells to different positions for different break points. Will see if I can get a video of this.

[charlie]

Thanks for the info on the border unlinking issue. It was a quick one to fix it’s go up in some point release.

I don’t know if you’ve had a chance to check out 6.3.3, but with some of the changes there it seems more responsive at least on the playground and some of my sites.

4. 404 Can you inspect which element has the background image? What is the classname or better a screenshot of the dev tools?

5. I see your notes above now. I don’t know if this was your issue, but when referring to a color-pair you would use it like {{dc:p:textColor.base}}. That through me off for a while. I was not having an issue with your parameters besides that though.

6. A screenshot of what you’re are changing it too might help. Or is this like a transitioning thing where the cells are moving into place as opposed to snapping?

[urchindesign]

(2) Undefined colors – Are you able to replicate the color issue? This is happening for me in multiple different builds that were all fresh installs of 6.3.

(5) Responsive settings in Grid Cells — The biggest thing that seems to happen is consistency with the break points. If you set a different position at a given break point then it sets all break points to be “responsive” based. i.e. they get highlighted orange. This is fine and as expected. The issue is sometimes if I set the different break points to be the same then the responsive settings get taken away but not for everything and I need to start again. It also seems a bit finnicky in the sense that I will have my desktop version set up, then I will start playing with adjustments but when i come back to desktop things are all out of whack and I need to set them up again. It could be user error but it feels like the switch between “responsive” (different positions for different breakpoints) and “not responsive” (same position across all breakpoints is possibly a bit too sensitive. Perhaps it shouldn’t auto switch based on input as it seems like the switch from responsive to non responsive shouldn’t happen the way it does. (hopefully that makes sense.) Could also be user error on my end.

(6) Responsive settings in parameters — I have it as you have mentioned however for some reason the responsive settings are not working. i.e. if I change the color or length or whatever at each break point only the top break point takes effect.

[charlie]

(2) Yes. I might have not been clear earlier. It’s an easy fix and we’ll get it up in a point release.

(5) What’s the UI say when this issue happens? Does the issue sound similar to this one? 6.2.9 button width responsive settings

(6) Is this is a component or theme parameters?

[urchindesign]

(5) It isn’t for the columns, but rather when working with cells and manually adjusting the cell positions. In my instance the columns are the same across all breakpoints and the rows are set to auto. Then I’m adjusting cell values to move the cells to different positions for different break points.

(6) This is for component parameters. The two that I’ve tried to use are responsive colors and responsive widths. For the width I was using it as a max-width.

I’m not much of a video person but I’ll try get some videos of both issues.