YukataNinja

Looks like you got this working, let me know if you are still having problems.

I’m not quite sure what is happening on your site. Is the title too long that it is causing a line break and this creates a second line, pushing the buttons down? You could edit the css to set a fixed height for div.rp_post_title or some other div to always have it be 2 lines tall.

Looks like you got this fixed. Let me know if it is still a problem.

Are you putting in the html code like: <img src="\Images\myimage.jpg" \>?

You could put a subtitle in the top of your post, but the tool itself, along with wordpress, does not support subtitles.

Not easily. The source could be edited, in rotating-posts.php, the nav is all contained in <div id=’rp_nav’>. For this to be moved above, the code would need to be refactored as local arrays are populated in the for loop that displays the content.

1. You could use custom css for all the related ID/classes that you want to be removed with display:none, I think just this might do it (untested):

div#rp_nav
{
    display: none;
}

2. In rotating-posts.php, move the if statement block if ($rp_display_title) to below the block with $postContent or wherever you want it. But note if there is a new version released, it will blast over any changes you make to source.

Do you have a link to your site? Did you include the code in your php file or use the shortcode in page/post?

In the next version (1.01), when you uninstall, all of the settings should be deleted.

Next version should fix hopefully this (1.01). Also, if you have ?debug in your url, these will show.

Will do, thanks for pointing this out.

RP is designed to work with the <!--more--> tag in your post to only show part of the post on the front page.

You could create a category for those posts and then assign the posts you want to show up in the plugin by selecting that category in settings -> rotating posts -> Show posts from category.

It works for me on WP Events Calendar 6.6-beta.

Those are there only if it is in debug mode, some other plugin must have set DEBUG to true. Guess I should have used a more local variable.