Gehn Signatures

[janaba]

The new Kadish signature is awesome btw ...

[Phantom]

Hi Phantom,

You need to remove the "[ code]" and "[/ code]" tags from your signature.

Tsar

Thank you very much, your advise worked and my signature is up and running. Your a treasure, thank you.

Phantom

[Acorn]

What is the "name" of the new pub sig?

[Tsar Hoikas]

Whoops, I forgot to update the OP. It's gomepub.

[janaba]

Yep, and you just have to right click Doobes' signature and choose 'show graphics info' to get the link of it, which is this ... only the name might not be enough as it has a different number ...

[Acorn]

thanks, both! I've changed to the pub for the MOULa and Cyan forums

[Tsar Hoikas]

The OP has been updated to change URLs to begin with HTTPS, given that the GoW site now uses SSL. I encourage you to update your signatures to the secure version--all you have to do is change "http://" to "https://". What you will notice from not using the HTTPS version is that you will see "broken padlocks" in your browser, indicating the page is insecure. It would be nice to have secure pages on the site

[janaba]

Done ...

I wonder though if pictures linked from other sites like Photobucket etc. would still lead to a display of the grey triangle with an exclamation mark ... However, hi, Adam, great job ...

[Deledrius]

I wonder though if pictures linked from other sites like Photobucket etc. would still lead to a display of the grey triangle with an exclamation mark ... However, hi, Adam, great job ...

Does Photobucket support HTTPS? (Edit: Looks like they do not)

Anything that is not served securely that's embedded on the page will cause that warning. It's just letting you know that some of the content isn't as secure. Most of the time it's not a big deal, but as more things support encryption (finally!) the holes will close up.

[Acorn]

The OP has been updated to change URLs to begin with HTTPS, given that the GoW site now uses SSL. I encourage you to update your signatures to the secure version--all you have to do is change "http://" to "https://". What you will notice from not using the HTTPS version is that you will see "broken padlocks" in your browser, indicating the page is insecure. It would be nice to have secure pages on the site

Thanks, Adam, for the extra security! I've updated the sig I use here but should I/can I do the same for the Cyan and Openuru forums? I assume they don't use SSL, as I don't see the padlock.