jeremycherfas

Thanks again Steve. Having taken a look at the complexities of Thesis — which is absolutely brilliantly built — I’m going to pass.

I just do not have the time to delve that deeply into theme building. I’ve got what I need, and I hope I’ve improved things a little for other users of WPFolio. I’ll be sure to add the site to the WPFolio list when it goes live.

Thanks Steve. I’m not really that much of a coder to be joining github. Feel free to use the change, if it helps. It could also be modified to output a DIV specific to every page, which some people might like.

On other sites I use a theme called Thesis, which has a very well developed approach to custom styles, keeping them separate in a Custom folder. That could be a good way to go.

I’ll see how other projects work out and then maybe try and do something similar with WPFolio.

I think I have solved the problem. In the original pages.php of WPFolio, this section seems to have been intended to insert a div class=”Home” on a static home page, if there is one.

<div class="pages">
<div class="<?php wp_title('',true,''); ?>">

It did not work.

I replaced it with a conditional, like this

<div class="pages"> 

<?php if (is_page('home')) {

	echo '<div class="';
	echo the_title('','');
	echo '">'; } 

	else if (is_page("")) {
	echo ''; }
?>

Now it seems to work fine. If the page is the home page, it adds an extra division. If the page is not the home page, it does nothing.

Someone better at PHP than me could probably clean it up further, but as I say, it works for me.

And yes, the static home page, if you want one, needs to be called Home for this to work. But of course you could call it anything, as long as your CSS reflected that.

Jeremy

Thanks Patrick. I had indeed selected a specific page, following the instructions on the WPFolio wiki. That is how I knew that there was no div class of Home being called on the home page.

Does the page literally need to be called “home” all in lower case?

I love the theme, and want to get it just so!

Jeremy

Sorry esmi, but at the moment it is password protected because it isn’t ready for public consumption. Are there some other diagnostics I could give you that might help?

Agreed. It is really badly broken. I reverted to 1.3.2 and all was well.

Another good reason always to have a backup, of plugins too!

Thanks. I had the same problem, deleted the plugin, and everything worked fine.

I’m piggybacking on this to ask whether anyone knows what happened to the CrossRef plugin?

It used to work just beautifully. Then CrossRef removed the search facility from its web site. The original plug-in page has gone, and I’ve seen nothing here or anywhere else about the demise of the plug-in.

It was a really good idea, using the DOI system to generate properly formatted citations. I know one can do this via researchblogging.org, but it would be great to have a plug-in to do it directly from WP.

I’ve no idea how to implement such a thing, but I know I’d use it.

@gulfee
Could you be a bit more specific? where would you put those tags? Outside the [gallery=1] or some other place?

Thanks

Er … so how did you resolve the problem? It would be nice to know, for those of us who may be having similar problems.

Thanks. I had a look at the Wikipedia entry for Remote File Inclusion hack, and I have a slightly better idea of what that means.

Follow up question: is the average WP installation vulnerable to this sort of attack, or can I just ignore it?

I have just discovered this problem on my site, where I was downloading wp-contents before upgrading from 2.3.3 to 2.5.1.

I can see the HTML files in wp-contents, but I do not know how to check the theme for the injections. I will look at the theme files to see if any have changed recently.

Can anyone offer any other advice? One thing I do not seem to be able to find is the correct permissions that should be set for each folder. Is there a list somewhere? I cannot find it.

Mod security did not work for me.

I use ecto on my Mac, which think is available in a Windows version, and it works very well indeed.

write permissions (755 or 777 depending on your server)

This is the first I’ve heard about the write permissions being different depending on the server.

Can you please expand?

Would it make any difference if I had 777 and it should be 755?

Thanks