I don’t think so. This case seems similar to image grids. On that change the warning was shown too, but this was the reply I got back then:
1 Like
You should still be able to disable it via the normal site setting afterwards.
@davidb can you confirm?
Agree this wording in upcoming changes is something we should also figure out a way to make less confusing.
One thing we can try to do is make that clear in the title and description of the change itself, when it’s configurable.
1 Like
The GIFs upcoming change is currently under a hidden site setting but I think going forward we will want to make this visible and can be enabled/disabled within the admin area.
In the meantime just keeping the upcoming change as ‘No one’ and it will be off by default in the future. No need to make any further changes on the admin side.
4 Likes
Yes, when I searched for enable_gifs it took me right to the upcoming changes page. It was very confusing.
The concept of the upcoming changes thing is great. Could just use a language tune up.
Thanks all!
2 Likes
In this case @davidb @mcwumbly , if the change type was site_setting_default instead of feature for enable_gifs, it wouldn’t have shown the scary permanent message. This is controlled here:
However I do think generally the feature type is fine for this upcoming change…so maybe we need to make this permanent notice something more explicit for upcoming changes.
Maybe will_become_permanent: true or something as extra Metadata? Not sure…
1 Like
why were we herded into using klipy instead of other options? i prefer giphy and would like to continue to use it.
the setting and interaction with the component makes this super confusing to use other options like giphy.
I think it’s because Giphy is no longer a free option
it’s fine now. i figured it out (thanks Moin!). i had to uninstall the discourse gif component to make the setting appear. then set the setting to no one, then re-install and re-configure the component. giphy is working again for me.
2 Likes
Glad I was able to help you. The fact that the upcoming change is hidden when the GIF theme component is installed makes this a little confusing: To use the component, you need to uninstall it, disable the upcoming change, and then reinstall it.
Were you notified about the change, or were those notifications suppressed because the upcoming change was hidden? I wonder if that results in the problem of them not knowing that they need to run the migration and get an API key.
1 Like