Difference between revisions of "Scioly.org:Wiki Issues"

From Scioly.org
Jump to: navigation, search
(Reports: Responding to reports.)
m
 
(13 intermediate revisions by 3 users not shown)
Line 86: Line 86:
  
 
{{Report
 
{{Report
|status=open
+
|status=resolved
 
|subject=Tables display on same lines
 
|subject=Tables display on same lines
 
|comment=Separate tables display on the same line when a page is scaled down.
 
|comment=Separate tables display on the same line when a page is scaled down.
Line 93: Line 93:
 
|browser=Safari
 
|browser=Safari
 
|date=2020/08/05
 
|date=2020/08/05
 +
}}
 +
{{Report
 +
|status=response
 +
|comment=This issue appears to have been resolved while addressing other styling issues with tables.
 +
|submitter=bernard
 +
|date=2020/08/06 10:59 PT
 
}}
 
}}
  
  
 
{{Report
 
{{Report
|status=open
+
|status=resolved
 
|subject=Site menu bar does not display username on login button
 
|subject=Site menu bar does not display username on login button
 
|date=2020/08/05
 
|date=2020/08/05
Line 106: Line 112:
 
|submitter=bernard
 
|submitter=bernard
 
|date=2020/08/05
 
|date=2020/08/05
 +
}}
 +
{{Report
 +
|status=response
 +
|comment=This was resolved by adding the navigation in <code>PhpbbAuth.php</code>.
 +
|submitter=bernard
 +
|date=2020/09/03 17:54 PT
 
}}
 
}}
  
Line 260: Line 272:
  
 
{{Report
 
{{Report
|status=progress
+
|status=resolved
 
|subject=DB Error occurs on page deletion
 
|subject=DB Error occurs on page deletion
 
|comment=Attempting to delete a page leads to a <code>Fatal exception of type "Wikimedia\Rdbms\DBQueryError"</code> error.
 
|comment=Attempting to delete a page leads to a <code>Fatal exception of type "Wikimedia\Rdbms\DBQueryError"</code> error.
Line 273: Line 285:
 
|submitter=bernard
 
|submitter=bernard
 
|date=2020/08/06 10:05 PT
 
|date=2020/08/06 10:05 PT
 +
}}
 +
{{Report
 +
|status=response
 +
|comment=This was fixed by reinstalling Extension:GeoData, which suggests that maybe the wrong version of the extension had been previously installed.
 +
|submitter=bernard
 +
|date=2020/09/03 14:32 PT
 
}}
 
}}
  
Line 300: Line 318:
 
|date=2020/08/06 10:16 PT
 
|date=2020/08/06 10:16 PT
 
}}
 
}}
 +
{{Report
 +
|status=resolved
 +
|comment=The problem persists in pages like [[Number of Teams per State]], where the Unicode dagger doesn't display correctly beside the name of states with two Division C bids. This seems to be related to styles specifically for <code>&lt;th&gt;</code> elements. Would it be helpful to remove Avenir entirely, and only use Avenir LT 95 Black for boldface? There may be more pages we have yet to find that have this problem.
 +
|submitter=gz839918
 +
|date=2020/08/12
 +
}}
 +
{{Report
 +
|status=response
 +
|comment=I've changed <code>/src/css/main.css</code> which the Wiki also relies on so that it references <code>/src/fonts/avenir-medium.ttf</code> instead of <code>/src/fonts/avenir-heavy.ttf</code> for font weights 800 and above but below 1000. A side effect is that there is less continuity between font weights, i.e. it is either slightly bold or very heavy, but more characters should appear correctly.
 +
|submitter=bernard
 +
|date=2020/09/03 14:32 PT
 +
}}
 +
 +
 +
{{Report
 +
|status=response
 +
|subject=@media screen Issue
 +
|comment=I noticed in the CSS for <code>#left-navigation</code>, there was a pixel difference between the <code>max-width: 980px</code> and <code>min-width: 982px</code>. Sure enough, this causes the left vector tabs to be positioned incorrectly when the screen width is between 980 and 982px. Changing <code>min-width</code> to 980 should solve the problem.
 +
<pre>
 +
@media screen and (min-width:980px) {
 +
/* ... */
 +
#left-navigation {
 +
  margin-left:11em
 +
}
 +
/* ... */
 +
}</pre>
 +
 +
EDIT: After realizing banners on the wiki break the current nav, <code>#mw-navigation</code> will be redone completely. This <code>@media</code> change will be included in the new nav, so please don't waste your time fixing an already broken nav. :)
 +
|screenshots=[[File:Report_Left_Vector_Issue.JPG|width|200px]]
 +
|browser=Firefox 79.0, Chrome Version 84.0.4147.105
 +
|submitter=Nyda
 +
|date=22:45, 6 August 2020 (UTC)<br>''Updated:'' 21:30, 7 August 2020 (UTC)
 +
}}
 +
 +
 +
{{Report
 +
|status=resolved
 +
|subject=Table fit-content width not working
 +
|comment=<code>fit-content</code> is not a property in Firefox. However, <code>-moz-fit-content</code> does work. For old versions of Edge and IE, <code>width: auto</code> will be used.
 +
<pre>
 +
@media (max-width: 2000px){
 +
    table.wikitable {
 +
        background-color: inherit;
 +
        border: 0;
 +
        display: inline-block;
 +
        max-width: 100%;
 +
        overflow-x: auto;
 +
        /* \/ \/ \/ Add this \/ \/ \/ */
 +
        width: auto; /* If browser is literally older than East */
 +
        width: -webkit-fit-content; /* Earlier versions of Chrome, Opera, and Safari */
 +
        width: -moz-fit-content; /* Firefox */
 +
        width: fit-content; /* Everyone else */
 +
    }
 +
}</pre>
 +
|pages=[[User:Nydauron#Results]]
 +
|browser=Firefox 79.0, Android Firefox 68.11.0, Edge 42.17134.1.0
 +
|submitter=Nyda
 +
|date=22:45, 6 August 2020 (UTC)
 +
}}
 +
{{Report
 +
|status=response
 +
|comment=This change has been made.
 +
|submitter=bernard
 +
|date=2020/09/03 14:32 PT
 +
}}
 +
 +
 +
{{Report
 +
|status=resolved
 +
|subject=Headers not clearing floating elements
 +
|comment=Add <code>clear: both;</code> to <code>.mw-body-content h1, .mw-body-content h2, .mw-body-content h3, .mw-body-content h4, .mw-body-content h5, .mw-body-content h6</code> so that headers clear floating elements preceding them.
 +
|pages=[[User:Jaspattack]]
 +
|submitter=bernard
 +
|date=2020/08/08 17:09 PT
 +
}}
 +
{{Report
 +
|status=resolved
 +
|comment=Change <code>clear: both;</code> to <code>clear: left;</code> so that results tables do not attempt to clear long navboxes. Not a complete fix because the header will separate from the results table on smaller screens but the best we can do for now.
 +
|pages=[[Parkview High School (Missouri)]]
 +
|submitter=bernard
 +
|date=2020/08/09 13:33 PT
 +
}}
 +
{{Report
 +
|status=response
 +
|comment=This change has been made.
 +
|submitter=bernard
 +
|date=2020/09/03 14:32 PT
 +
}}
 +
 +
 +
{{Report
 +
|status=resolved
 +
|subject=Wiki nav restructuring to work with banners.
 +
|comment=Thought this fix was done a while back, but I guess not. This HTML restructuring will make the nav position relative to other sub elements (like the main nav or banners) on the page rather than to the `<body>`. Note that most of the css changes can be found in wiki.css. Note: Commented out CSS lines refer to them being removed. If there are any questions, feel free to PM me or somethin'.
 +
<pre>
 +
========= HTML Format ===========
 +
 +
<div id="wrap-me-up">
 +
  <div id="mw-page-base" class="noprint"></div>
 +
  <div id="mw-head-base" class="noprint"></div>
 +
  <div id="mw-navigation" style="position: relative;">
 +
    ...
 +
  </div>
 +
  <div id="content" class="mw-body" role="main">
 +
    ...
 +
  </div>
 +
  <div id="footer" role="contentinfo">
 +
    ...
 +
  </div>
 +
</div>
 +
 +
========= CSS ===========
 +
/* Please replace any old values with new ones. */
 +
 +
#mw-navigation {
 +
  position: relative;
 +
}
 +
 +
#mw-head {
 +
  margin-top: 0;
 +
  /*position: absolute;*/
 +
  top: -64px;
 +
}
 +
 +
div#mv-head div#p-personal {
 +
  margin-right: 0;
 +
  right: 0;
 +
}
 +
 +
#left-navigation {
 +
  padding-left: 120px;
 +
}
 +
 +
@media screen and (min-width: 980px) /*Issue not been fixed yet, so I'll force u to do it :): was min-width: 982px (now min-width: 980px) */
 +
#left-navigation {
 +
  margin-left: 1.25em;
 +
}
 +
 +
@media (max-width: 980px)
 +
#left-navigation {
 +
  margin-left: 20px;
 +
}
 +
 +
@media (max-width: 900px)
 +
#left-navigation {
 +
  margin-left: 0;
 +
}
 +
 +
@media (max-width: 600px)
 +
#left-navigation {
 +
  margin-left: -120px;
 +
}
 +
 +
div.vectorTabs {
 +
  padding-left: 0;
 +
}
 +
 +
#right-navigation {
 +
  margin-right: 0;
 +
}
 +
 +
@media (max-width: 900px)
 +
#right-navigation {
 +
    /* margin-right: calc(25px - 10px); */
 +
}
 +
 +
#p-search {
 +
  margin-right: 0;
 +
}
 +
 +
@media screen and (min-width: 980px)
 +
#p-search {
 +
    margin-right: 0;
 +
}
 +
 +
#mw-panel {
 +
  margin: 0;
 +
  padding-left: 0;
 +
  padding-top: 0;
 +
}
 +
 +
@media screen and (min-width: 980px)
 +
#mw-panel {
 +
    /* padding-left: 0.5em; */
 +
}
 +
@media (max-width: 900px)
 +
#mw-panel {
 +
    /* padding-left: 25px; */
 +
}</pre>
 +
|browser=Basically every single one, but this was tested on Chrome Version 85.0.4183.83
 +
|submitter=Nyda
 +
|date=23:47, 3 September 2020 (UTC)
 +
}}
 +
 +
{{Report
 +
|status=open
 +
|subject=Using <nowiki>[[page name]]</nowiki> no longer has the same bold effect as <nowiki>'''pagename'''</nowiki>
 +
|comment=The text produced by <nowiki> [[ ]] </nowiki> where the content was the page name previously produced an identical effect to the standard markup for bold font, <nowiki>''' '''</nowiki>, but this is no longer the case.
 +
|pages=Many, including some older team pages. Check the Tournaments of State navboxes at the bottom of state pages for consistent examples.
 +
|submitter=Hugo
 +
|date=16 September 2020
 +
}}
 +
 +
<!-- Please add new reports above this line. -->
 +
'''[https://scioly.org/wiki/index.php?title=Scioly.org:Wiki_Issues&action=edit&section=2 Click here to edit this page.]'''

Latest revision as of 03:53, 17 September 2020

Please use this page for reporting (using the template below) incorrect or unexpected behavior by the Wiki that is likely the result of code and therefore requires the attention of site administrators to repair. Reference Template:Report for parameter descriptions.

{{Report
|status=
|subject=
|comment=
|pages=
|screenshots=
|device=
|operating_system=
|browser=
|submitter=
|date=
}}

Hard Refresh/Clearing Browser Cache

Web browsers store and access website data locally to decrease loading times, so the version of Scioly.org your browser displays may not show our latest updates. Before submitting a report, try hard refreshing the affected page to load its latest version and see if the problem persists. Instructions for hard refreshes or clearing browser caches are listed in the table below for several browsers and operating systems.

Web Browsers Operating Systems
Android iOS/iPadOS macOS Windows
Google Chrome Settings (Chrome) > History > Clear browsing data > Cached images and files > Clear data Shift + Click Reload
OR
Cmd + Shift + R
Ctrl + Click Reload
OR
Ctrl + F5
OR
Ctrl + Shift + R
Internet Explorer Involves clearing cache for ALL apps: Settings > Storage > Internal storage > Cached data > OK N/A Ctrl + Click Reload
OR
Ctrl + F5
Microsoft Edge Settings (Edge) > Privacy > Clear browsing data > Cache > Clear browsing data > Clear
Mozilla Firefox Settings (Firefox) > Data Management > Website Data > Clear all Website Data Shift + Click Reload
OR
Cmd + Shift + R
Ctrl + F5
OR
Ctrl + Shift + R
Safari N/A Settings App > Safari > Clear History and Website Data Shift + Click Refresh
OR
Command + Option + E, then Command + R
N/A

Reports














Click here to edit this page.