ooeygui

WordPress WYSIWYG, gotta love it.

I’ll be looking more into this on the next release. I’ll probably add some kind of “format” checkbox where you can turn off the WYSIWYG or maybe just the auto P tags for a particular reusable because this is really annoying.

Try placing span or div tags around the text and make sure you’re in code view when you click save so the WYSIWYG doesn’t try to change your code.

Originally the plugin was designed this way, but one way or another you’re going to need a unique identifier. Name just isn’t unique. Unfortunately, with the transition over to using custom post types in WP3.0 we don’t have much(if any) control over post titles/names so theoretically you could create two reusables that share the same name, which can be a bigger problem.

I appreciate the input, this has been on my mind after having made that change in the plugin, a controllable “slug” would be what you want. Similar to the url slugs on posts.

One suggestion, if you’re working locally(with or without version control) it might be a good idea to create your reusables out on the production environment and sync the database to your development environment before you start working. That ought to cut down this issue a bit. Also, consider using dynamic sidebars, reusable region widgets, and the [reus] short tag in your theme rather than directly calling the reus() function(ie: Utilize your admin screens as much as possible, that’s really the whole point of the plugin). I made the functions available just in case, but I really don’t recommend using them if you don’t have to. It creates dependencies where your theme MUST have that plugin installed in order to work. This has always been why I like WordPress, for the most part everything works independently, and its just simple. Look at Drupal where everything depends on everything else in order to work, it can be really confusing.

fireproofsocks — Lol, this has been fixed.

Snooze — Try removing the last line of reusables.php. (ie: Get rid of the ?> all together). This almost sounds like the file is somehow being altered with what I’m thinking is a space or some other invalid character after the closing PHP tag.

Let me know if this works so I can update the plugin.

Techism — It might be that you’re using PHP5.3, try switching to 5.2 if you can.

This issue has been patched

Thanks, I’ll take a look at this asap

Got it! ??

function is_active_nav_menu($location){

	if(has_nav_menu($location)){

		$locations = get_nav_menu_locations();
		$menu = wp_get_nav_menu_items($locations[$location]);

		if(!empty($menu)){
			return true;
		}

	}

	return false;

}

Ok so… has_nav_menu() will return true or false based on whether or not a “theme-location” for a menu actually has a menu assigned to it. That gets me partially there, I would like to then find out, if it DOES have a menu associated with it does that menu have items in it?

Is this a reusables admin screen? and do you have full admin access to the WordPress install?

Hmm… when you say you posted a “message” do you mean a post or a reusable? And did you try uninstalling/deactivating the plugin to see if the admin menu comes back? Also, are you using WordPress 3.0 and is it a brand new fresh install of it, or did you upgrade to it?

v3 uses the wp_reus_regions, wp_reus_roles, wp_post_reus, and wp_posts tables. The old wp_reus table isn’t being used anymore since the addition of custom post types in WP3.

I’m not exactly sure why it wouldn’t be working now on your existing install. I was having the exact same problem on my own site and I found that the issue was that only on and upgraded version of WordPress the reusables would save as “future” posts.

Patched… update the plugin, thanks!

Apparently the comments problem is an issue with my theme, they show up in the twentyten theme and my old theme, but as far as I can tell I’m using mostly the same code in my new theme which is odd.

As far as the custom content type — thats just weird, works fine on a fresh install.

Nope, still nothing :/

If you’re really in a pinch, you might want to try a fresh install of WP3 — like I said I’ve been having some similar issues after upgrading but everything appears to work fine on a fresh install.

In the meantime I’ll see if I can work this out.