@Moderators
I think you just might be sadistic as well as evil if you expect us to be satisfied with the new smileys. I mean I’m not religious, but dear god, please change them to the older type. There’s just something about them, they look really effeminate or something, and dare I say it, I’m sure that if they did the rounds on YouTube, people would be inclined to think they were a bit gay.

I’m literally having to force my hand to click on these, just to show you what I mean:

All you need is a mustache added to this one and you could claim campiest set of smileys on the internet:

I just can’t use those smileys, give me a break, I mean even the uber-cool Hoff would have trouble shaking-off any gossip that would surely accumulate if he were to use one of those smileys.

Mentioned this at The Commons but didn’t get a response but I’m very security conscience and concerned about this error message every time I post to the forums. Any suggestions?

Might that be because this is not a https (port 443) but simply a http (port 80) connection?

I get a similar security problem with the Chrome browser. When I visit the logon page, the HTTPS is highlighted in green meaning it’s safe. But as soon as I’ve logged in I get a HTTPS that is orange with a warning. Whatever it is, I think it’s got something to do with DAZ’s certificate. I’m on a totally different browser and OS to Dan, but still something is getting detected as being insecure.

When you log in to this site, the HTTPS protocol is used. This is secure and the stuff sent over the network encrypted. As soon as you get into the forums, the protocol changes to HTTP. Everything sent over the network is as open. There are no certificates needed for HTTPS. It might be that your browser settings are such that you are warned when you leave a secured protocol and continue with an open one. I wouldn’t get excited about that.

If you are in an online store and pass on your credit card number over HTTP, than get worried.

I think you’re right. I just logged in again to check, and indeed the HTTPS disappears and it reverts to standard HTTP from whatever page I click on after the page I got logged into. I forgot all about that, I used to use IE before and can’t even see a setting in Chrome for it.

Anyway, I’m not worried about it, the only time I get concerned is if it turns red with a cross through it.

Just for the records, I’ve just checked with Chrome. Before I log-in, I don’t see the protocol in the address field. Then I log-in and get a green HTTPS protocol indication. After having entered my credentials and hit the button, I lose the HTTPS protocol and get none in the address field. Copying the address field to a simple text editor shows the full URI with the protocol and it is HTTP. By the way, we had this discussion before.

Has anyone noticed that there’s no longer a warning that you already purchased an item, and no easy way to sift thru your order history to check manually? Just these 2 bugs together are a genuine disaster. And that’s just the tip of the iceberg.

Has anyone noticed that there’s no longer a warning that you already purchased an item, and no easy way to sift thru your order history to check manually? Just these 2 bugs together are a genuine disaster. And that’s just the tip of the iceberg.

This was one of the first things that was mentioned, when the store first went live.

@Pam
I forgot to mention this one in my previous post, it’s the worst of the lot —->

@Horo
I don’t know what you mean, peasant, when did that happen?

Anyway, I think I must have something set different in my settings, because that effect you describe where it hides the protocol, is part of the design of Chrome (unless the site uses a security protocol). I’m not getting that though. The page I land on directly after logging in, still shows the HTTPS but has an orange security warning over it.

OK, it’s no big deal, it’s just that if you click Galleries” from the home page you get a different display, but can still see Galleries, well sort of see galleries. not current ones but you can see images.

That one is password protected because they’re still testing it (yes, they atually do test before they go live)