·
Added a discussion

If I visit the "studio >app store" from a UNA 15 site, are all the modules listed there guaranteed to support the UNA version 15.0 ?

Recently (2 months before ) I purchased Places module. It was listed at " > Studio > app store" from within mysite. So I assumed it is compatible with mysite which was then at version 14.0. But now when I looked at the config file, for version support it says

    'compatible_with' => array(
        '13.x.x'
    ),

Now i am worried if it really supported the previous Una 14.0 version when I purchased it. And now that we are going to 15.0, not sure if it is supported.

But my question is - Should the UNA marketplace by default be filtering out non compatible modules ? Specially since we are installing the modules directly from our UNA site (We click download and then go to downloads section and Install - All within our site). If someone wants an outdated version, they could go to unacms and dowload it. But the modules listed within the App store should at the minimum make sure the module is compatible.

  • 206
Comments
    • Hello, if the module developer is no longer active, you’ll have to update the module to version 15 yourself or ask someone else to do it. In the App Store, there are several older modules available for download that are no longer supported — for example, they might not work with version 14 but still function well with version 13, which is why they remain there. As for modules from the UNA team, those are always up to date, but they probably can’t control or filter the compatibility of modules created by other developers.

      And if it's a module from Jerom(Modzzz), it's no wonder it's not up to date.

      • @PavelS , What you are discussing is for already purchased modules.

        But I am talking about purchasing a module Today from the app store, on a newl UNA 15 site.

        If I have a NEW site with UNA 15, then Studio > App store should only show Modules that are supporting UNA 15.0. Why will it show me outdated modules ? And studio also allow me to install that module in a single button click.

        I can understand older modules being available to download from the store.. But ffrom within the studio, the button to install that module should be disabled. Because this is installing a Incompatible module to a site directly.

        • Hello @highlightings !

          This part in the module means that the "minimal" (oldest) version where the module will work. In your example, the module will not work on UNA 11-12. But for the coming releases the situation depends from the vendors which should check and update their modules if necessary because sometimes it may break the normal work of UNA.

          • Hello @highlightings !
            vendors which should check and update their modules if necessary because sometimes it may break the normal work of UNA.

            If such modules could break a site. Then una should force the vendor to add tags for a major version. And ONLY then should this be available for those websites from the studio.

            Let it be available at your main site where any user can download any version and install at their own risk.

            From studio, these incompatible versions should not be listed. This is a minimum that any app store should have.

            I saw we can add multiple tags to a module.

            • Hello,

              Unfortunately, that's one of the biggest issues we have been facing here with UNA. Many vendors, if not all, UNA third-party devs have quit the platform and we, the users, were just left behind without any support at all. We ended up having outdated modules in our system which are tricky to update. Those are the ones breaking websites.

              • Agree, wholeheartedly. However, as fix/solution for this UNA should amend regulation to permit whoever developer or freelancers on this platform who are willing to fix or upgrade those modules for whoever is still willing to use them with no restrictions provided that the original developer of those modules didn't upgrade them in a timely fashion.

                • It depends on what license the original module was released. If they have any permissible Opensource licenses (MIT, apache etc), then we could edit and distribute. Else, even UNA will get into trouble.

                  • UNA filters the incompatible modules in the Studio->Apps Market. But if the app has been installed in UNA 14 it would be hard to detect what it may do with the UNA 15. That's why we don't advice to upgrade sites till the Alpha and Beta versions - the sites owners and vendors have enough time to test them.

                    • The main issue is that some vendors are no longer available or responsive to UNA forum.

                      Login or Join to comment.