Differences in INI file structure between QGIS versions is not considered

[kannes]

Ref: https://lists.osgeo.org/pipermail/qgis-developer/2023-June/065957.html

Connections can be defined in the INI file in many different ways, e. g.:

[connections]
ows\items\WFS\connections\items\foo\authcfg =
ows\items\wfs\connections\items\foo\dpi-mode = All
ows\items\wfs\connections\items\foo\http-header = @Variant(\0\0\0\b\0\0\0\0)
ows\items\wfs\connections\items\foo\ignore-axis-orientation = false
...
ows\items\wfs\connections\items\foo\version = auto

[qgis]
WFS\foo\authcfg=
...
connections-wfs\foo\dpiMode = All
connections-wfs\foo\ignoreAxisOrientation = false
...
connections\WFS\foo\authcfg =
connections\WFS\foo\password =
connections\WFS\foo\username =

This seems to be due to changes between QGIS versions.

Currently the Profile Manager only looks for "connections-" under "[qgis]".

This affects at least the "Data Sources", but might affect other things from QGIS3.ini too.

[kannes]

The INI file is too much of a mess. It does not make sense to invest too much effort into something that unstable and undocumented...

So my (hopefully reasonable and functional) plan is:

• For each data source type I will catalog all known places where it might be stored, regardless as to why and the usefulness of those settings keys.
• During data source discovery the plugin will simple collect all those occurences and store the sections + keys + values.
• Then we can use that to just transfer the whole bunch to a different profile (ignoring if some keys might be deprecated and unused in newer versions) or to delete all that from the profile.

[kannes]

Got it working pretty well, got into a frenzy of more clean up too though which might take a few evenings.

[kannes]

Since #34 we are using all known locations for source discovery and transfer those 1:1 to the target.

It would be ace to only transfer the needed information for a specific QGIS version instead. That would be a new concept though and potentially lead to lots of headache. The user would need to be able to decide a target QGIS version, not something we can safely discover from a profile afaik.

So I am closing this as "good enough to transfer all kinds of existing sources, in the worst case the target profile is a bit cluttered, but working". If you want to tackle version specific migrations, just shout.