Support

I have already talked to Tassos about this, because it is something that he's doing wrong causing this behaviour.

Back in the Joomla! 1.5 days there were only components, modules, plugins, and templates. If you wanted to create an extension package which consisted of a component, a few modules, and some plugins you had to get, um, “creative”. You'd create a component extension package, put all of the modules and plugins in subfolders, then use some really wacky code in Joomla's post-installation script to install them on the site. The update site would always be on the component. The other extensions did not have an update site of their own.

Core Joomla! developers figured out this is a big problem, so when they released Joomla! 1.6 in 2010 they introduced the package extension type. This extension type is, in fact, a collection of other extensions. When a package extension is installed, all of the other extensions are marked as “belonging” to the package. The package is what has the update site. Therefore, since circa 2013-2014 (when Joomla! 1.5 was already one to two years into end of life) all developers moved to using packages.

Ten years later, Convert Forms – or any other of Tassos' extensions – still uses the ancient use-the-component-as-a-poor-man's-package workaround from the Joomla! 1.5 era. The problem with that is that you get a bunch of “top level” extensions (extensions which do not belong in a package) which do not have an update site. Even worse, updating the component DOES update all of the other extensions which violates the fundamental principle of not catching users by surprise.

I talked to Tassos about this around Easter and he said that he's going to move to package extensions. When he does, you will only see the package extension for Convert Forms. The individual component, module, and plugins will be hidden.

Until he does, sorry, you're stuck with seeing this mess. He is aware this is his fault and he's going to fix it. That's all I could hope for and that's what he's doing.