Hi guys,
In the last couple of weeks I posted some bugs we encountered. The isVar bug has been fixed by removing it outside of the group. This is an issue on itself we know you guys are aware off.
But the problems we encounter right now are as followed:
-
font-weight parameter applies fw-bold instead of the computed bold or medium inside the CSS.
-
font-size parameter keeps being applied to the max-width (1em), works after clearing cornerstone cache, but breaks again after refreshing.
-
adding the same component to the page strips all content from the already existing components drop-in zone (enable slot) (using parameters to fill static elements inside the component is not an option as discussed in our previous thread).Reported on this thread:
Bug found when using the same components on the page -
using the list parameter is broken inside the looper json provider, needs to be the old format {{dc:p:parameterName}} instead of {{param.parameterName}}
-
Cornerstone keeps throwing an error about an undefined component being loaded on the page.
The last item has been “game” breaking for us since the last 2 months and is really breaking the way we use cornerstone and its components and limits the development.
This is the error we get, the definition changes everytime.
Could not find element definition cs2 {id: ‘undefined’, title: ‘’, options: {…}, active: true, group: null, …}
After adding some debug code to find out what, where the issue lays, we got this debug info:
Page: Homepage (ID: 611)
Missing Component Name: Unknown/Deleted Component
Missing Component ID: Pt9w85nAaasmp8Hf3z
Full Parent Chain in Navigator: Unknown/Deleted Component Component → slot → Unknown/Deleted Component [Pt9w85nAaasmp8Hf3z]
We found out that when you add a component to the page directly without using the component element (you cant use the parameters through this option) and add a second componend (child) inside the slot zone, it throws this error. But when you use the component element and add it through that it works.
So we thought that perhaps it was our own stack that had a broken database record or somewhere inside our parameter usage we had a hidden syntax error. What we did was:
- Set up a clean wordpress install
- Install Pro + Child theme
- Create an empty component with 2 columns where 1 column is a slot (drop-in zone)
- Create a basic headline component with just:
{
“headingPaddingTop” : {
“label” : “Padding top”,
“type” : “dimension”,
“initial” : “0em”,
“isVar” : true,
“slider” : true,
“keywords” : [ “auto” ],
“units” : [ “px”, “em”, “rem” ],
“ranges” : {
“px” : { “min” : 0, “max” : 150, “step” : 1 },
“em” : { “min” : 0, “max” : 32, “step” : 1 },
“rem” : { “min” : 0, “max” : 32, “step” : 1 }
}
},
“headingPaddingBottom” : {
“label” : “Padding bottom”,
“type” : “dimension”,
“initial” : “0em”,
“isVar” : true,
“slider” : true,
“keywords” : [ “auto” ],
“units” : [ “px”, “em”, “rem” ],
“ranges” : {
“px” : { “min” : 0, “max” : 150, “step” : 1 },
“em” : { “min” : 0, “max” : 32, “step” : 1 },
“rem” : { “min” : 0, “max” : 32, “step” : 1 }
}
}
} - Add the 2 column component to the page directly by using the command/alt key and “Add element” Instead of a section
- Add the headline component inside the slot zone
- Component breaks and outputs the error.
We think that this causes a lot of things to break behind the scenes, like the things I explained at the start of this post.
These issues have been present since the last 2 updates of cornerstone, we thought that the version 6.9 would fix some of the bugs. Also as explained in the post I linked, not using the slot zones or falling back to just static components is not an option for us. Also it is not a caching issue or a lack of server memory. We tested this across 4 websites and they all have the same issue.
I already reported this a couple of weeks ago, thinking it was the naming of our parameters that was using reserved keywords like maxwidth of fontsize etc:
I would love to hear your thoughts about this.