Join GitHub today
[4.0] Show changelog - GSoC Expand Extensions Manager #17536
At this time, users have to look for external sources of information about changes in an extension, when they are going to update their extensions. In most cases, users install an extension without checking the changelog due to the difficulty to find the associated changelog. With this new feature, users can review the changelog of the extensions when they are about to install an update (granted that the changelog is provided by the extension's developer), and after the extension is installed.
Summary of Changes
Added a new parameter on the xml updateserver files 'changelogurl' and adding it to #__updates table.
I made some changes in the core databases so before testing you should fix your database:
Extensions -> Database -> Fix
Install my component: https://github.com/NunoLopes96/component_joomla
If the changelog is not available it will show N/A like in the Folder column
It will open a modal with an iframe of the changelogurl in the body.
The changelogurl is supported for Components, Libraries, Modules, Plugins and Packages, you just need to add tags in your instalation xml with a valid url inside.
To test this you can use these modified packages:
(To test Package, Component, Module, Plugin)
(To test Libraries)
(To test languages)
This happens because it has 1 function to install and another one to update ( they are similar )
(To test templates)
(To test Files)
In Updates View you will have a new column that will show a changelog button to open a modal if there is a changelogurl in the #__updates table.
Documentation Changes Required
Add changelogurl parameter on updatesite information and in extension
I have started to bring this PR inline with the 4.0-dev codebase and work out the issues and improve the featureset.
I am sure @Quy will help me with codestyle :) Now I also need help with styling the modal containing the updates. Have a look at this:
This contains all the possible sections that are available. @ciar4n is this something you can help me with?
As for the
This PR is not ready yet but I would appreciate feedback already so we can get this into a ready state.
I don't think you need the
Additionally I think we only need
@wilsonge The reason the
As an extension developer I use all of them to clearly identify where the entry belongs to. Each has their own merit to me at least. I don't see any harm in offering them, extension developers don't have to use them of course. They are there for those who want to use more distinction.