Is it possible to use Frontend Plugin Framework Slot on quince tutor 17.0.0?

Development
1

I wasn’t able to find this information for sure from the documentation so I just wanna ask if it’s possible to use Frontend Plugin Framework Slot on my quince tutor 17.0.0? I’m trying to modify the LearningUserMenuSlot and I don’t wanna change frontend-component-header to do this. What would be the easiest way? Basically I just wanna leave “Logout” and remove all other dropdown options. Attached below is the dropdown I’m talking about. I’m fine if there is a solution to do a repeated change across all MFEs, as long as I can make it work.

image
image1813×562 64.1 KB

2

Hi @Muhamed_Cicak , unfortunately slots were introduced in Sumac, you can see the release notes: Open edX Sumac Release - Product Release Notes — Latest documentation

3

Thank you Sarina for letting me know.

Do you think there’s a simple way to achieve this without slots?

4

I don’t think so. Slots were introduced to make this easy.

5

Upgrading is pretty easy with tutor: Installing Tutor — Tutor documentation

6

I’m not confident enough in any software let alone in Open edX for such migrations to take place without a problem on production. I will try and solve it somehow by mounting the frontend-component-header and modifying it.

Would you happen to know which version of frontend-component-header was released for quince tutuor 17.0.0?

Thank you for your help.

7

looks to me like the frontend-app-learning MFE for Quince installs frontend-component-header 4.6.0

In my opinion though you’d likely be better off upgrading Tutor to latest instead of reinventing the wheel with older version. If you’re scared about breaking production then you might find it worthwhile to set up a test environment on another server to test the upgrade procedures and verify that all works as expected.

If you want to try your hand at modifying it anyway, there some info here that may be helpful: Customising MFEs

For instance, you could install one particular version of the header to the Learning MFE by patching mfe-dockerfile-post-npm-install-learning, and another one to the ORA Grading MFE by patching mfe-dockerfile-post-npm-install-ora-grading:

hooks.Filters.ENV_PATCHES.add_items(
    [
        (
            "mfe-dockerfile-post-npm-install-learning",
            """
    RUN npm install '@edx/frontend-component-header@git+https://github.com/your-repo/frontend-component-header.git#your-branch'
    """
        ),
        (
            "mfe-dockerfile-post-npm-install-ora-grading",
            """
    RUN npm install '@edx/frontend-component-header@git+https://github.com/your-repo/frontend-component-header.git#your-other-branch'
    """
        ),
    ]
)
8

We do already have a test environment, but the reason I refuse to upgrade is that I am more certain than I am frightened something will break. I’ve been in touch with the Edly team and we’re using many features that are now “obsolete” in the newest releases.

The ENV_Patches are very useful, that worked painlessly, thank you.

1 Like