Seth Carstens

Thank you for your response. I would love to help make the changes / updates from 1.0.2 to 1.1.0 “optional”. The plugin is “built” with AppThemes customers in mind, but I want it to make sense for general wordpress websites.

If you have a specific request on how I can adjust the plugin to work with your site, please give us a link to your site with a specific request of what you would like to change. Also feel free to “contact us directly” at https://sethmatics.com/contact-us/

Fun. I’m not sure if it was something in my setup, or something from the recent update, but this time is stopped resetting my new roles. I’ll keep poking and prodding it to see if I can make it happen again… if not hooray! Cause I was really bummed when it stopped working the first time.

Anyways, I have been taking screen-shots along the way, if I make it happen again I’ll provide more information. Thanks for the reply.

wow, that was quick, thanks wordpress codex for the help! lol.

there was an easy lookup function to make sure it only adds the custom input field. Note that this code will ad “sticky posts” functionality to wordpress until they release a version that supports sticky on custom post types.

function my_sticky_option() {
	global $post;

	//if post is a custom post type and only during the first execution of the action quick_edit_custom_box
	if ($post->post_type == 'custom_post_type' && did_action('quick_edit_custom_box') === 1): ?>

	<fieldset class="inline-edit-col-right">
		<div class="inline-edit-col">
			<label class="alignleft">
				<input type="checkbox" name="sticky" value="sticky" />
				<span class="checkbox-title"><?php _e('Featured Ad (sticky)', 'my_plugin'); ?></span>
			</label>
		</div>
	</fieldset>
<?php
	endif;
}
//add the sticky option to the quick edit area
add_action('quick_edit_custom_box', 'my_sticky_option');

thanks I was also wondering where they went, guessing this is a 3.1 deal?

I also have this issue, why is it removing my get variables when doing a quote “proper 301 redirect”. I’m a bit annoyed by this, may look into coding a fix myself because I otherwise love this plugin.

I remember there is an options page. I don’t remember where i put it though. If I had to guess, it would be in the “users” section. I know for a fact that somewhere, there is an options panel cause that’s where all the user roles are set for each blog.

Yes, until we create an option to “enable x role on all blogs by default” you will have to manually change the users permissions on all the blogs you want them to have access to. I realized this while programming the plug-in, but the fix is rather complex to write and will take a while.

apologies, I’m actually having some issues with cross-domain security issues I’m dealing with on this plug-in. For some reason its having issues keeping authentication when logged in on 2 connected websites.

Basically it goes like this though:
1. Install 2 blogs into the same database with different prefixes.
2. Install and activate the plugin into both blogs.
3. Choose one blog to be the “master”. On this blog you do nothing, but realize its going to hold all your users.
4. On the “child” blog where you want to share your users with the “master” blog, you go into the plugin’s options menu and “choose the master website” from the dropdown menu.

Hopefully if your looking at your sites while following these guidelines it will be enough to get you going.

Right now I’m shooting for September. This project was taken back a bit as I developed a couple of other plugins and learned more about WordPress 3.0 changes.

With wordpress 3.0 finally out, I’ll probably start development on this plugin again. I’ve developed several other plugins now so I’m pretty confident I’ll take care of the bugs in 1 fell swoop in the next update in September.

I added some new options in 1.0.2 what did you think?

https://www.ads-software.com/extend/plugins/sm-sticky-featured-widget/

Yes I apologize but since the coming of wordpress 3.0 I have “put the project ON HOLD”. I will begin to develop the features after all the huge changes and merge of WPMU into WP3.0.

Yes, I just released 1.0.1 today which fixed a nasty bug that was breaking the plugin on some sites. Now that its pretty “bug free” I’ll work on providing you some options, the first one being “Number of Posts” so that you can limit or extend the number of posts away from the default of 5 posts that I have it set at now.

The next release will most likely be next sunday.

I didn’t find on his lines at all
do a “FIND AND REPLACE for all code that says
$_POST['code']

and replace it with
$_POST['regcode']

bump, I also receive this error.