If you have an email ending in @hotmail.com, @live.com or @outlook.com (or any other Microsoft-related domain), please consider changing it to another email provider; Microsoft decided to instantly block the server's IP, so emails can't be sent to these addresses.
If you use an @yahoo.com email or any related Yahoo services, they have blocked us also due to "user complaints"
-UE
Comments
So your choices again: black-and-white, badly spaced topics, or large title bar/invisible links. I'm gonna do another rotation of these themes now, starting with Light Grunge.
Why is it that like half of the vanillaforums stylesheets make links impossible to notice?
^ That seems like the best idea...
l like it.
If you want to change the font in your browser (for any of the themes), add this as custom CSS for itjustbugsme.vanillaforums.com:
Just replace "Georgia" with the name of any font you like.
…
therefore
no changes will be made.
If you can make a new theme and just don't know how, send the template my way. I can figure something out. ANYTHING but this >.<
EDIT: Yeah, the alignment to the right is what annoys me
Still hard to see.Well, that's a little better.But perhaps the problem is that vanillaforums just doesn't allow custom CSS with free forums. Or something.
I have a forum hosted on Vanilla, and in the dashboard is its front page's HTML. I don't see anything to do with fonts, though, have a look:
{asset name='Head'}
{logo}
{dashboard_link}
{discussions_link}
{activity_link}
{inbox_link}
{profile_link}
{custom_menu}
{signinout_link}
{asset name="Content"}
{asset name="Foot"}
Well it should work if you just put your custom CSS in a
/* ---- Edit CSS ----
If you are unfamiliar with CSS, there are some learning resources in the help
section on the right-hand side of the page.
Here are some things you should know before you begin:
1. Any definitions you enter here will be related to your custom theme. If you
change to a different theme, these definitions will no longer be visible on
this page. If you switch back to your custom theme, your changes will be
present.
2. By default, your custom css definitions will be included *after* the theme
css files. So, your definitions will take precedence over the theme ones.
3. You can choose to not include the theme css files at all, and instead only
include your custom css definitions with the "Revision Options" to the
top-right.
4. We strip comments, invalid code, expressions, @imports, and unsafe or
potentially malicious code from your css before saving it.
5. When you preview your changes, you are the only one who can see the preview.
*/
I imagine this is meant to be blanked and replaced with code that will "bind" itself to the code in place, or something.
I assume that is just an extra stylesheet that gets loaded in addition to the default ones and the selected theme one, so... yeah. Easy.