CWCki:Technical

From CWCki
Jump to: navigation, search


Community Portal
Forum News Policy
Help Technical General

For discussion of errors, extensions, and technical stuff in general(yes we know about the 500 errors).

upgraded to 1.16.0

seems like all the obvious stuff is fixed but if there are any missing extensions you need please let me know --Cogsdev 02:39, 2 August 2010 (PDT)

Audio hosting

Seeing as how some of the audio recordings that we link to on some pages have been removed from their file hosting sites, I was thinking maybe instead of having people download audio we simply host it here CWCiki side. An example of what I am talking about can be found here.[1] CrassCrab 10:14, 3 August 2010 (PDT)

This could be doable, but needs server configuration. From user's point of view, it could be a simple matter of converting the files to Ogg Vorbis and uploading them here. Currently, the upload page doesn't accept .ogg files, and files are limited to 7 MB. In order to make the in-browser support work, we'd need the OggHandler extension (which needs ffmpeg and other leet stuff installed on the server as well). --wwwwolf (wake me when you need me) 03:12, 6 August 2010 (PDT)

Apache Module versus CGI

I've been a long time lurker, but the prevalence of 500 Internal Server Errors has prompted me to register an account. I've lurked and searched the CWCki to see if this has been suggested, but I didn't see anyone bring up this potential solution. So I apologize if I'm offering a redundant suggestion. These error messages seem to suggest to me that the Wiki software is running on CGI. A lot of CGI-related performance issues can be remedied by running PHP via an Apache module, rather than as a CGI binary. The PHP CGI binary is invoked, processes a script, and then shuts down every time a page is requested. Apache modules are continuous, thread safe processes (thread safety can be build dependent). I'm not sure if this hosting provider offers such a configuration option, but it may be worth looking into one that does if this becomes an increasingly prominent issue. FastCGI may be a worthwhile alternative to the current configuration if an Apache module is not an option because of some inherent limitations with Wiki software. Sheex 10:28, 24 August 2010 (PDT)

500 internal server error poll

Please note what page you received it on and what your action was (view/edit/etc...). Clydec 14:25, 5 October 2010 (PDT)

  • Main Page/View - It happens sometimes when I try going here on a new window. --EdtheHedgehog1894 18:14, 5 October 2010 (EST)
  • I almost always get it when saving an edit, sometimes when I log in. Pfargtl9000 Spam & Eggs 17:10, 5 October 2010 (PDT)
  • That's actually been happening to me quite a bit, recently. --EdtheHedgehog1894 21:23, 5 October 2010 (EST)
Extra processing and memory is used while saving a page, and since lack of memory is the likely cause of the error - it's unsurprising that you encounter it when doing the above. Implementing global caching would help alleviate server load, as currently every page request from logged in users is generating server processing. Longer pages have more chance of generating the error - as they are larger, and take up more memory while being processed. --Anonymax 18:30, 5 October 2010 (PDT)
I'll back up the main page and saving edits. I almost never get them otherwise recently. Sometimes I get them if I try to open a page in a tab. The way I browse, I open links I want to read in tabs in tabs to where I can continue reading the page I'm on without having to come back and remember where I was. The tabs will 500 error about 25% of the time. BubblegumPinkButler 14:22, 6 October 2010 (PDT)
  • Got one this morning on the Main page. I didn't do anything in particular other than trying to open it. --ErsatzHouse 12:55, 8 October 2010 (PDT)

Is the CWCki faster now?

Is it? Do you get the 500 internal server error still? Clydec 20:39, 5 October 2010 (PDT)

  • It's better. Though it still takes a little while to load longer pages after editing, and I've only experienced one error message while searching for some video. It's a good start, though. --EdtheHedgehog1894 00:02, 6 October 2010 (EST)
Yes it's very fast when not doing things like editing/saving pages (as to be expected). The changes made should hopefully mean fewer errors for everyone, and it seems like a much faster article-browsing experience too. --Anonymax 21:18, 5 October 2010 (PDT)
  • I still get a lot of 500 Internal Server Errors. Not as many as before but it still happens a noticeable amount. It's as fast as it was before; I don't see any difference. Yossarian 13:26, 6 October 2010 (PDT)
  • I've only gotten one today. Usually I get at least three.--trombonista 21:35, 9 October 2010 (PDT)
    • Okay, today I got bitchslapped by the error when trying to edit that stupid prank call page.--trombonista 21:24, 15 October 2010 (PDT)
  • I only seem to get 500 errors when requesting pages which are not static (i.e. edit pages, recent changes, histories, diffs). The odd 500 error I get when browsing regular articles tends to be on ones that are subject to a lot of recent edits, such as a new video article. --Anonymax 05:52, 13 October 2010 (PDT)

Default Skin

I think we should make Vector the default skin for the CWCki, as MonoBook is pretty dated and Vector gives wikis a very clean appearance. A lot of wikis are adopting Vector for this reason. The layout differences are fairly minor, so it really shouldn't give anyone much trouble by making it the default. Users who really dislike it can still change back to MonoBook in their prefs.

Your thoughts please! --Anonymax 20:11, 19 November 2010 (PST)

Personally I find Monobook more simplistic and nice, as well as more familiar. But we'll see. -- Mexican 21:03, 19 November 2010 (PST)
Vector is clunky and confusing. I prefer Monobook. --BreadGod 21:38, 19 November 2010 (PST)
Monobook is only used by autistics. Vector should be the new default skin.--Inos 22:09, 19 November 2010 (PST)
Vector's kinda pretty! --NerdyNautilus 10:36, 19 November, 2010 (PST)
I could defend either one but they're both shitty white default skins so I honestly don't give a damn. If I had to choose I'd say the one we have now is fine, there's no reason to change it for the sake of changing it. That's how Banjo-Kazooie: Nuts and Bolts raped my childhood. Fuckfuck fuck that noise. I forgot vector moves the searchbar to the top, and it was confusing as fuck when Wikipedia did it. Vector can eat a dick.--Thorgnzorrg 23:45, 19 November 2010 (PST)
The search box movement is about the only major layout change in Vector. There's a reason why Wikipedia changed the default to Vector - it's nicer. --Anonymax 06:34, 20 November 2010 (PST)
Vector is made of AIDS. Monobook works just fine. --Reimu H 05:40, 20 November 2010 (PST)
I don't see how Vector is made of AIDS. Just because something works is not a reason to not consider changing it. While some people clearly prefer MonoBook because it's been the default for so long, I was hoping that people would see that it does give a cleaner appearance to the CWCki and that from the average reader's perspective - it can be more aesthetically pleasing. The design of Vector is more fluid than MonoBook, with less grey and more light colours. The removal of the grey book background is one noticeable change that definitely lightens up articles. With Wikipedia and several other major wikis already using Vector, it should make the CWCki feel more familiar for the average reader. --Anonymax 06:34, 20 November 2010 (PST)
I don't know, it feels like Vector is just using cheap gradient tricks and light blue colors to seem nicer, but really it's actually making everything bigger and less streamlined. I tink the only people who are really going to come to CWCki are nerds of course, and they probably more appreciate the monobook look. -- Mexican 08:36, 20 November 2010 (PST)
Use of gradients is fairly minor, and is done because the skin is not meant to be very heavy. It doesn't really make things bigger - the default size for menu links is indeed larger than MonoBook, but it adds to the clean and clear factor of Vector. The sidebar is about the same width. Vector seems very streamlined to me. I disagree with both the claim that the majority of our visitors are nerds and the claim that they will appreciate monobook more. If they're familiar with Wikipedia, they'd be more likely to appreciate Vector. --Anonymax 08:50, 20 November 2010 (PST)
I say we keep Monobook, the movement of the search bar is the big problem with Vector. At least we're not using Oasis, which is Wikia's new skin. Pfargtl9000 Spam & Eggs 07:14, 20 November 2010 (PST)
There are a number of issues I have with Vector. First of all, raising the search bar makes it so that I have to scroll to the top of even small articles to search, which is a minor irritant, but an irritant nonetheless. Secondly, the breaking up of the "Page/Discussion" and "Edit/View History" makes it more difficult to quickly navigate an article (I use a trackpad, so moving across the screen is not really something I like to do). Thirdly, the "Watch" button is hidden in the little menu next to "View History" - and it's the only thing there. That just bothers me, and besides, when I want to watch a page, I'd like to only have to click once. I suppose the only other two changes that I can see that matter are that 1) the bottom bar is now different (to which I am indifferent, as I never use that bar anyway) and 2) the Donation ad appears to be gone, although that might be easily corrected (and again, I am indifferent). I honestly think what we have appears more professional (looks like a portfolio to me) and is more compact (because it is). To me, Vector/Monobook is like Mac/Windows. Protip: Windows is better. Freecell 07:33, 20 November 2010 (PST)
You know that the little dropdown next to View history should be on-hover and not on-click, so it should still only be one click. The dropdown contains more options if you're an admin. I rarely use the watched pages feature though - so I guess I've never really been worried about where the link is for it. --Anonymax 07:37, 20 November 2010 (PST)

Thing is this isn't a professional & widely-used wiki like Wikipedia. It's a wiki dedicated to doccumenting the trolling of a fat retard from Virginia. Besides, you said we'd be able to change it back to Monobook if the default layout was changed right? Why can't there just be an alternative option to change the layout to Vector for those who want it instead of changing the default layout to Vector? --Thorgnzorrg 07:59, 20 November 2010 (PST)

You can manually configure Vector to be your default skin already. The idea of setting Vector to be our default skin would be to make the CWCki nicer to the majority of users who simply come here as readers, who may not have accounts, and who may be unaware of the fact wikis allow you to change your skin. The vast majority of visitors to CWCki are readers, and I think it would be nicer for them to experience CWCki with Vector. I don't think the subject of this wiki makes either skin a better or worse choice. --Anonymax 08:50, 20 November 2010 (PST)
/shrug. Set up a vote on the Main Page then. --Thorgnzorrg 09:04, 20 November 2010 (PST)
Meh. Personally, I hate Vector, but it'll make the wiki look more pro. Anyone as particular as me about it can just change it ourselves. Enibure 09:34, 20 November 2010 (PST)
I feel that Vector has a "food court" aesthetic that I don't like, plus everybody is used to Monobook already. I support the "keep Monobook, but let people change to vector if they want" motion. Is there a problem with Monobook, or is it just a matter of keeping up with the Joneses? -GrotchManchowder 12:36 PM, 20 November 2010 (EST)
I support the "vote on the Main Page" idea. If you're worried that staying like this will be worse for the average, account-free Joe, just make it say something like "Hey anon faggot come vote here" or some shit. Freecell 09:53, 20 November 2010 (PST)
I don't like how Vector has the search bar at the top right. It's a lot more convenient when it's near the navigation and toolbox windows. Mr3urious 10:11, 20 November 2010 (PST)
Then again, I am getting used to Wikipedia's layout. Mr3urious 10:13, 20 November 2010 (PST)
Everything but not what the Wikipedia is using right now. I hate it even more that these huge-ass "personal appeals" from Jimbo begging for my money that I keep clicking on accidentally. --Sonijew is back 10:22, 20 November 2010 (PST)
I don't really have a preference. Vector has a nice professional feeling to it (but then, none of us are professionals, just bored trolls following the misadventures of an overweight manchild... but that's off-topic), but Monobook has more nostalgic appeal to me. Whatever's best. N. Onymous 10:58, 20 November 2010 (PST)
I vote for vector! PeachyKeen 11:17, 20 November 2010 (PST)
Both are equally good. OrsonZedd 11:54, 20 November 2010 (PST)
Vector is awesome, and I use it in every wiki that supports it, mostly because you don't really need to look for the search box (in some MonoBook sites, its location kind of depends on what the admins have been drinking over the past week). But I don't know if I have any preference either way as to whether it should be made default. People who are logged out can't edit the wiki and people who are logged in can change the preference, so it's hard to start weighing the usability and the skins don't really affect the way the articles look like. No harm going either way. --wwwwolf (wake me when you need me) 11:58, 20 November 2010 (PST)

Vector looks bloated. Like Chris. CrassCrab 12:34, 20 November 2010 (PST)

You make it sound suitable for CWCki then :P Also seems like we have a poll up for voting! --Anonymax 13:27, 20 November 2010 (PST)

Essentially I'm tempted to push for the change to Vector as default anyway. We have to look at this from the perspective of "what is best for new users/readers" rather than what is best for the small number of users who hold accounts and choose to voice their opinions. Overall, Vector is widely accepted as being far better for users than MonoBook is - Wikipedia would not have been as bold as to switch to it if that wasn't the case. Don't forget that if anyone really doesn't like Vector, they can easily switch back to MonoBook in their userprefs. --Anonymax 15:37, 20 November 2010 (PST)

  • Hence the vote, which doesn't require an account. Freecell 15:39, 20 November 2010 (PST)
Doesn't mean that the right people will vote though. For instance, a lot of people enter the CWCki sideways, via search engines to certain pages rather than the main page. --Anonymax 15:50, 20 November 2010 (PST)
The people who look at one article and leave won't even use the search bar. This change appeals to the regs, and the regs will almost definitely check the front page for updates on Chris. I think this gives us as accurate a representation as possible. Freecell 16:00, 20 November 2010 (PST)
The change affects everyone, it will be more noticeable to the regs, but overall it's a change that will improve familiarity and usability for the majority of users. --Anonymax 16:03, 20 November 2010 (PST)
I think a vote is the best way to get the general consensus. If you think it will increase validity by putting the vote on every page, by all means do so. If the vote is meaningless because the sultanism of CWCki deigns it so, take it off the front page. Freecell 16:09, 20 November 2010 (PST)
I didn't come up with the poll idea - but I think it is the wrong way to really determine whether we switch or not. --Anonymax 16:20, 20 November 2010 (PST)
The poll results are certainly surprising to me so far. Perhaps Vector is the way to go after all. -- Mexican 09:27, 21 November 2010 (PST)

Just make it an option in people's settings. IMO, Vector looks retarded. I'd perfer to keep it as it is. Smtp 18:58, 21 November 2010 (PST)

When Vector was introduced in Wikipedia I hated it with a passion, especially for the position of the search box. Now I got used to it, and it does look a tad sleeker than MonoBook. Whatever the poll says. --ErsatzHouse 04:41, 22 November 2010 (PST)

I agree with Smtp. Vector looks like a mess in comparison to Monobook. Also, yeah, just make it an option in the preferences or something. Der Zuschauer 13:39, 22 November 2010 (PST)

It already is an option - but I think it would be better to have Vector be the default and people who really can't handle change can switch back to MonoBook. --Anonymax 14:44, 22 November 2010 (PST)

If its already an option, why are we polling about it or having discussion? Just set it and people that don't like it can just switch it and leave it at that. Smtp 17:05, 22 November 2010 (PST)
To clarify: Logged in users can change their preferences - you can already choose whether you use Vector or MonoBook. People who aren't logged in can't change it (permanently, anyway), and will only see the default skin set by the site admins. So this poll is essentially asking "what skin would you like the random passers-by and perpetual lurkers see?" I guess someone would call this "Decision-making that affects an important demographic" or other crap like that. --wwwwolf (wake me when you need me) 04:43, 24 November 2010 (PST)
  • For my two cents, I like the old one because 1) it doesn't try to look flashy and everything is up there and 2) I fear change. But don't let my opinion sway your opinion, folks.--Champthom 14:28, 23 November 2010 (PST)

I actually think the CWCki needs to be a little more pro in terms of visual style and the overall documentation, plus adjust the feeling of the CWCki, make it more inviting for first timers and people wanting to check out the illustrious CWCki. Granted it's a wiki dedicated to a retarded manchild and his wild exploits, but that doesn't mean we can't make the CWCki look a little more sophisticated and organized. I think streamlining it a litte more will be better in the long run, I think the Vector is more fetching than the current Monobook format. Just something made me like Vector more than Monobook. --Chris Pickles 02:18, 25 November 25th 2010 (EST)

Vector is now the default skin

Following the poll, which included over 500 votes, Vector was the most popular and has been made the default. Don't forget that you really can't handle the change - you can change back to MonoBook in your user prefs. I would hope that you at least give Vector a fair chance before switching back. Any interface changes we make are unlikely to be applied to MonoBook, which may eventually break it. --Anonymax 11:22, 25 November 2010 (PST)

If you ever add new stuff to vector and not monobook let us know. -- Mexican 19:09, 1 December 2010 (PST)
Don't worry too much about the skin compatibility. Many of the CSS tweaks should work on both skins if you put them in MediaWiki:Common.css instead of MediaWiki:Monobook.css or MediaWiki:Vector.css, like how things apparently have been done so far. The skin-specific bits are, uh, supposed to be skin-specific. --wwwwolf (wake me when you need me) 04:28, 2 December 2010 (PST)

Error messages and security

I noticed yesterday (3/15/11) that there was a window of downtime. During this time, PHP error messages were visible. PHP errors should always be disabled during production, because PHP errors can help users with malicious intent to develop an attack footprint on an application. One particular error revealed a class name used in the app, and the location in the filesystem that the script triggering the error existed. Since exploits and vulnerabilities in PHP applications are far from rare, a known exploit in the Wiki software combined with the knowledge the error gave can make it easier for malicious users to choose an attack type that is the most effective.

Check out the following PHP runtime config options:

Although these are php.ini level configuration options, they can be changed during script execution with the use of ini_set(), or even by employing an .htaccess file in the root directory that changes these values. So you don't need php.ini access to apply these security settings.

I know it seems trivial to some, but I felt like this was worth bringing up. Sheex 07:43, 15 March 2011 (PDT)

Problem with the watchlist

When I click on the "Watchlist" option in the top right, it shows the page for a second, then the page goes white. Harryhenry1

I also have this problem. -CWCTime (talk) 15:29, 5 January 2015 (UTC)
Same. --Holdek (talk) 07:10, 13 January 2015 (UTC)

Does anyone have a solution to this problem? I tried logging out and back in again, but the problem is still there. - Harryhenry1 7:44, 5 February 2015 (PST)

Refresh the watchlist page, should be fixed. Canine (talk) 23:12, 4 February 2015 (UTC)

It works now! Thanks! Harryhenry1 (talk) 13:24, 5 February 2015 (PST)
Thanks Canine. --Holdek (talk) 03:47, 6 February 2015 (UTC)

The Cwcville Library

The channel was deleted. Most of the video embeds are broken now, if anyone's listening. EDIT: Never mind, someone listened. —Preceding unsigned comment added by 4thhokage (talkcontribs)

geoip lookup going away

Your wiki is currently using http://www.toolserver.org/~para/geoip.fcgi as geoip lookup service, but this service is going away in the near future. To prevent issues due to non-loading requests, please switch to another service, or disable the use of geoip lookups altogether. Thanks! Valhallasw (talk) 15:24, 18 August 2016 (UTC)

Spam accounts

Should we disable account creation for a week or two in order to stop the flow of spam accounts? FokkerTISM (talk) 02:39, 22 October 2017 (UTC)

CWCipedia archive is down

It appears that the CWCipedia archive has been off-line since the servers were down in July 2019. When I try to access it, I receive the following message:

Warning: session_name(): Cannot change session name when headers already sent in /var/www/html/cwcipedia/includes/Setup.php on line 241
Fatal error: Uncaught TypeError: Argument 1 passed to wfReportException() must be an instance of Exception, instance of Error given, called in /var/www/html/cwcipedia/includes/Exception.php on line 346 and defined in /var/www/html/cwcipedia/includes/Exception.php:281 Stack trace: #0 /var/www/html/cwcipedia/includes/Exception.php(346): wfReportException(Object(Error)) #1 [internal function]: wfExceptionHandler(Object(Error)) #2 {main} thrown in /var/www/html/cwcipedia/includes/Exception.php on line 281

This is reproduced in a webpage capture, confirming the problem is not on my side. Meanwhile, the archived CWCville.com is still functioning. Is this a known issue? ChanOfTartary (talk) 23:30, 25 September 2019 (UTC)

Hello, I believe that the CWCipedia is using an very old version of MediaWiki, which no longer works under the current version of PHP (7.2.10). See also: Talk:CWCipedia#Broken_CWCipedia --Little Owl (talk) 02:25, 26 September 2019 (UTC)

Preserving CWC videos

Several of Chris's videos have been taken down from YouTube for violating the Terms of Service in the past, and re-uploading them is no guarantee that it cannot happen again. I would suggest that we use something like the Internet Archive to preserve CWC content, or even better, store them locally if we have got the space. As the classic videos are mostly 240p, I do not anticipate such being too much of a problem. It is better this than be at Google's mercy. ChanOfTartary (talk) 16:23, 20 December 2019 (UTC)

The best idea would be to store them with this wiki, on a standalone server with the archived CWCipedia and Sonichu sites. In that way it does not have to piggy back on another service, hoping that they will not remove it, causing us to go back to square one. --Little Owl (talk) 17:35, 20 December 2019 (UTC)
IIRC, Marvin has said storing on the wiki can't be done due to bandwidth. His solution was to use torrents - https://kiwifarms.net/threads/damage-control-thecwcvillelibrary-is-down-missing-content-general.15073/ Hurtful Truth Level (talk) 00:02, 21 December 2019 (UTC)