#651 - Sync with upstream libraries (dependencies) and with API versions (ongoing) – Composr CMS: Your Data, Your Privacy, Your Control

This is a spacer post for a website comment topic. The content this topic relates to: #651 - Sync with upstream libraries (dependencies) and with API versions (ongoing)

By Guest posted 7th Sep 2020, 2:33 PM

This was mostly completed for v11 earlier in the year, and I just finished redoing the Facebook as part of Hybridauth integration.

I have retagged for v12 as we will need to revisit this regularly.

By Guest posted 2nd Jan 2023, 6:19 PM

We won't have time to re-do this for the final v11 release, and the third_party_code test (testSyncDates specificaly) is failing on them needing review again.
For now I put in a 3 year time between reviews so our continuous integration doesn't break down, but this needs reducing back to 1 year.

By Guest posted 4th Aug 2024, 4:19 PM

Historically we have been bad at contributing to upstream projects. We should rectify this and maintain forks as little as possible.

By Guest posted 4th Aug 2024, 6:17 PM

I prefer the plugin route as per my latest updates to MantisBT. Whenever possible, make a Composr plugin for the project to handle all the integrations instead of overwriting the projects' original code and having to maintain it.

There will be a couple of exceptions. For example, MantisBT still doesn't have full compatibility with our needs, so a few files still needed overwriting. And their sponsorship block (widget) is a disaster UI-wise, so I re-did it to conform to the layout of their other blocks (widgets).