v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Editing User talk:Lethosor
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 403: | Line 403: | ||
::If regex functions are just parser functions, then wouldn't they still be [[wikipedia:WP:TLIMIT|limited by MediaWiki software]]? This means that a limit will still exist to prevent overloading, just at a much higher cap. I have no knowledge about the other configuration changes though, or if you or someone else had set up the other configs in the past differently that would affect how the templates using regex will work post-upgrade. Is this what you meant by performance? Optionally, if you're still unsure about upgrading, you could raise the limit a little instead. DF2014:Creature token currently exceeds the limit by 51. I think 200-500 is enough to fix things now and later down the line. Most other wikis I've seen that have RegexFunctions still use 1.5.0, so this is probably the better/safer option. I changed my mind about #rreplace and would like for it to remain, however the limitation is still causing issues for the page. The revert did mitigate it somewhat, but [[DF2014:Creature token#NOTHOUGHT|not perfectly]]. – [[User:Doorkeeper|Doorkeeper]] 13:17, 13 December 2021 (UTC) | ::If regex functions are just parser functions, then wouldn't they still be [[wikipedia:WP:TLIMIT|limited by MediaWiki software]]? This means that a limit will still exist to prevent overloading, just at a much higher cap. I have no knowledge about the other configuration changes though, or if you or someone else had set up the other configs in the past differently that would affect how the templates using regex will work post-upgrade. Is this what you meant by performance? Optionally, if you're still unsure about upgrading, you could raise the limit a little instead. DF2014:Creature token currently exceeds the limit by 51. I think 200-500 is enough to fix things now and later down the line. Most other wikis I've seen that have RegexFunctions still use 1.5.0, so this is probably the better/safer option. I changed my mind about #rreplace and would like for it to remain, however the limitation is still causing issues for the page. The revert did mitigate it somewhat, but [[DF2014:Creature token#NOTHOUGHT|not perfectly]]. – [[User:Doorkeeper|Doorkeeper]] 13:17, 13 December 2021 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Unrelated, but I'd like to request for [[mediawikiwiki:Snippets/Horizontal lists|horizontal lists]]. This feature allows for [[wikipedia:MOS:HLIST|single-row styled lists]] using wiki markups in tables, templates, etc. A lot wikis including WP use them. I want to redesign [[Template:Navbox]], and hlists would be very useful. – [[User:Doorkeeper|Doorkeeper]] 13:24, 13 December 2021 (UTC) | Unrelated, but I'd like to request for [[mediawikiwiki:Snippets/Horizontal lists|horizontal lists]]. This feature allows for [[wikipedia:MOS:HLIST|single-row styled lists]] using wiki markups in tables, templates, etc. A lot wikis including WP use them. I want to redesign [[Template:Navbox]], and hlists would be very useful. – [[User:Doorkeeper|Doorkeeper]] 13:24, 13 December 2021 (UTC) | ||
Line 701: | Line 693: | ||
:Sorry, I made a hasty edit and summary and should have clarified. What I meant is that ''only'' tagging an article as "tattered" isn't really what the quality rating system is for, because that doesn't tell the user ''what'' is wrong with the article (is it outdated? incomplete? something else?). I think a combination of marking the article with {{tl|quality|tattered}} and marking the affected information with {{tl|old}} or another appropriate template would help make it more obvious what the problem is. —[[User:Lethosor|<span style="color:#074">Lethosor</span>]] ([[User talk:Lethosor|<span style="color:#092">talk</span>]]) 05:42, 12 March 2023 (UTC) | :Sorry, I made a hasty edit and summary and should have clarified. What I meant is that ''only'' tagging an article as "tattered" isn't really what the quality rating system is for, because that doesn't tell the user ''what'' is wrong with the article (is it outdated? incomplete? something else?). I think a combination of marking the article with {{tl|quality|tattered}} and marking the affected information with {{tl|old}} or another appropriate template would help make it more obvious what the problem is. —[[User:Lethosor|<span style="color:#074">Lethosor</span>]] ([[User talk:Lethosor|<span style="color:#092">talk</span>]]) 05:42, 12 March 2023 (UTC) | ||
::Ahh, that makes a lot of sense, thanks for clarifying. In future, if I am just doing a quick edit like that for rating/improvement notes, that would benefit from elaboration, I'll be sure to leave a comment on the talk page. On a related note, I hadn't properly read the {{tl|Old}} documentation, and thought it was redundant with {{tl|Migrated article}}. So, one final question: In this case, if it looks like the only issues are with recent version changes, would it make sense to ''replace'' <nowiki>{{migrated article}}</nowiki> with <nowiki>{{old}}</nowiki> ( presumably <nowiki>{{old|v=50."xx"}}</nowiki> ), rather than leave both tags? --[[User:Alpacalypse|Alpacalypse]] ([[User talk:Alpacalypse|talk]]) 17:19, 12 March 2023 (UTC) | ::Ahh, that makes a lot of sense, thanks for clarifying. In future, if I am just doing a quick edit like that for rating/improvement notes, that would benefit from elaboration, I'll be sure to leave a comment on the talk page. On a related note, I hadn't properly read the {{tl|Old}} documentation, and thought it was redundant with {{tl|Migrated article}}. So, one final question: In this case, if it looks like the only issues are with recent version changes, would it make sense to ''replace'' <nowiki>{{migrated article}}</nowiki> with <nowiki>{{old}}</nowiki> ( presumably <nowiki>{{old|v=50."xx"}}</nowiki> ), rather than leave both tags? --[[User:Alpacalypse|Alpacalypse]] ([[User talk:Alpacalypse|talk]]) 17:19, 12 March 2023 (UTC) | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |