FreekBes
commented
9 months ago The campus I'm at doesn't have access to V3 yet which is why it's not supported yet - I have no means to develop and debug for it. V3 will definitely be supported by the extension in the near future.
The missing features from V2 in V3 are not all caused by the extension. I've seen plenty of reports of missing features from 42 staff to the Intra dev team - it's something they will be working on to resolve. If this takes too long, of course with the extension it would be possible to add some features back.
If anyone wants to start contributing, feel free to fork and create a pull request - or share the HTML and CSS files with me (or just the whole profile page saved offline to a ZIP) and I can get started on it too. If it contains private data, you can also share it with me on the 42born2code Slack workspace (@Codam_staff_Freek).
Is your feature request related to a problem? Please describe. Many campuses rolled out Profile V3 or Intra V3 lately, which at least from my testing and understanding is unsupported by this extension. Extension simply tries to authenticate and gets redirected back to profile.intra.fr and none of the features are applied. However, it only affects profile subdomain, other pages seem to be behaving as usual (i.e. dark theme is applied).
Describe the solution you'd like First of all I would like to open a discussion whether this extension can be adopted to support profiles of intra v3 or should it be forked. Furthermore, I am happy to contribute to this project to adapt it to intra v3.
Describe alternatives you've considered A simple alternative would reverting profiles back Intra V2 however this is unsupported currently at my campus. Also, it does not seem like a good long term solution.