PeteHoliday

I just uploaded a new version (0.6.92) of the plugin which I hope will resolve the issues you’re seeing. It should appear on WP Extend relatively shortly.

Please take a look and let me know if you’re still having trouble.

I just uploaded a new version (0.6.92) of the plugin which I hope will resolve the issues you’re seeing. It should appear on WP Extend relatively shortly.

Please take a look and let me know if you’re still having trouble.

I just uploaded a new version (0.6.92) of the plugin which I hope will resolve the issues you’re seeing. It should appear on WP Extend relatively shortly.

Please take a look and let me know if you’re still having trouble.

I was able to set up test blog and reproduce the issue. I’ve just uploaded version 0.6.92 to WP Extend (it should be showing up there relatively soon).

Please check that out and let me know if the issue is still exists with the latest version of the plugin.

Can’t really hep without a lot more information.

What version of WordPress are you running? What version of the plugin?

What plugins besides WP Sentry are you using?

Is FeedKey enabled in the ‘General Options’ tab of the plugin’s settings?

Have the private posts that you’re trying to view been assigned groups? If so, is the user that is trying to view them a member of those groups?

Is this happening for all users or just some of them?

Hi Haddok,
WP Sentry does support pages. Unfortunately, many wordpress functions ignore all private posts/pages, and the function that the jillij theme uses to create the drop-down menu of pages (wp_list_pages) is one of them.

This is a known issue, and I’m looking into ways of making wp_list_pages (and the other internal wp functions) respect and show private posts/pages, but for now about the best option is to use a theme with a sidebar and make use of the page-listing sidebar widget.

I understand that’s not ideal, but it’s the best we have right now while we try to get WP to play nice with its own features. ??

Sorry for the trouble.

Ahh. Yes, your theme is to blame for this one, and it’s not really doing anything that bizarre. It looks like the theme is trying to populate the “Title” attribute of the anchor tag and is choking on the nested HTML. Two possible solutions to that:

First, somewhere you probably have a line like this:

<a href="<?php the_permalink() ?>" rel="bookmark" title="Link to <?php the_title(); ?>"><?php the_title(); ?></a>

This is a bug in the theme. The title attribute should be using, not surprisingly, the_title_attribute(), which strips HTML and encodes quotes.

So something like this, instead:

<a href="<?php the_permalink() ?>" rel="bookmark" title="Link to <?php the_title_attribute(); ?>"><?php the_title(); ?></a>

Let me know if that solves your problem. (This code might appear on any number of pages within your theme)

I don’t really understand what you’re saying it’s displaying.

Either way, I’d guess the issue is the plugin, unless your theme is doing some really bizarre stuff.

Yes. I didn’t think to escape the quotes, apparently. I would guess that if you checked it out, it would be working as expected right now, even though the display in the admin is wonky.

I’ll push an update to fix that issue in the next day or so.

This problem may have been fixed in today’s release of version 0.6.6. Please send me an email if the new version doesn’t resolve your problems.

What version of the plugin?

Apologies, I’m just now noticing this thread — jmash is correct, although this is an issue I would imagine could be resolved one way or another — I hadn’t really anticipated this issue.

One of the options is to disable the sentry-provided widgets, which should solve the problem, although it would mean that pagemash wouldn’t get the private posts, so it might not work quite like you’d want.

Disabling Sentry widgets will be an option in future releases, but for now you can do this manually by commenting out the group of three lines from the register_widgets() function.

Fix has been implemented and uploaded to WP Extend. Thanks!

Thanks for this bug fix, I will take a look this afternoon and push through an update!

It sounds to me like this behavior would get closed in trac because it’s not a bug. ‘If it is decided that your bug isn’t in fact a bug, but is the intended behaviour, it will be closed with invalid.’

What, exactly, is the point of this forum? (This question is mostly rhetorical as I have yet to find a moderator who can provide an even remotely helpful answer)