Repository navigation
Error when trying to use the Custom Module Manager #80
Description
When trying to open the Custom module manager I get only this errors:
Class "Composer\Semver\VersionParser" not found …/modules_v4/extended_import_export/vendor/jefferson49/webtrees-common/Helpers/GithubService.php:275
#0 …/modules_v4/custom_module_manager/src/ModuleUpdates/GithubModuleUpdate.php(317): Jefferson49\Webtrees\Helpers\GithubService::getRecentReleasesInfo('Jefferson49/Cha...', 'ghp_2NX6IRwW3Eq...')
#1 …/app/Cache.php(58): Jefferson49\Webtrees\Module\CustomModuleManager\ModuleUpdates\GithubModuleUpdate->{closure:Jefferson49\Webtrees\Module\CustomModuleManager\ModuleUpdates\GithubModuleUpdate::fetchReleasesInfoCached():313}()
#2 …/vendor/symfony/cache/LockRegistry.php(113): Fisharebest\Webtrees\Cache::{closure:Fisharebest\Webtrees\Cache::remember():55}(Object(Symfony\Component\Cache\CacheItem), true)
#3 …/vendor/symfony/cache/Traits/ContractsTrait.php(102): Symfony\Component\Cache\LockRegistry::compute(Object(Closure), Object(Symfony\Component\Cache\CacheItem), true, Object(Symfony\Component\Cache\Adapter\FilesystemAdapter), Object(Closure), NULL, 1.0)
#4....
Im the last time I did only some updates of modules, but not this module.
The Admin page of Custom Module Manager works fine.
Activity
Jefferson49 commentedon Oct 5, 2026
Thank you for reporting the issue.
The background is probably that you have both of my modules Custom Module Manager and Extended Import/Export installed. They both use a common library (/vendor/jefferson49/webtrees-common). There is some specific code, which ensures that always the latest common library is used. If Extended Import/Export has a later common library version, Custom Module Manager will use it and you can get errors from /modules_v4/extended_import_export/vendor/jefferson49/webtrees-common/
Can you check if my assumption is true: Are both of the modules installed? Which versions of the two modules are installed?
Jefferson49 commentedon Oct 5, 2026
Recently, there was a conflict in my common library. Therefore, you might need to update both custom modules to the latest module versions:
However, before updating, please check and note down the current versions. It is important for me to understand the error and help other users as well.
ro-la commentedon Oct 5, 2026
Thanks for the informations. When dissabling the module Extended Import/Export (renaming the folder to *.dissable) it works OK. After this the module Extended Import/Export is displayed as "not installed". When clicking on Install the modul is installed and the errors are back.
Where can I see the version number (in files)?
Custom module manager is 2.0.5.
It would nice to have somwhere an information about upgrading a modul using this great module. Either in the "Website logs", or as a column in the module page.
Jefferson49 commentedon Oct 5, 2026
You can find the version here: https://github.com/Jefferson49/ExtendedImportExport/blob/71f4daea9c45f36796721a49934ad7d9d2c1541b/DownloadGedcomWithURL.php#L182
Jefferson49 commentedon Oct 5, 2026
Do you mean some kind of logs? Or can you describe in more detail?
ro-la commentedon Oct 5, 2026
Yes for example an entry with type "update" in the Website logs. I think there was also a discusion on forum/github about the question how can the admin see the history of webtrees updates (but I cannot find it).
Or in the display of the Custom Module Management a new column which would display the timestamp, when the module was installed/updated on my site.
Jefferson49 commentedon Oct 5, 2026
o.k., that sounds like a good feature. I think the website logs would be fine. Columns are more difficult, because the table width is very limited and there will be some additional columns in the next version of Custom Module Managers.
I will put the logs on my list for further developments.
Jefferson49 commentedon Oct 5, 2026
I can reproduce the behavior in my webtrees installation. I will work on a bugfix.
Jefferson49 commentedon Oct 6, 2026
I released a new version 4.3.1 for Extended Import/Export, which should fix the issue.