Jupitercow

Dumb mistakes in that function. Here it is fixed:

/**
 * Change sitemap frequency in XML, default is "monthly"
 *
 * always, hourly, daily, weekly, monthly, yearly, never
 */
add_filter( 'sewn/sitemap/frequency', 'custom_sitemap_frequency', 10, 2 );
function custom_sitemap_frequency( $frequency, $post )
{
	if ( 'unit' == get_post_type($post) ) {
		$frequency = 'daily';
	}
	return $frequency;
}

I don’t get notifications from WordPress forums on new topics which annoys me, so I have to check in to find out there are issues… I am looking at this now. Sorry you had problems. I will see what I can find out and issue a new version if needed.

This is actually built in as a filter:

/**
 * Change sitemap frequency in XML, default is "monthly"
 *
 * always, hourly, daily, weekly, monthly, yearly, never
 */
apply_filters( 'sewn/sitemap/frequency', 'custom_sitemap_frequency' );
function custom_sitemap_frequency( $frequency, $post )
{
	if ( 'news' == get_post_type($post) ) {
		$frequency = 'daily';
	}
	return $frequency;
}

I am not sure what might be happening. That action should trigger when the status changes.

I am curious as to why it is fired in the backend, but not the front end. I will look a bit deeper at how it gets fired.

When you edit in the backend, are you changing the status of the post?

eg: from draft to publish?

And when you edit in Gravity Forms using this plugin, are you also changing the status of the post?

I added this into the latest version. Thanks for highlighting it.

To get it to open in a new page, you would want to set up a page with its own form set up to edit. and then update your edit link to point to that page and send the current post’s id in that link. This is what I need to cover in the new documentation…

Hmmm. It sounds like it isn’t working right for you. I really need to finish updating the documentation… I hope to have some big updates on that this weekend…

It should fill in all the form fields unless something is wrong…

Definitely let me know if you get a chance to try the latest version ( in a test environment obviously! ), and if you are finding the same issues. I want to make sure that the issue you had is addressed.

do_action('gform_update_post/setup_form');
if ( current_user_can('manage_options') ) : // Admin
     gravity_form(1);
elseif ( current_user_can(/*another capability*/) ) : // Next role
     gravity_form(2);
endif;

etc.

The above solution is the one I would use. I am not super interested in creating a method without the nonce. And nonces are time sensitive.

So. I know this is really old. And I am sorry I never finished responding to this. But in case anyone comes across this, I would like to finish this discussion.

First I was able to reproduce what you described, and I understand it.

However, I don’t see any reason to change how it works currently. I think more often than not, users expect post settings that are not actually controlled in the form to see the same when a user edits. I get complaints when things change, because that is unexpected. I have worked to try and maintain things like post status upon edit.

So. The functionality you described is how it works and how it is meant to work. It isn’t going to change.

That said. You are already tapping into the GF hooks to send emails. You have like 75% of the work done for you there. I am not sure how you resolved this, but all you would need to do is is use those hooks to also change the status. That is the way I would recommend for this functionality.

I am not totally sure why you don’t just keep the post in “Pending Review” status though. That also seems like it would solve your problem.

I am not seeing an issue here, but it seems like you have it worked out.

If you make a user an author, they are only able to edit posts they created by default. So that is a start.

I am updating documentation to better illustrate how to use the shortcodes. It can be confusing. I need a richer tutorial on it.

I see this issue. i am hoping to resolve it soon. There is a disconnect in how this data is stored. I am pretty sure it is a simple issue. Something like array vs string. Will update when it is fixed.