Dougal Campbell

Eventually, I will find time to update the plugin. When I do, I will incorporate whatever the latest version of the fancybox jQuery plugin is at that time. Sorry about the lack of updates, but “free time” is something I do not have a lot of, unfortunately. ??

The FacyBox Gallery plugin doesn’t have any settings at this time. It is a “fire-and-forget” plugin. You use it by putting gallery shortcodes in your posts as specified in the instructions, no other settings are needed.

If I can find time to update it, I will probably be adding new features which will also require the addition of a settings screen.

If you’re comfortable editing the plugin code, look around line 288 (in the externimg_backcatalog() function), and you should see a line like:
$pp = get_posts( array( 'numberposts'=>-1 ) );

Change it to read like so:
$pp = get_posts( array( 'post_type' => array('post', 'page'), 'numberposts'=>-1 ) );

I think we need to be able to configure our pancakes: Large, small, and silver-dollar.

Also being able to have a whole stack of pancakes for Multisite would be useful.

Was just able to confirm the fix with the update to 3.3.1. Thanks for taking care of it!

As was already said, your basic building block is going to be good content. Build your site, and put good content on it. Be an expert in your field, and show your expertise through your content. Plugins can help improve SEO a little, but generally speaking, WordPress comes with pretty good SEO out of the box.

You want backlinks? Become part of a community. Find other sites that write about your area of expertise. Write meaningful comments. Invite a popular guest-blogger to write a post for your site. Offer to guest-blog on another site. If there is a Meetup group, business association, club, or other group in your area related to your topic of interest, participate. Do presentations. Speak at conferences. PARTICIPATE. Make yourself visible.

There is no magic SEO bullet. There are a zillion websites where you can read about SEO tips and tricks. None of it will matter if you don’t have something worth offering. And again, WordPress gives you decent SEO from the start. You have the tools in your hands already.

Gah. Sorry about the bad formatting. I guess the forums don’t like code inside a blockquote.

Johanna,

Depending on your theme, you may need to modify several files. In many themes, the first file you want to look at is the index.php template. But in some newer themes (like TwentyTen), the ‘loop’ portion of the code is broken out into separate files, so you might need to look for loop.php or something similar.

Some themes might also have a home.php or a front-page.php, and the archive.php file might be one you’ll want to modify, as well.

And if you’re getting really fancy, just about all of the templates could be modified. For example, you might edit single.php so that single-page ‘asides’ posts are structured very differently from single-page ‘link’ posts.

But generally speaking, ‘index’ and maybe ‘archives’ are probably where you want to start looking. If you compare the code in your theme files to what you see in some of the tutorials on Post Formats, you should see where to make the changes.

Good luck!

+1 on Media Manager improvements and simplification of Taxonomy table structures. I can’t exactly put my finger on what’s wrong with the Medial Manager, but it could definitely stand to be easier and prettier.

Meta-data for everything (taxonomies, media). I’d love to be able to tag my media with keywords, then be able to search on that (in the media manager, as well as front-end searches).

Taxonomies for users.

Generalize URL routing more, and give more control over URLs for things like authors, categories/tags, etc. Yes, resolving conflicts will require some thought and planning. But as long as rules are consistent, it should be fine. Current URL setup should be redone as a set of filterable regexp rules which can be overridden by themes/plugins.

Over time, at least for me, the Links Manager has become less and less important. Turn it into a Core Plugin, convert it to use custom post types, and ditch the old tables.

As mentioned recently on wp-hackers, an intuitive, documented method to bypass the default get_posts that happens in the normal wp initialization.

Clean up default user profile info (hard-coded services like AIM, Yahoo, Jabber/GTalk). These should probably be configurable in the backend somewhere, allowing the admin to create relevant entries? This might be Core Plugin territory.

Also, I’d like some helper functions that make it easier to add buttons to the editors (TinyMCE and Quicktags) for simple things like a ‘code’ HTML tag.

Lastly, I’d like to suggest a push in the Core Plugins area for “API-only” plugins, such as is often seen in the Drupal community. This is pretty developer-centric, but part of the notion behind Core Plugins is supposed to be to keep developers from having to reinvent the wheel over and over. Core Plugins which provide a common basis for other plugins to build upon, without providing much/anything in the way of front-end features make sense. Use-cases include things such as: OAuth; service specific APIs for Twitter, Facebook, Flickr, etc.; advanced hooks for media management…

Too lofty for a 3.2 goal, but eventually, I’d like to see more of the SQL stuff abstracted out to the point that it could be easier to use alternative database engines for some/all of WP core. Yes, it’s possible right now to create your own db.php, but that’s a bit of a sledgehammer, and there’s still some MySQL-specific features/syntax elsewhere in core. Eventually, what if a developer could choose to store user data in MongoDB? Or store posts in Redis?

It’s sometimes hard to see but there is a search box at the very top of all pages, at least in my browser.

Aw, heck. I knew that was there. But since it says “Search www.ads-software.com”, I always assumed it was still the usual site-wide search. But it turns out that when in the forums, it does default to limiting the search to just the forums. My bad, but it illustrates the fact that it’s at least not clear that the search box stays in the forums.

Plus as others have noted, it’s really hard to see. A search box is a very important feature for this site, and needs to stand out better. And a checkbox to limit searching to the currently viewed topic (when applicable) would still be nice, I think.

There should be a Search box on every forum page view for searching the forums. Currently, the only place I see it is on the front page of the forums. Additionally, there should be an easy-to-use option to limit the search to the current topic area.

The composition textarea should be WYSIWYG instead of using quicktags (though a tabbed option for both a la the WordPress post editor would be nice, too).

Perhaps we should create our own in-house “pastebin” service, and make it easy to access when composing a message on the forums.

Oh, and did I mention email notifications? Yeah, I did.

+alot for email notifications, and especially for plugin author topic notifications.

How about a “vote up/down” mechanism for individual responses, so that the best answers float to the top? The ability to vote might need to be predicated by some sort of bozo filters — some minimum prior participation level, double-opt-in email verification, peer approval, etc. What many sites call a “reputation” level.

Plugin authors could probably use some moderator-type abilities within topics related to their plugins: mark as closed/resolved/duplicate.

And while it doesn’t directly impact the usability of the support forums, how about pretty permalinks? When you’ve opened several tabs of forum questions, it would make it easier to keep them straight.

You can also just try re-importing the same file again, and see if it picks up more of the posts. It will automatically skip over the posts that it has previously imported.

We’re having this problem, too (IE6, IE7, IE8), and replacing the p2.js file with the one from SVN doesn’t seem to fix it. Haven’t had a chance to try to track down the source of the problem, myself.

Have you tried version 0.3? Let us know if your issues are fixed.