Request: Lock module or extension updates

[celestian]

Has there been any thought to adding a option to "lock" a module (perhaps extension as well) so that it will not be updated during update process? I ask mostly since updating can sometimes cause problems if you're running a module and the content within is updated. At least then they could lock it and if they want to update unlock it to update when they are not concerned it will cause any issues.

I ask because I am updating some of my older conversions to have better maps and I can imagine the havoc it will cause when someone updates and has no idea why his maps are not as expected.

It's not a very important option I admit but it should be low hanging fruit ;)

[LordEntrails]

Won't FG not already updated anything that's in use that has been modified unless the GM does a Revert on it? If it hasn't been modified, would a content update cause problems?

[Zacchaeus]

Won't FG not already updated anything that's in use that has been modified unless the GM does a Revert on it? If it hasn't been modified, would a content update cause problems?
The file in the moduledb looks for the original content that it wants to overwrite. As long as the name is the same it will find it. However in this case we are changing the filename (in most cases from .jpg to webp) and so the original filename no longer exists in the module. Hence the image fails when the user tries to open it.

[LordEntrails]

Ah, I knew I was missing something :)

[celestian]

The file in the moduledb looks for the original content that it wants to overwrite. As long as the name is the same it will find it. However in this case we are changing the filename (in most cases from .jpg to webp) and so the original filename no longer exists in the module. Hence the image fails when the user tries to open it.

Indeed. I've updated some products before like this previously and it did cause some support issues.

I'll be leaving the original but changing the ref-manual links to point to the new maps and linking to the ref-manual pages (not story entries). It should mitigate some of the issues... but I'd still think being able to block updates to certain things would be useful.

[rhagelstrom]

While I understand the request, I could see this being an issue, for extensions at least. Person locks extension from updates, has issues(s), ask for support, back and forth and some head scratching only to find out they have it locked and it's out of date.

[Morenu]

bit of a pain, but could you copy off the mod/ext prior to updating. then update. then replace the updated mod/ext with your copies?

[LordEntrails]

bit of a pain, but could you copy off the mod/ext prior to updating. then update. then replace the updated mod/ext with your copies?
You can. But the average user is not going to know to do this. And I think the intent of the request is to help the average user and reduce support tickets/threads/requests.

I'm not sure even the lock module would be known to the average user. At least not until it's too late and they already updated and have a challenge with their maps. I'd rather see a 'systematic' solution. Even if it were a script someone wrote to update the moduledb files to update the image extension references. But not sure how intelligent that would need to be in order to prevent more 'damage'.

[celestian]

bit of a pain, but could you copy off the mod/ext prior to updating. then update. then replace the updated mod/ext with your copies?

You cannot. At least not the ones that are vaulted and the stuff I am working on is vaulted as are many extensions and any time you load up it's probably going to try and update tho I've not tried.