Difference between revisions of "CWCki:Technical"
SeventhBase (talk | contribs) (→"File extension does not match MIME type.": new section) |
|||
| Line 15: | Line 15: | ||
==Apache Module versus CGI== | ==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. [[User:Sheex|Sheex]] 10:28, 24 August 2010 (PDT) | 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. [[User:Sheex|Sheex]] 10:28, 24 August 2010 (PDT) | ||
== "File extension does not match MIME type." == | |||
I keep getting this message when I try to upload pictures, both in jpg and png format. What's wrong with the interface right now? --[[User:SeventhBase|Seventh]][[User Talk:SeventhBase|Base]] 12:13, 1 September 2010 (PDT) | |||
Revision as of 14:13, 1 September 2010
| 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)
"File extension does not match MIME type."
I keep getting this message when I try to upload pictures, both in jpg and png format. What's wrong with the interface right now? --SeventhBase 12:13, 1 September 2010 (PDT)