Page 3 of 3

Re: Old Forum is Really, Really Old...and Broken

Posted: Sun Jul 11, 2010 8:28 pm
by Gonzoron of the FoS
Isabella wrote:There some minor cosmetic trouble with the Imperium skin where the links at the top are half-hidden.
Unable to reproduce. Can you send a screen capture so I can see what you mean?

Re: Old Forum is Really, Really Old...and Broken

Posted: Sun Jul 11, 2010 8:39 pm
by Isabella
Gonzoron of the FoS wrote:Unable to reproduce. Can you send a screen capture so I can see what you mean?
http://i272.photobucket.com/albums/jj19 ... glitch.jpg

It works on my computer, but not on my boyfriend's.

Re: Old Forum is Really, Really Old...and Broken

Posted: Sun Jul 11, 2010 9:53 pm
by Gonzoron of the FoS
Ah... looks like it has to do with the width of the screen. if there's too much text to fit the screen, it wraps around.

Not sure how to fix it. Any html/css/php experts got an idea?

Re: Old Forum is Really, Really Old...and Broken

Posted: Mon Jul 12, 2010 1:05 am
by Nerit
Yeah, this does seem to be a problem with width, as in, his resolution is small! The only reason the wrapping looks bad is because of the image behind. Could be removed, I guess *shrug*.

Mind you, I can keep looking for interesting skins in my spare time, especially fantasy or medieval or antique looking.

Re: Old Forum is Really, Really Old...and Broken

Posted: Tue Jul 27, 2010 6:33 pm
by Gonzoron of the FoS
Isabella wrote:
Gonzoron of the FoS wrote:Unable to reproduce. Can you send a screen capture so I can see what you mean?
http://i272.photobucket.com/albums/jj19 ... glitch.jpg

It works on my computer, but not on my boyfriend's.
I made the background image a bit taller. does that help?

Re: Old Forum is Really, Really Old...and Broken

Posted: Sat Jul 31, 2010 2:51 pm
by NeoTiamat
I'm not sure whether this is an old issue or a new issue, but I tried to swap from my usual ClanofDarkness forum skin to one of the Hermes (since the quotes/spoilers are rather jarring in the default skin), and it pretty much froze my internet.

Re: Old Forum is Really, Really Old...and Broken

Posted: Sat Jul 31, 2010 4:22 pm
by Nerit
That's not normal. Did it switch skins at all?

Re: Old Forum is Really, Really Old...and Broken

Posted: Sat Jul 31, 2010 8:53 pm
by Gonzoron of the FoS
err.... absolutely not normal, and first time I've heard of it. It's possible it's an unrelated issue that just so happened to occur when you switched skins. Couldn't hurt to run standard anti-virus and anti-malware scans. Deeply sorry if it was in fact board related. What's the status now? were you able to switch skins? and re-occurrence of the freeze?

(I'll look into making spoilers and quotes less jarring on the default skin, too)

Re: Old Forum is Really, Really Old...and Broken

Posted: Sun Aug 01, 2010 6:31 pm
by NeoTiamat
I suspect it's an interrelation of my old desktop computer and the Hermes skin. Eventually I just took my laptop (which had no problem) and used it to switch back to the default. I'll run a full sweep tonight, if I remember.

Re: Old Forum _was_ Really, Really Old...and Broken

Posted: Thu Dec 05, 2013 9:47 pm
by HuManBing
I'm getting occasional Google search warnings for FoS forum hits.

This message shows up:
This is probably not the site you are looking for!
You attempted to reach fraternityofshadows.com, but instead you actually reached a server identifying itself as *.bluehost.com. This may be caused by a misconfiguration on the server or by something more serious. An attacker on your network could be trying to get you to visit a fake (and potentially harmful) version of fraternityofshadows.com.
You should not proceed, especially if you have never seen this warning before for this site.
"Not the site you are looking for"?

Hmpf!

I suppose next thing I know, Google will be telling me that I'm free to go about my business and that I should move along.

Re: Old Forum _was_ Really, Really Old...and Broken

Posted: Thu Dec 05, 2013 11:53 pm
by Gonzoron of the FoS
Well, that's kind of weird, but I can assure you that bluehost.com is our hosting service, so it should be safe to proceed. Not sure how I'd go about fixing it.