When using a Drupal Installation Profile or a distribution that provides the ImagesLoaded or Masonry libraries, this module is currently unable to find them because it isn't looking for them there. Additionally, the module's requirement check is made right before the files directory is created, so that requirements check fails when installing the module from a profile as well.
If the module is being installed as part of a Profile installation, we should check the profile's libraries directory manually, as the libraries module is not yet configured. We should also skip the file directory check, as that won't yet be set up.
Postponed: needs info
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
No activity here for 5 years. I've just become a maintainer and I'm looking to clean up the issue queue. Can anyone confirm if this issue persists against 2.x as there have been many changes to the module. Thank you!
Setting this to active as it is currently being worked on and no longer postponed.