c

I’m on a dedicated server, so I can pretty much do whatever I want. Ill try those out right now.

Thanks. I changed it to 15, didnt seem to fix anything.
I did the memory test and it says this:
Wordfence Memory benchmarking utility version 6.0.15.
This utility tests if your WordPress host respects the maximum memory configured
in their php.ini file, or if they are using other methods to limit your access to memory.

–Starting test–
Current maximum memory configured in php.ini: 200M
Current memory usage: 70.00M
Setting max memory to 90M.
Starting memory benchmark. Seeing an error after this line is not unusual. Read the error carefully
to determine how much memory your host allows. We have requested 90 megabytes.
Completing test after benchmarking up to 80.25 megabytes.
–Test complete.–

Congratulations, your web host allows you to use at least 80.25 megabytes of memory for each PHP process hosting your WordPress site.

I found a problem with that code. It doesn’t seem to apply to single posts. I’m trying to figure out what the single post code might be, but havent been able to figure it out yet.
I tried: #content .single-post a:visited and a bunch of others and it didn’t work. Is it something close to that?

Thanks!
That didnt seem to fix it, so I assume something(shockingly) it wasn’t coded correctly. This is the page:
http://www.freestufftimes.com/free-money/
My CSS for links are:

a {
color:#6d9337;
}
a.active,a.visited,a:active,a:visited {
color:#000!important;
}

Oh and sorry about the confusion, I didnt mean only on the single post page, I meant only within the post content. So it won’t affect links on the menu and sidebar, just within actual post content.

Finally got it to work. I used a couple database optimization plugins(removed over 600 megs of useless data) and it finally went through 🙂

I may have to do that, but its the last thing I really want to do since I have tens of thousands of posts, even more comments, and all that so I can just see so much going wrong with that approach. Still cant find out why its doing this though

Thanks for the great plugin and support!