This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - Eeems
Pages: 1 ... 57 58 [59] 60 61 ... 370
871
« on: September 29, 2013, 02:17:26 pm »
yay, no more spamming logs! 
Speaking of log spam... Sorunome, go fix all the errors from your stuff. I'll fix up the tool I gave you to allow you to do searching of the logs. EDIT: Done, just run 'apachelog help' to find out it's usage.
872
« on: September 28, 2013, 09:55:44 pm »
That is good to hear. I hope you can fix the latter, though 
I hope so, I've just been unable to figure out where the redirect is happening. I'm going to eventually do a completely rewrite of ourl.ca to allow for an admin panel that can control the rewrites dynamically. EDIT: It seems that it was fixed, my browser just had the old redirect cached.
873
« on: September 28, 2013, 09:48:25 pm »
necro :P
I've recently done some work to clean up ourl.ca's redirects. Now whenever it is used it doesn't fill up our log with 404 errors. I've been unable to track down why it doesn't redirect to omnimaga.org with no arguments though.
874
« on: September 26, 2013, 10:34:09 pm »
Could you write a template as example on how to properly file bug reports? Because I sent 3 reports already and none of them were right  .
First off, select what seems most appropriate for where the bug report is for. Fill out your username and then fill out a description of the bug. Try to keep it to one bug per report, and please don't fill out a massive wall of text explaining the bug/issue. If we need more information we will contact you based on your username.
875
« on: September 26, 2013, 03:02:49 pm »
Hey guys, while the site feedback and questions is great for providing feedback and asking questions about the site. It doesn't work well for reporting errors and getting them fixed. I have a solution however, if you want to make sure your issue is noticed by admins who will then fix it asap, just go to http://ourl.ca/issue and log the problem.
877
« on: September 24, 2013, 12:35:00 pm »
878
« on: September 24, 2013, 09:44:41 am »
You sure are a professional Eeems ^^
EDIT: I also noticed that, even though the switch, when doing quick reply with alt+s it sometimes says pretty long 'loading' up there, sometimes it even says that longer than the new-post-bot notices the new post.
Strange, it's snappier for me then it was before.
879
« on: September 23, 2013, 05:49:33 pm »
It's probably the least rocky because it's being handled by a professional 
880
« on: September 23, 2013, 05:06:22 pm »
I've been at work all day, I haven't had time to look at it yet.
881
« on: September 23, 2013, 05:05:20 pm »
ctrl-z as well
882
« on: September 22, 2013, 08:04:10 pm »
Looks pretty nice
883
« on: September 21, 2013, 09:51:57 pm »
It tries to.
Btw, old search is back since our server seems to be able to handle it.
884
« on: September 21, 2013, 07:34:09 pm »
http://status.ourl.ca/statsgraph.php is still current. I can't quite get the full year for 2012 on cloudflare, but here are the analytics. EDIT: I have no idea what happened to the missing chunk. EDIT2: Oh and btw, I did a bunch of optimization that should help make the site feel faster.
885
« on: September 21, 2013, 01:54:38 pm »
I got redirected to some weird URL (http://www.omnimaga.org/23.82.187.93) for a while but I managed to fix it now. Thanks for all the hard work on the website
As for loading time it seems fine for now (posting via quick reply seems faster), but the true test will be from Monday to Friday from 4 PM to 6 PM GMT-5 and when the search engine is enabled again 
EDIT Attachments work too, so that's good.
Woops, I'll go fix that. That was me trying to get the old server to force you to use the new one. I'll do some testing with the old search engine to see if it will work fine on the new server. Wow! So much cheaper and so much better
The only potential issue I see is what happens when you hit the 2TB cap (if ever  )
Some people attacking the server may force it to hit the 2TB cap 
We use cloudflare to mitigate attacks. It would be really hard for them to do that. Plus I'm sure if I talked to customer support and they realized it was attack we wouldn't be charged for it. Also, the 2TB cap is way better then paying per MB. We still would have had the same issue on AWS. With the new server we only pay per MB after we hit the 2TB limit per month. The old server averaged around 60GB/mo. hm, http://status.omnimaga.org/api.php?req=counts×tamp=1379763623984 (when going on status.omnimaga.org) gives internel server error
it's possible that this wasn't setup yet. It might have moved, but I don't think status.omnimaga.org, axe.omnimaga.org, asmtools.omnimaga.org and the rest were updated yet.
They all were. EDIT: I think I fixed the status subdomain. No idea how I did though
Pages: 1 ... 57 58 [59] 60 61 ... 370
|
Show Posts