Since the update to Elements V3.x, there have been issues with grids. When they are displayed in one column, the text overlaps. Here’s a simple example://downloadDocument/B8W90CQo71Pw
Sorry, the Link was wrong. Try this: elementsapp://downloadDocument/B8W90CQo71Pw
The grid component has not changed between versions.
I’ve looked at your project in both Elements 2.x and Elements 3.x and the layout looks the same.
Can you share more details on how it looked before and how it looks now. A couple of screenshots showing the before and after would be very helpful.
Hi Dan,
I caused the error myself, and it has nothing to do with the version update from 2.x to 3.x. Today, I restored a very old version using Time Machine, and the problem didn’t occur there. In doing so, I realized that I had set the size of the parent container to 460px, which caused the overlap. I did that because there was another issue I can’t quite remember now. We’ll see when this problem comes up again.
But here’s another suggestion. Globals are typically used when the same content needs to be placed on different pages. However, it’s also possible to set up a global as a global design component. To do this, it would be helpful to ask, when creating a global, whether the content should be static or variable. In the variable case, the “Global Overrides” option would then need to be enabled for all child objects. This option should also be available for all child objects. Currently, there are no “Global Overrides” for images.
I have had a longstanding request that globals support some form of locking for various elements in the global. This would then allow you to prevent accidental changes to elements that never change. Essentially, a locked element is static within the global.
I have been bitten so many times by accidentally moving an element in a global and have it reset all of the content, which is very painful. But if elements could be locked, this could be minimized.
Globals are incredibly powerful and useful, but some guardrails would be appreciated.
As a workaround…
Have you tried creating the global, seeing up on the page as you want it, i.e with the content and style override in place, and then adding it as a Template to the project.
That way when you drag on the Template the Global has it’s settings and overrides in place and it’s ready to go.
Hope that makes sense.
Yes, I have tried this and use it frequently, but it still does not prevent problems with accidental changes to the global by inadvertently moving an element.
I don’t understand the hesitancy for some sort of locking feature. I could not work in any of my graphics programs without the ability to lock elements.
As far as I’m concerned, it is even more critical in Elements.
It’s not a hesitancy, we’ll get round to it, it’s just a little more complex than it seems on the surface…
Leave it with us 
Yes, I don’t doubt that there is some complexity involved; there always is with most features.
Just glad to hear it has not dropped to the bottom of the list.