User talk:Yasir72.multan

Welcome to Wikimedia Commons, Yasir72.multan!

First steps tutorial Our first steps tour and our frequently asked questions will help you a lot after registration. They explain how to customize the interface (for example the language), how to upload files and our basic licensing policy (Wikimedia Commons only accepts free content). You don't need technical skills in order to contribute here. Be bold when contributing and assume good faith when interacting with others. This is a wiki. Getting help More information is available at the community portal. You may ask questions at the help desk, village pump or on IRC channel #wikimedia-commons (webchat). You can also contact an administrator on their talk page. If you have a specific copyright question, ask at the copyright village pump.

Goodies, tips, and tricks Put Babel boxes on your user page so others know what languages you can speak and indicate your graphic abilities. You can find the files you have uploaded in your Uploads. Please sign your name on Talk pages by typing ~~~~. To link to an image page without embedding the image, type: [[:File:Foo.jpg]], which produces: File:Foo.jpg. You may enable gadgets (custom features) for your account. There are several tools to upload files. Have you edited Wikipedia before? This guide might be useful. Made a mistake? Do you want to have a file renamed or moved? Use the move link and wait for an authorized user to rename it. Do you want to have your recently uploaded picture removed? Tag it as {{speedy|reason here}}. For more information read the deletion guidelines.

-- Wikimedia Commons Welcome (talk) 13:26, 14 October 2013 (UTC)

Please sign your postings

---

Click the "Signature and timestamp"-button to sign your talkpage contributions

As a courtesy to other editors, it is Commons:Signatures policy to sign your posts on talk pages, user talk pages, deletion requests, and noticeboards. To do so, simply add four tildes (~~~~) at the end of your comments. Your user name or IP address (if you are not logged in) and the date will then automatically be added along with a timestamp when you save your comment. Signing your comments helps people to find out who said something and provides them with a link to your user/talk page (for further discussion). Thank you.

--SignBot (talk) 09:01, 11 October 2015 (UTC)

Ok I will take care for it. Thanks - Yasir72.multan (talk) 09:05, 11 October 2015 (UTC)

Sorry about that, my bot currently checks for unsigned messages and did not recognize tables. Should be partially fixed now and you may ignore the bot. --Zhuyifei1999 (talk) 10:22, 11 October 2015 (UTC)

Hmmm. It's Ok Zhuyifei1999. - Yasir72.multan (talk) 12:17, 11 October 2015 (UTC)

File tagging File:Bomanji Square Multan Cantt.jpg

This media was probably deleted.

Thanks for uploading File:Bomanji Square Multan Cantt.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Bomanji Square Multan Cantt.jpg]]) and the above demanded information in your request.

 

Achim (talk) 09:36, 23 January 2016 (UTC)

Ok delete it - Yasir72.multan ^Talk _Contribs
09:41, 23 January 2016 (UTC)

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 5 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 166 character 131: Missing semicolon. - Evidence: acc.innerHTML = "<b>Results not accurate!</b><br>Please check where you made a mistake.<br><b>("+trow.length+"!="+fsmonthcg+"")</b>";
2. ISSUE: line 166 character 131: Expected an identifier and instead saw ')'. - Evidence: acc.innerHTML = "<b>Results not accurate!</b><br>Please check where you made a mistake.<br><b>("+trow.length+"!="+fsmonthcg+"")</b>";
3. ISSUE: line 166 character 133: Unclosed regular expression. - Evidence: acc.innerHTML = "<b>Results not accurate!</b><br>Please check where you made a mistake.<br><b>("+trow.length+"!="+fsmonthcg+"")</b>";
4. ISSUE: line 166 character 133: Unrecoverable syntax error. (80% scanned). - Evidence: undefined

Your CommonsMaintenanceBot (talk) at 10:42, 13 January 2018 (UTC).

File tagging File:Uzma Khan.jpg

This media was probably deleted.

Thanks for uploading File:Uzma Khan.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or ask the author or copyright holder to send an email with copy of a written permission to VRT (permissions-commons@wikimedia.org). You may still be required to go through this procedure even if you are the author yourself; please see Commons:But it's my own work! for more details. After you emailed permission, you may replace the {{No permission since}} tag with {{subst:PP}} on file description page. Alternatively, you may click on "Challenge speedy deletion" below the tag if you wish to provide an argument why evidence of permission is not necessary in this case. Please see this page for more information on how to confirm permission, or if you would like to understand why we ask for permission when uploading work that is not your own, or work which has been previously published (regardless of whether it is your own). The file probably has been deleted. If you sent a permission, try to send it again after 14 days. Do not re-upload. When the VRT-member processes your mail, the file can be undeleted. Additionally you can request undeletion here, providing a link to the File-page on Commons where it was uploaded ([[:File:Uzma Khan.jpg]]) and the above demanded information in your request.

 

 samee  chat  17:43, 14 March 2018 (UTC)

Notification about possible deletion

Some contents have been listed at Commons:Deletion requests so that the community can discuss whether they should be kept or not. We would appreciate it if you could go to voice your opinion about this at their entry. If you created these pages, please note that the fact that they have been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with them, such as a copyright issue. Please see Commons:But it's my own work! for a guide on how to address these issues. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Incnis Mrsi (talk) 10:22, 17 March 2018 (UTC)

Code issues in User:Yasir72.multan/common.css

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new prettyCss issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. WARNING: suggest-relative-unit:px: line 4 char number 17 - Evidence: 3px

Your CommonsMaintenanceBot (talk) at 08:42, 5 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 7 new jshint issues — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 152 character 32: Use '===' to compare with '0'. - Evidence: if(fm_on.length==0) {
2. ISSUE: line 158 character 26: Creating global 'for' variable. Should be 'for (var h ...'. - Evidence: for (h in fm_on_show) {
3. ISSUE: line 223 character 47: Missing semicolon. - Evidence: temp_string += '<b>'+k+'</b> '
4. ISSUE: line 286 character 33: Unreachable 'break' after 'return'. - Evidence: case 0: return '☆☆☆☆☆'; break;
5. ISSUE: line 287 character 33: Unreachable 'break' after 'return'. - Evidence: case 1: return '★☆☆☆☆'; break;
6. ISSUE: line 288 character 33: Unreachable 'break' after 'return'. - Evidence: case 2: return '★★☆☆☆'; break;
7. ISSUE: line 289 character 33: Unreachable 'break' after 'return'. - Evidence: case 3: return '★★★☆☆'; break;
8. ISSUE: line 290 character 33: Unreachable 'break' after 'return'. - Evidence: case 3: return '★★★★☆'; break;
9. ISSUE: line 291 character 31: Missing semicolon. - Evidence: case 5: return '★★★★★' break;
10. ISSUE: line 292 character 34: Unreachable 'break' after 'return'. - Evidence: default: return '☆☆☆☆☆'; break;

Your CommonsMaintenanceBot (talk) at 09:32, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new esprima issue — the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ERROR: Cannot parse line 291 column 26: Unexpected token break

Your CommonsMaintenanceBot (talk) at 09:32, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 150 character 32: Use '===' to compare with '0'. - Evidence: if(fm_on.length==0) {
2. ISSUE: line 156 character 26: Creating global 'for' variable. Should be 'for (var h ...'. - Evidence: for (h in fm_on_show) {
3. ISSUE: line 221 character 47: Missing semicolon. - Evidence: temp_string += '<b>'+k+'</b> '
4. ISSUE: line 283 character 25: Missing semicolon. - Evidence: var sn = parseInt(n)
5. ISSUE: line 284 character 11: Use '===' to compare with '0'. - Evidence: if (sn==0) {

Your CommonsMaintenanceBot (talk) at 09:44, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 67 character 137: Use '===' to compare with '0'. - Evidence: if ((parseInt(fs_stars.text())&&(parseInt(fs_stars.text())>=0&&parseInt(fs_stars.text())<=5))||parseInt(fs_stars.text())==0) {

Your CommonsMaintenanceBot (talk) at 09:58, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 67 character 137: Use '===' to compare with '0'. - Evidence: if ((parseInt(fs_stars.text())&&(parseInt(fs_stars.text())>=0&&parseInt(fs_stars.text())<=5))||parseInt(fs_stars.text())==0) {

Your CommonsMaintenanceBot (talk) at 10:03, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 135 character 45: 'otd_star_avg' used out of scope. - Evidence: $('#otdrating').html('<h3>'+otd_star_avg.toFixed(1)+'★</h3>');

Your CommonsMaintenanceBot (talk) at 10:34, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 103 character 35: Missing semicolon. - Evidence: fs_star_string

Your CommonsMaintenanceBot (talk) at 10:41, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 2 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 106 character 58: Missing semicolon. - Evidence: var fm_star_per = (fm_star_avg/5)*100
2. ISSUE: line 323 character 182: Missing semicolon. - Evidence: return '<div style="border:1px solid #ccc;width:100px;height:6px;overflow:hidden;display:inline-block"><div style="background:#d61515;width:'+percentage+'%"> </div></div>;'

Your CommonsMaintenanceBot (talk) at 11:01, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 3 new jshint issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 149 character 32: Use '===' to compare with '0'. - Evidence: if(fm_on.length==0) {
2. ISSUE: line 155 character 26: Creating global 'for' variable. Should be 'for (var h ...'. - Evidence: for (h in fm_on_show) {
3. ISSUE: line 220 character 47: Missing semicolon. - Evidence: temp_string += '<b>'+k+'</b> '

Your CommonsMaintenanceBot (talk) at 13:52, 12 May 2018 (UTC).

Code issues in User:Yasir72.multan/common.js

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 1 new jshint issue — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. ISSUE: line 150 character 32: Use '===' to compare with '0'. - Evidence: if(fm_on.length==0) {
2. ISSUE: line 156 character 26: Creating global 'for' variable. Should be 'for (var h ...'. - Evidence: for (h in fm_on_show) {
3. ISSUE: line 221 character 47: Missing semicolon. - Evidence: temp_string += '<b>'+k+'</b> '
4. ISSUE: line 302 character 21: 'myLineChart' is already defined. - Evidence: var myLineChart = Chart.Line(line_canvas_total,{
5. ISSUE: line 445 character 22: Missing semicolon. - Evidence: form_string += '<br>'
6. ISSUE: line 446 character 22: Missing semicolon. - Evidence: form_string += '<br>'
7. ISSUE: line 447 character 58: Missing semicolon. - Evidence: form_string += '<input type="hidden" id="potd-image-id">'
8. ISSUE: line 448 character 57: Missing semicolon. - Evidence: form_string += '<input type="hidden" id="potd-caption">'
9. ISSUE: line 510 character 24: 'caption_height' is already defined. - Evidence: var caption_height = caption_padding;
10. ISSUE: line 536 character 15: 'i' is already defined. - Evidence: for (var i=1;i<=lines.length;i++) {

Your CommonsMaintenanceBot (talk) at 10:41, 25 December 2018 (UTC).

Code issues in User:Yasir72.multan/common.css

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 4 new prettyCss issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. WARNING: suggest-relative-unit:px: line 12 char number 10 - Evidence: 1px
2. WARNING: suggest-relative-unit:px: line 13 char number 11 - Evidence: 8px
3. WARNING: suggest-relative-unit:px: line 18 char number 18 - Evidence: 12px
4. WARNING: suggest-relative-unit:px: line 19 char number 18 - Evidence: 12px
5. WARNING: suggest-relative-unit:px: line 39 char number 9 - Evidence: 25px
6. WARNING: suggest-relative-unit:px: line 40 char number 9 - Evidence: 1px

Your CommonsMaintenanceBot (talk) at 14:29, 2 January 2021 (UTC).

Code issues in User:Yasir72.multan/common.css

Hi Yasir72.multan, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

1. You edited User:Yasir72.multan/common.css. Glad to see you coding in css! Have you ever considered becoming a MediaWiki hacker?
2. Though, that change appears to introduce 2 new prettyCss issues — the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in css writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page or cmb-opt-out anywhere on your your global user page on Meta. Good luck at Wikimedia Commons and happy hacking!

1. WARNING: suggest-relative-unit:px: line 31 char number 9 - Evidence: 25px
2. WARNING: suggest-relative-unit:px: line 32 char number 9 - Evidence: 1px

Your CommonsMaintenanceBot (talk) at 17:50, 2 January 2021 (UTC).

Template:UserTalkArchiveBox

Template:UserTalkArchiveBox has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry. If you created this template, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it. Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!

Achim (talk) 22:58, 3 January 2021 (UTC)