RenaissanceFestival.com Forums

R/F.com Updates => Ask the Admin => Topic started by: Melkar on May 30, 2008, 09:27:08 AM

Title: My Messages possible bug?
Post by: Melkar on May 30, 2008, 09:27:08 AM
It appears that if I send a reply to a message in "My Messages" and check the "save a copy" box it's not actually saving a copy in my outbox (it remains empty). This was using Safari on a Mac. Anyone else see this?

Suggestion note:  In the amber menu bar at the top, it can be somewhat confusing to have "RF Home" and "Home".  I know it's R/F.com homepage vs the Forums home page.  Perhaps changing "Home" to "Forums"  would be more intuitive?

Anyway, neither is a big deal.  I know y'all are figuring out new software and having to basically rebuild the site from the ground up.  That's no small task.
Title: Re: My Messages possible bug?
Post by: willin on May 30, 2008, 09:26:41 PM


none of the messages that i send show up in my "Outbox"
Title: Re: My Messages possible bug?
Post by: Lady Mikayla of Phoenicia on May 30, 2008, 09:31:53 PM
I had trouble trying to "reply" to messages earlier tonight, it would say I had "just posted to the IP board within the last 60 seconds" when I had not.  But when I started a new message it was fyne.
Title: Re: My Messages possible bug?
Post by: renfairephotog on May 30, 2008, 10:00:14 PM
I'm on safari and check the "save a copy" option and it works for me.  I have a few glitches sending  mail but once I restarted safari it's worked.



try going to Personal Message Options and check Save a copy of each Personal Message in my outbox by default.
Title: Re: My Messages possible bug?
Post by: DeadBishop on May 30, 2008, 10:09:51 PM
I haven't had any problems personally.  I'm also on a Mac, using Safari.  For those having issues, it very well could be an issue with the web browser you're using, in conjunction with the site itself.  We'll try to look into this.
Title: Re: My Messages possible bug?
Post by: Melkar on June 01, 2008, 10:07:47 PM
Just a follow-up.  I just tried it with Firefox on the Mac and it worked fine.

I was using an "older" Safari (ver. 3.0.4) and that might also be the reason.  Next time I'll try with Safari 3.1 and see if it "behaves".  :D

Web "standards" gotta luv 'em.  ::)