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
One of the most asked question on community.elgg.org both in the group discussions and also in the comments to plugins is: "Does it work with Elgg version XY?"
After the soon to be released Elgg 1.8 this question will be asked again countless times for sure.
Currently, the developers can mention the compatibility in the plugin description or release notes, but it isn't done in most cases unfortunately.
A mandatory field about compatibility of a newly released plugin could help at least in the future. Multiple versions (1.6, 1.7, 1.8) could be offered, maybe even minor releases, but one version must be selected at least for the upload of a plugin to work.
The text was updated successfully, but these errors were encountered:
This feature was made available with the old community site theme: the compatible Elgg version selected at plugin upload was displayed on the download page.
But the new Elgg 1.8 community theme no longer shows this information.
Original ticket http://trac.elgg.org/ticket/2756 on 41003662-04-21 by trac user iionly, assigned to unknown.
Elgg version: 1.8.6
One of the most asked question on community.elgg.org both in the group discussions and also in the comments to plugins is: "Does it work with Elgg version XY?"
After the soon to be released Elgg 1.8 this question will be asked again countless times for sure.
Currently, the developers can mention the compatibility in the plugin description or release notes, but it isn't done in most cases unfortunately.
A mandatory field about compatibility of a newly released plugin could help at least in the future. Multiple versions (1.6, 1.7, 1.8) could be offered, maybe even minor releases, but one version must be selected at least for the upload of a plugin to work.
The text was updated successfully, but these errors were encountered: