stfox38

Hi Allison,
I just went to my infrequently used blog and found the title had been changed to “Hacked By Badi Fuck Ghassen Jebari” .
Everything else seems to have been untouched. When I viewed the source I found that code had been inserted and php bloginfo(‘name’) came out as shown. I suppose that I need to find where that php info is stored and change it, but I’m not sure where that is.
Also, I have no idea if that is all that was done.
I have two other sites on the same hosting site and neither of them was touched. It seemed to be just the WordPress blog.
I hope someone will help us both out.
Good luck

Stephen

Check out The Green Pelican

Made a file “leftsidebar.php” just like “sidebar.php” and added code to “template-functions-general.php” to create function “get_leftsidebar()”

I just cut and paste an existing function block and edit the necessary words like change “get_sidebar()” to “get_leftsidebar().

I hope this helps.

Are you asking how to set up a localhost server on your computer or are you wanting to set up WordPress on a free web hosting site? There is a world of difference.

If you mean like this, it’s done by creating another sidebar in CSS and floating it right. Then, the content must be adjusted by padding. e.g.

.content {padding: 0 20% 0 20%; }

then the right sidebar can be width 20% and it works pretty well.

I hope this will help.

Thanks. I finally got it. There’s a reason for the hyphens in the directory names. The chain is broken if you name a directory green pelican. Well, now that that’s out of the way……..

I have the same problem with trying to validate the W3C CSS on my site. I get this
I know the stylesheet exists and functions on the site. Why can’t W3C (jigsaw) find it?
Any help will be appreciated. I like to validate.

I’ve had a similar experience trying to change the font-family of the posts. I assumed that .storycontent would do the trick, but nothing I entered changed the font. I could change color, etc. but not the font. After much unnecessary troubleshooting I finally got around to checking the css for fonts and discovered the little line:

p, li, feedback {
font: 90%/175% Tahoma, Arial, sans-serif;
}

That little p tag was driving the font declaration for the posts no matter what I declared in the <div> .storycontent .

Once I removed p from that line I had no further trouble declaring the font that I wanted in .storycontent. Voila! Cascading means cascading..