Thanks for your patience.
I just got your details via email.OK. So here what's happening on your site. It appears that you've implemented a master FRAME, which makes it so that your entire site is essentially viewed from within an IFRAME tag. There is nothing really "wrong" with doing this, although I personally discourage it.
My personal opinions aside; if you do this, you absolutely MUST match up your domain name across each frame. In other words, if you're going to build a set of frames, each frame MUST reside on the same domain in order to circumvent security protocols enforced by Internet Explorer.
Your site ( a case in point )On your site, your frameset is located on the domain:
www.wearesinai.comHowever, that frameset is calling upon files loaded from:
wearesinai.net ( notice the .net extension, and also the missing the www. prefix ). The reason it's missing the
www. prefix, is that your installation of WordPress® is configured under
Settings -> General without the
www. prefix. So a conflict arises in Internet Explorer, because it considers all cookies set by your WordPress® installation to be
3rd party cookies; resulting in the automatic rejection of every login attempt. Internet Explorer is the most picky browser in this regard. You're also loading a completely different
.net extension into the IFRAME.
So the problem is that you need to load your frameset without the
www. prefix in it ( AND, on the
.net extension ), so that when your installation of WordPress® is loaded, it matches exactly with your main frameset; thereby circumventing Internet Explorer security restrictions, related to
3rd party cookies.
Temporary fix:If you login here with Internet Explorer, it works just fine:
http://wearesinai.net/wp-login.phpHere are some possible long-term solutions for you:Option #1. Change your WordPress® configuration under: Settings -> General
( configure WordPress® to use the
www. prefix for your domain name, on the
.com extension ). This way your main frameset and WordPress installation both match up.
Option #2. Leave your WordPress® configuration "as is", and just force your main frameset to load without the
www. prefix ( on the
.net extension ), so it matches up with your existing installation of WordPress®.
Option #3. You could do away with the frameset all together, and just be sure to use a consistent version of your domain in all links that you produce on-site, via email, etc. Every site owner has to make a decision early-on about whether then intend to use a
www. prefix or not, and whether they intend to use the
.com or
.net version of their domain. So you could just stick with:
http://wearesinai.net/ ( matching your existing configuration ).