You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our software is currently running H5P 1.26. Someone tried to install the Documentation Tool package and got an error saying that one of the dependencies requires 1.27.
My assumption is that the required version of the Documentation Tool would be set to the minimum of the required versions of the dependencies. Currently it appears to report it requires H5P 1.19. As it is, the Documentation Tool appears in the interface to be installable, until you try to install it. If it required 1.27 instead then it would not be shown, and not be installable, thus avoiding the error message.
I know we can install an older version of the package/dependencies, or we could update our H5P to 1.27. The problem I'm trying to avoid is non-technical users getting the error message.
I don't know what you guys think of this. Is it a problem with this package (and possibly others?) or is it working as intended? If it's working as intended, how should we be handling this situation?
Thanks,
Nathan Lewis - Senior software developer at Totara Learning Solutions
The text was updated successfully, but these errors were encountered:
Hi.
Our software is currently running H5P 1.26. Someone tried to install the Documentation Tool package and got an error saying that one of the dependencies requires 1.27.
My assumption is that the required version of the Documentation Tool would be set to the minimum of the required versions of the dependencies. Currently it appears to report it requires H5P 1.19. As it is, the Documentation Tool appears in the interface to be installable, until you try to install it. If it required 1.27 instead then it would not be shown, and not be installable, thus avoiding the error message.
I know we can install an older version of the package/dependencies, or we could update our H5P to 1.27. The problem I'm trying to avoid is non-technical users getting the error message.
I don't know what you guys think of this. Is it a problem with this package (and possibly others?) or is it working as intended? If it's working as intended, how should we be handling this situation?
Thanks,
Nathan Lewis - Senior software developer at Totara Learning Solutions
The text was updated successfully, but these errors were encountered: