CUNY Academic Commons

Also, please do not network activate, as the license was for just one blog. Here is the theme homepage: http://themeforest.net/item/king-size-fullscreen-background-wordpress-theme/166299

Thanks so much, Boone. Much appreciated.

OK, the release is live. You can enable the theme for a site at Network Admin > Sites > [your site] > Edit > Themes.

Awesome. Thank you.

Jesus -- here are directions from the theme's backend:

Upload a global background, or specify the image address [ie., http://www.yoursite.com/yourimage.jpg]
Important Reminder: Set the following folder permissions to 777:
/wp-content/themes/kingsize/cache
/wp-content/themes/kingsize/images/upload
/wp-content/uploads

Forgetting this important step will result in images not properly displaying throughout your website.

I'll give it a try without changing folder permissions, but if there are problems, I guess we should just disable this crappy theme. I assume you agree with that.

if there are problems, I guess we should just disable this crappy theme. I assume you agree with that.

Yes, I agree with that, as long as your choice of this particular theme is negotiable.

It sucks, because the theme is very much the style I was looking for, but what other choice do we have?

what other choice do we have?

To change the directory permissions as the message requests. I'm strongly against it, but you're the boss.

Really? You'd let me do something that patently makes the entire project extremely vulnerable to hacks?

These permission settings seem like non-starters, unless it is somehow the case that the more localized folder permissions (wp-content/themes/kingsize/cache &
/wp-content/themes/kingsize/images/upload) wouldn't make the entire site vulnerable . . . .

unless it is somehow the case that the more localized folder permissions (wp-content/themes/kingsize/cache &

/wp-content/themes/kingsize/images/upload) wouldn't make the entire site vulnerable

In an application like WordPress, server security is made up of many small pieces. Making the directories in question world-writable increases the chance of a certain kind of security issue. In truth, the increased chance is probably very, very low. However, my own policy has been not to make any changes of this particular kind for the Commons. This policy is, of necessity, a bit arbitrary, and if you told me that you simply couldn't do your project without using this theme, I could make an exception or modify the policy. I don't want to do this, of course.

Another option is that I could rewrite the portions of the theme that force the 777 requirement. I'd have to do more research to see how viable it is, but my guess is that it'd take a few hours' work, not including any additional time that future upgrades to the theme would take (assuming that we ever actually upgrade these commercial themes).