Device-specific long URLs option missing in Webclient 4.1.0 #1207
-
shlink-web-client version4.1.0 How do you use shlink-web-clientDocker image Current behaviorIn previous version Expected behaviorWhen using "Advanced Options" Device-specific long URLs should be possible. Minimum steps to reproduce
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Starting with shlink-web-client 4.1.0, the "Device-specific long URLs" section is dynamically displayed/hidden based on the version of the Shlink server you are using. Shlink 4.0.0 replaced the device-specific redirects with the new Dynamic rule-based redirects system, which covers the same functionality, but is more flexible. If you are using Shlink >= 4.0, you now have to go to "Manage redirect rules", in the short URL dropdown, in order to configure redirects based on the device type. |
Beta Was this translation helpful? Give feedback.
-
Thanks for clarifying. With the new implementation, there are now even more options available. The only thing I don't like is that you now have to create a short link first and then modify it afterwards. If you used to work with the advanced options, you now have to perform one more step. Thanks for your help and this great tool! |
Beta Was this translation helpful? Give feedback.
Starting with shlink-web-client 4.1.0, the "Device-specific long URLs" section is dynamically displayed/hidden based on the version of the Shlink server you are using.
Shlink 4.0.0 replaced the device-specific redirects with the new Dynamic rule-based redirects system, which covers the same functionality, but is more flexible.
If you are using Shlink >= 4.0, you now have to go to "Manage redirect rules", in the short URL dropdown, in order to configure redirects based on the device type.