HRWiki talk:Upgrade to MediaWiki 1.6
From Homestar Runner Wiki
(Difference between revisions)
(→JS & CSS) |
(→JS & CSS) |
||
Line 26: | Line 26: | ||
::::Still doesn't look right until I purge the cache. What's up with that? —{{User:X-Spider2/X-Sigger2}} 09:58, 24 June 2006 (UTC) | ::::Still doesn't look right until I purge the cache. What's up with that? —{{User:X-Spider2/X-Sigger2}} 09:58, 24 June 2006 (UTC) | ||
+ | |||
+ | :::::To be more specific: when you edit your custom CSS/JS page, right after editing it, it's parsed as a normal wiki page, rather than being put in a <code><pre></code> block. <code>action=purge</code> is needed to make it look correct. I think I read somewhere that when you save a page it's parsed and put in the cache, and that it's seperate to the parser that usually runs when you view a page... perhaps there's something there that can be looked at. Incidentally, I have the same problem on my test wiki, which is a clean 1.6 install. {{User:Phlip/sig}} 13:29, 24 June 2006 (UTC) |
Revision as of 13:29, 24 June 2006
Contents |
To-do list
- Add drop-down menu on Special:Upload with list of personal-image templates.
Open issues
RC patrol
Could we get recent changes patrolling turned back on? — User:ACupOfCoffee@ 17:39, 21 June 2006 (UTC)
- That's already "on". Maybe you should try again. — Lapper (talk) 17:41, 21 June 2006 (UTC)
- Nope, nothing. Then again I can't use it at another wiki that recently upgraded to 1.6 either. Can't use it in IE7 either. — User:ACupOfCoffee@ 18:25, 21 June 2006 (UTC)
- Well, whattaya know. The "patrol" permission wasn't automatically given to the user group as of this version. Enable'd! — It's dot com 20:19, 21 June 2006 (UTC)
- Saints be praised! The exclamation marks are alive! — User:ACupOfCoffee@ 02:56, 22 June 2006 (UTC)
- Well, whattaya know. The "patrol" permission wasn't automatically given to the user group as of this version. Enable'd! — It's dot com 20:19, 21 June 2006 (UTC)
- Nope, nothing. Then again I can't use it at another wiki that recently upgraded to 1.6 either. Can't use it in IE7 either. — User:ACupOfCoffee@ 18:25, 21 June 2006 (UTC)
Copyright tags
Copyright tags as well [as personal-image tags on Special:Upload]? — User:ACupOfCoffee@ 17:35, 21 June 2006 (UTC)
- Those are already there. Do you see them? — It's dot com 17:56, 21 June 2006 (UTC)
- After a hard refresh, I now see them. — User:ACupOfCoffee@ 18:07, 21 June 2006 (UTC)
JS & CSS
After their first edit since the upgrade, monobook files don't look quite as they did before the upgrade. (How the files affect style and all that hasn't changed, it's what the files look like when you visit them that's a problem.) If you don't understand, look at my files. —Y2K () 07:56, 22 June 2006 (UTC)
- If you refer to the text at the top, this is due to a modification that It's dot com made to MediaWiki:Clearyourcache, found in your preferences and at the top of your Monobook CSS and Monobook JS pages. — Lapper (talk) 14:31, 22 June 2006 (UTC)
- Looks normal to me. If it's something other than what Lapper said, then could you be a little more specific? — It's dot com 17:44, 22 June 2006 (UTC)
- Sorry, just had to purge my cache. —Y2K (
) 06:03, 23 June 2006 (UTC)
- Sorry, just had to purge my cache. —Y2K (
- Still doesn't look right until I purge the cache. What's up with that? —Y2K (
) 09:58, 24 June 2006 (UTC)
- Still doesn't look right until I purge the cache. What's up with that? —Y2K (
- To be more specific: when you edit your custom CSS/JS page, right after editing it, it's parsed as a normal wiki page, rather than being put in a
<pre>
block.action=purge
is needed to make it look correct. I think I read somewhere that when you save a page it's parsed and put in the cache, and that it's seperate to the parser that usually runs when you view a page... perhaps there's something there that can be looked at. Incidentally, I have the same problem on my test wiki, which is a clean 1.6 install. --phlip TC 13:29, 24 June 2006 (UTC)
- To be more specific: when you edit your custom CSS/JS page, right after editing it, it's parsed as a normal wiki page, rather than being put in a