Bug: Key Modification Failure In GeoPlateforme Plugin

by RICHARD 54 views

Hey guys! 👋 We've got a pretty annoying bug report coming in regarding the GeoPlateforme plugin, specifically with how it handles key modifications. Looks like some of you are experiencing issues when trying to add or remove services associated with a key. Let's dive into the details and see what's happening. This affects the core functionality of the plugin, making it difficult to manage access and permissions, so it's definitely something we want to get sorted ASAP. I'll break down the issue, how to reproduce it, and what versions are affected so you can get a better understanding of the situation.

The Bug: Key Modification Problems

Alright, so the core issue here is that modifying keys in the GeoPlateforme plugin (version 0.13.0) isn't working as expected. You can change the name of the key, no problem. But when you try to add or remove services associated with that key, it just doesn't stick. After saving your changes and going back to check the key, it still has the same permissions as before, like nothing ever happened. Pretty frustrating, right? 😫

This isn't just a visual glitch, either. It's been confirmed that the modifications aren't actually taking place. The user confirmed this with cartes.gouv. They tried the same key modifications directly through cartes.gouv and it worked perfectly. This strongly suggests that the problem lies within the plugin itself. This bug essentially prevents users from updating the permissions of their keys, which is a critical function for managing access to services. Think about it: you can't grant or revoke access to specific services, which severely limits your control over who can use what. This can lead to security risks and usability issues.

This issue is a significant disruption to the intended workflow. When you're managing a system that relies on key-based access control, the ability to add and remove services is absolutely essential. Users rely on being able to make these adjustments as needed, and the failure to do so can have serious consequences. In a nutshell, this bug breaks a crucial part of the plugin's functionality, rendering it less useful for its intended purpose. We want to make sure that we have a smooth and reliable experience for everyone involved.

Steps to Reproduce the Issue

Want to see this bug in action? Here's how you can reproduce the issue:

  1. Create or Select a Key: Start by either creating a new key or choosing an existing one within the GeoPlateforme plugin.
  2. Click 'Modify': Select the key you want to change and click the 'modify' button (or whatever similar function is available in the plugin).
  3. Add/Remove Services: In the modification settings, try to add or remove services associated with the key. This is where you would normally adjust the key's permissions.
  4. Save Your Changes: Make sure you save your modifications. The plugin should confirm that the changes are saved.
  5. Recheck the Key's Services: Go back and view the services associated with the same key. The permissions should have been updated to reflect your changes, but they won't be. The associated services will still be the same as before.

By following these steps, you'll be able to see the key modification failure firsthand. It's a straightforward process that highlights the core problem and makes it easy to understand the nature of the bug. If you're running into this, you can easily verify that the issue is happening on your system. This reproduction process is important for validating and confirming the bug. It also helps the developers to quickly identify and fix the problem.

Affected Versions

Here's what we know about the versions affected by this bug:

  • Plugin Version: 0.13.0
  • QGIS Version: 3.44.1 "legal"

It's important to note that this issue seems to be specific to plugin version 0.13.0. While we don't have information on earlier versions, the provided details point to this specific build. Make sure that when you're testing or encountering this bug, you're using these versions of the plugin. The QGIS version is also specified, providing you with all the details you'll need to replicate the problem. Keeping this information at hand is a key part of working on this bug.

Is Your QGIS Version Supported?

It looks like the user is running a supported QGIS version according to the official roadmap. This is a critical detail because it means that this bug isn't likely due to an incompatibility with an unsupported QGIS release. It makes the troubleshooting process easier. Since both the plugin and QGIS versions are supported, we can narrow down the root cause more efficiently.

Testing with a New Profile

The user tried this bug with a new QGIS profile. This is a great troubleshooting step. It ensures that the issue is not caused by any configuration issues within their current profile. This step helps to ensure that the issue is not caused by any profile-specific configuration. A new profile sets things back to the default and ensures that all the settings are clean. It's an important step to make sure that we can isolate this issue. This helps in focusing on the actual plugin. If the bug still occurs in a new profile, it points directly to a core issue. This process allows us to eliminate a lot of potential causes and focus on the core problem.

Additional Context

There's no additional context provided in this report. This indicates that the provided information provides a clear and concise overview of the issue. Without any extra information, it helps keep the focus on the reported bug and what's currently happening. This makes it easier to work with the existing information and concentrate on what the user has provided.

What's Next?

So, what does all of this mean? Well, the development team needs to investigate this bug, and work to get it fixed. Make sure you report any issues you find. If you have any further insights or specific scenarios where this bug is occurring, it would be super helpful to share those details. The more information we have, the better. By providing detailed steps, version information, and troubleshooting efforts, the user has given the developers a great starting point to tackle this issue. Let's get this fixed and improve the user experience! 👍