Hello everyone,
I’d like to bring up an issue regarding the conflict between MFE and Indigo, and find out whether I’m the only one facing it — and possibly identify solutions to some of the problems. For now, I’ll list the issues I’ve encountered while using the Indigo plugin. I’m not 100% sure if Indigo is solely to blame, as the problem might be coming from the MFE plugin. In any case, disabling the MFE plugin just to make Indigo work doesn’t make much sense to me — ideally, they should work together smoothly without interfering with each other. Otherwise, perhaps it’s better to fully switch to using MFE on all pages.
Bug when editing the footer. When modifying the footer via plugin slots for MFE, some pages show two footers — one from Indigo and one from MFE. Obviously, this shouldn’t happen, and what’s strange is that it only occurs on some pages, not all.
Login page logo issue. If only the MFE plugin is enabled (without Indigo), a logo is displayed that links back to the homepage. But when both MFE and Indigo are enabled, the logo disappears — even though it should be there for better user navigation.
Style overriding issue. I’m unable to override Indigo’s styles in the /lms/static/css or /cms/static/css files, even though I can successfully edit the .html templates. Maybe this isn’t technically a bug, but I’d really appreciate it if someone could share how to properly do this.
I’m asking everyone involved in the awesome Open edX project to please take this into consideration. I’d love to get feedback not only from the developers, but also from anyone who may have encountered similar problems.
Hi @abylaikhan.suev.02 . First, thanks for adding an in-depth context and explanation. That makes it very easy to understand the issue and carry on the discussion. There have been issues with Indigo and Tutor Maintainers fix them on a priority basis. There have been larger conversations on opposing views of making Indigo default theme or not including it in tutor by default. Indigo is an important component of Tutor, and our aim is to make it as stable as possible.
Please feel free to file the above issues on GitHub · Where software is built. They will be triaged and fixed accordingly. When creating the issue, it would be important to add all the relevant details, like pages where you notice the issue, the logs, the custom plugin or code, etc.
As noted in the answer, this is not a bug in Indigo, but is related to how you forgot to re-build the openedx and mfe Docker images.
Without more details, it’s impossible to draw a conclusion that the issue is related to Indigo. We would need:
the exact changes you made
screenshots of the issue
which MFEs are affected, and which ones are not
My gut feeling tells me this is an issue with plugin slots, not with Indigo.
This seems to be a feature, not a bug. But we can’t say more without screenshots. What is “this logo” that you refer to?
Indigo is not doing much with certificates. As Maria commented, the real issue is with the message “the user has no eligible cert for…”. I suspect that when Indigo plugin is disabled, the certificate is incorrectly displayed because of a rendering error (see the “missing theme” error message).
You are trying to address too many problems at once, and you are making assumptions about the root cause which might not be right (note I’m saying “might”). I suggest you do the following:
Try to tackle just one issue at a time.
Thoroughly describe your problem. Include accurate steps to reproduce your issue, screenshots and logs. What might be obvious to you isn’t to others who are staring at their screen on a different continent.
Don’t make assumptions about the root cause of the issue – until you find conclusive evidence. Otherwise you will waste your time on false leads.