Ryan Duff

That link should be https://www.website.com/wp-admin/edit.php?post_type=page&paged=2

I’m not convinced this is an IIS issue though. Did you do the normal, switch themes to twenty eleven, disable all plugins, etc?

If you’re filtering the query and not doing it right somewhere you can change the query parameters in admin as well which might explain why you’re getting the wrong link being generated.

Can you pastebin the code? It looks like nowhere in your loop do you have a call to output the post content.

I’m afraid I’m going to have to side with Andrea on this one. There is no attribution requirement for GPL software. As long as the licenses are compatible GPL2/GPL3/etc then you’re literally free to copy and paste and do whatever you want without attribution.

It is common courtesy to attribute someone else’s code, a quick comment like the one that’s included is more than enough to let others know where that code came from.

Perhaps you should read the GPL… I think you’re misunderstanding a few things.

For the most part that looks right, but I do see 1 typo.

On line 5 your have “add_object_page” … that should be options, not object.

add_options_page('Course Dependencies', 'Course Dependencies', 'manage_options','course dependencies', 'course_order');

I’m also assuming that you have it in either your theme’s functions.php file or in a plugin file with a correct plugin header so that you can activate it. If its not in either of those places, the code won’t run.

Nope, password protecting the directory only affects their viewing rights just like any other blog you’d see on the internet. Unless you shared the username and password for your WordPress Admin account they wouldn’t be able to sign in to that part.

This goes over adding menu items. https://codex.www.ads-software.com/Adding_Administration_Menus

I would recommend sticking to the standard options page format if you’re adding a page with some sort of form to the admin side. That’s discussed Here

Best way to do this would to just use your web server’s password protect directory feature. Just create a password protected folder and install WordPress there. Give that password out to friends and family so they can see the blog.

As far as commenting. Leave it on for everyone, no registration required. That way they can comment without needing a password to sign into WordPress itself.

They may be hidden by default in 3.1. You won’t see them in single site or multisite. So uninstalling MU will do nothing.

At best, maybe there’s a plugin hiding them?

Eg. I ran into that issue the other day using WooThemes because I needed to disable WooThemes Dynamic Images so it would revert back to WordPress featured images.

Hope this helps.

Spammers seem to be reverting back to the old fashioned way, or they created a space age machine thats able to comprehend what I wrote, come up with a legitimate comment that relates to the post and even alludes to things I said, and made it seem like a human was typing it.

I’ve been using SK2/BB/Akismet for a while and still get a few occasional spams (1-2/day) that sound like a human typed them due to the context of the comment in relation to the post and has links to spam sites. Most of these IP addresses all seem to lead back to Canada.

Matt has all his feeds at rss.photomatt.net… I’ve been yearning to figure out how he re-wrote this… Its gotta be great for stats, etc because it removes all the rss hits from your normal stats and you can then track them on the subdomain

Yeah, it was posted to the testers list, but no response from Matt at all. I’m not sure if he even saw it. In the thread, its been reported down since January 11th.

https://comox.textdrive.com/pipermail/wp-testers/2006-April/002445.html

NuclearMoose

Over-zealous hype…

Marke1

NuclearMoose, you forgot to protect your plugins dir:

That about speaks for itself…

Did you run upgrade.php? Parts of the sidebar tend to “disapear” until you upgrade the database.

you changed the permissions on the files, but what about the owner and group? If the ownership is not correct, the webserver might not be able to read a file or something along those lines.

I thought WP automagically serialized and unserialized when putting arrays in the database… Including update_option(), get_option(), and add_option()