Windows installation [of 5.2 addons] problem with 6.0.0 and 6.0.1

I am using Windows 11 (23H2) and have been successfully using successive versions of 5.1, then 5.2. I am trying to upgrade to 6.0.0 (and now 6.0.1). Using the same process I have always used, I install with all default values. My installation appears to be successful, but when I open Gramps it does not show the theme I was using in 5.2 (Adwaita/dark). It then asks to install Addons. I select all. The download and install appear to work, except that I get an error indicating ‘The following addons had errors’ and then listing what appears to be all of them. There is no indication of what these errors are.

I note that my Family Trees are visible, but obviously, I can’t go any further.

What could be happening here?

Thanks

Start Gramps AIO from the console and recreate the error then copy the output in console here please.

I think you are trying to load the 5.2 plugins on a 6.0 system.

You will have to download the 6.0 versions using the Addon Manager. (Delete the gramps/gramps60/plugins folder first. You want to start fresh.)

Be certain to double-check the “Projects” tab to make certain that all of them have the 6.0 URLs. (There is another posting with a list of the collections outside of the Gramps-Project.)

For example, the following examples are curated 5.2 addon collection “projects” and, while the addons would download, they could not run on Gramps 6.x:

Although you can resolve this problem, with the correct Project settings. Better warnings and it should not install the wrong target version addons. So a bug report has been filed. (I was certain one had been reported previously. But cannot find it. So re-filed.)

  • 0013789: [Addon Manager] incompatible Addons are listed for installation

Many thanks, Brian (and Gioto). All sorted once I corrected the URL in the Project tab of the Addons manager. It was set to 5.2. Resetting the defaults did that for me. I installed most of the addons, and my dark theme popped back in as soon as I installed the Theme Preferences addon (no surprise, I guess).

Thanks
John

2 Likes