Eric Mann

There’s a quick and easy solution to this problem (if you understand PHP).

Step 1:
Add the following lines to your theme’s header.php file immediately below the call to wp_head():
<?php if(is_front_page()) do_action('jdm_head'); ?>

Step 2:
Open the main file for the Featured Content Gallery (content-gallery.php) and edit the following lines at the end of the file:

/* we want to add the above xhtml to the header of our pages: */
add_action('wp_head', 'gallery_styles');
add_action('admin_menu', 'gallery_options_page');

Chance them to:

/* we want to add the above xhtml to the header of our pages: */
add_action('jdm_head', 'gallery_styles');
add_action('admin_menu', 'gallery_options_page');

Assuming the featured content gallery is on the front page of your blog (like it is on mine) this completely solves the conflict problems between the two plug-ins.

You can check out the interaction live on my site. The home page is http://www.jumping-duck.com and the e-commerce store is http://www.jumping-duck.com/store.

Good luck!

@starapple Any time! 🙂

What you want to do is enable “permalinks.” WordPress uses a URL rewriting module to map http://mydomainname.com/category/keep-it-simple to http://mydomainname.com/?cat=4.

Go to the “Settings” menu and select the “Permalinks” sub-menu. Select “Custom Structure” and edit what appears in the text box to be “/%postname%/”

This does two things. First of all, it will give you the permalinks you’re asking about. Secondly, it will change the way your post URLS show up, too. Instead of http://mydomainname.com/?p=102 you’ll see http://mydomainname.com/this-is-my-post-title/

It looks more professional and is much more SEO friendly.

(The “Day and Name” and “Month and Name” settings will give you the same behavior, but they’ll put the post date into post URLS. Category/tag URLs will be the same regardless.)

Sorry for taking so long to get on this. The original code used the wp_redirect() function to send people to the appropriate registration page. Unfortunately, this breaks on many themes and on WP 2.7 in particular.

I am still planning a fully-featured new release sometime soon (including upgraded features, admin menus, and a built-in user permissions manager), but since I can’t set a specific date I’ve created a temporary “fix” for the plugin. In situations where headers have already been sent (the error above), the plugin instead feeds a meta redirect to the page. This isn’t the best way to do things … but it will work for now and will give me time to finish polishing off version 1.0 of the plugin.

Enjoy, and let me know if you run into any more problems!

I’d recommend looking at something like bbPress (http://bbpress.org/). It will give you user forums that are easy to manage (exactly like the forums here on wordpress.org).

At times, Firefox is smart enough to fix errors like that so that you can see the page. If another debugger (IE) is telling you that you’re missing a semicolon, my best recommendation would be to track down that line and see if you really do need one.

Lokust,

If you’re interested in getting something coded special for you, I’d recommend one of three options:

1. Post your request to http://jobs.wordpress.net
2. Post your request to the WP-Pro mailing list
3. Send me an email off the forum (eric [at] eamann [dot] com)

This should be a fairly easy application to set up with shortcodes. I.E. [pluginname level=”author”] Content for Author-level[/pluginname][pluginname level=”contributor”]Content for Contributor-level[/pluginname] etc …

Or something along those lines. Like I said, contact me offline if you want to talk more about it.

As far as using custom fields, I’m not 100% sure how you’d do that. Maybe have one custom field containing content for authors, one for editors, one for subscribers … and then a plugin that applies a filter to your custom fields – displaying only those that match the current user level. I haven’t worked much with custom fields, though, so I’m not sure exactly how it would work.