@francisco_ramonm5108
Anything new about your decisions regarding EXTRA support?
No, I have not yet heard back from the management.
I will update here as soon I have any news.
@donovand
I hope we can find a short-term solution that does not involve choosing one or the other.
Keeping fingers crossed that a short term solution materialises in the next few days.
This will likely not happen in a few days.
Maybe we will be able to come up with some custom code workaround, but given the size of the issue, this is most likely not possible.
What if Layouts or Toolset, in general, provided a single global option for a custom namespace?
This works (in theory) in PHP.
But what with CSS?
If you namespace the classes, the CSS needs to be addressed with the new class as well.
As far I know, CSS can not hold variables like $custom_namespace-classname.
You can do things like:
div[id^=custom_class] {
color: #f00;
/* and so on... */
}
This would then address each class that begins with "custom_class".
But it's self-explaining that this will not work in that case.
I am not 100% sure but I do not think this will work.
Anyway, please be assured that our management, myself and the DEV are:
1. Aware of this issue
2. Generally speaking, we use a native (Bootstrap), and good-practice following standard code
3. We will push and communicate where needed and ensure 100% compatibility with Themes; this is our primary goal.
But I must also inform you that every development needs coding, testing, QA, QC and so on.
This requires time.
We do not send you out there with no help or assistance, but we will require some time on this.
If you are in an urgent situation, I cannot say more than that currently, another Theme should be chosen instead of EXTRA.
This is hard, I know, but I have to inform you about this, otherwise, I would be lying if I say, we will fix this in a day or two.
I cannot state ETA's or make things happen faster; this depends on many decisions that I am simply not in the position to take.
As such, I have to honestly inform you that if you are in a real hurry, waiting for a "fix" might be a too long process.
I apologise that I cannot provide a generic all-in-one solution.
I will push for it though, that I can guarantee.
Let's also not forget that ANY Plugin requiring Bootstrap will provoke the same issue, in conjunction with this kind of Themes.
That is not an excuse; it is just a reminder that we try to solve something that would be avoided if the Theme would simply use a Custom Class.
I am also not trying to put any fault on anyone.
As said we will work on this, and in a way or another, we will provide solutions.
Thank you again for your patience.
