WIP: Component and Element Manager issue

Bugs
1

Browser: Chrome 136.0.7103.93
OS: Windows

Hi team,

Elements that are inside the component are still identified as unused in element manager > usage. In addition to this, if you agree, it makes sense that if we convert an element to a component, even if we have not used that component on any page, that element should not be identified as unused.

Please watch the video below.

2

Hi @HOSEIN,

thank you so much for your report. I was able to replicate it locally and I’ve created an internal task.

Now, regarding the part where you said:

I don’t think this would be correct. If I have a component, but don’t use it on a page… the element is unused? :thinking:

Best regards,
Mate

3

Hi Matej,

I think I may have misrepresented what I said due to using Google Translate, and I apologize for that. So let’s go step by step.

Suppose we didn’t use the counter element on any page. Now we will use this element in a component, but we will only create the component and not use it. Now the question is, is the counter element still an unused element?

Honestly, I think it shouldn’t be an unused element. Even though we haven’t used that component on the page, we have a counter element in the component.

This is exactly what happened to me. Before using version 2, I had a component that used a divider element. In fact, the divider element was only in the component. Not on any other page. On the other hand, I wasn’t using that component on any page. After updating to version 2 and disabling unused elements, I accidentally added that component to the page while the divider element was disabled.

element manager
element manager1337×481 34 KB

4

Hi @HOSEIN,

thanks for further explanation. I still think that if the component is unused, and that the element is not rendered anywhere on the page, the counter should not increase.
But, I’ll add a note to the task anyway, just so that we have a reference, if we decide differently.

Thanks,
Matej