PressShack

Hi imagefact,

Thanks for reporting that.
Sorry to hear you are having issues. I wasn’t able to reproduce it yet, but I will make more tests. Please, could you check the browser console looking for any JavaScript error or warning?

Thanks

• This reply was modified 7 years, 8 months ago by PressShack. Reason: Fixing a typo

Hi MGitkos,

Awesome, thank you for the kind words.
You are very welcome!

Please, feel free to contact us if you need any help.

Cheers,

You’re welcome, and thanks for helping us catch that Jetpack issue.

Cheers tua33450!

Hi rearley.

Could I ask you to ping us questions via [email protected]? It’s much easier for us to track requests and code over there.

First question … could you email us with the number of tasks you have? We’ll do some testing and try to see what you’re seeing.

Hi tua33450

Could we continue the conversation by asking you to email [email protected], please?

It’s much easier for our team to look at the code and collaborate on a solution for you.

Hi,

I was making a few tests, and it displays on the calendar based on the publishing date. Maybe we have a bug? Please, could you send more information? So I can try to reproduce or debug?

Thanks

Hi tua33450,

A quick update on this: we have this request in our system, and we’ll ping you back as soon as it’s added to the PublishPress core.

Hi tua33450,

Cool! Thank you for the kind words.
We will check what we can do to help you.

Kind regards

Hi,

Cool, I’m glad it worked.

1. Yes
2. I changed it, but I can’t set a hardcoded value again. I refactored the code allowing you customize that priority. You can try using the following package:

https://www.dropbox.com/s/g3km7xx3c4xqnqo/publishpress.zip?dl=0

After installing the alpha package you can set your own value, defining the following constant:

define( 'PP_NOTIFICATION_PRIORITY_STATUS_CHANGE', 10000 );

Please let us know if that works for you.

Thanks

Yes, except it would be better to return true, in case it is not deleting.

/* Change PublicPress notifications trigger */
/* Don't Trigger notification when trashing posts */
add_filter('pp_notification_status_change', 'ppchangetrigger');
function ppchangetrigger($new_status, $old_status, $post, 10,3){
if $new_status === "trash" {
return false;
}
return true;
}

Re the second question, if the notification works when you publish in the back-end, your idea might be correct. If it doesn’t, it is probably a bug and if you confirm, we can help you on that.
Considering it works in the back-end, you need to double check how the plugin you are using to publish from the front-end triggers the publish action.

We hook to this action: transition_post_status
More info: https://codex.www.ads-software.com/Post_Status_Transitions

The priority of our action is 10, but right now it is hard-coded, there is no way to change it without modifying the code (not recommended).

You can try checking if our method is being called when you publish from the front-end:

publishpress/modules/notifications/notifications.php (line 534)

Hi imagefact,

cool! ??

Thank you for the kind words.
You are very welcome!

Please, feel free to contact us if you need any help.

Cheers,

Hi imagefact,

Thank you, You’re very welcome.

We don’t have an option for that right now, but we have 2 filters you can hook:

pp_notification_status_change or pp_notification_{post_type}_status_change

Those filters receive as params: $new_status, $old_status, $post.

If you return false, the notification won’t be sent.

Please, let us know if you need any further help.

Kind regards,

Hi Colbyalbo

Please don’t be rude and leave reviews like this without contacting the developer first.

I see you’ve done the same with other plugins too:
https://www.ads-software.com/support/topic/didnt-work-for-me-89/
https://www.ads-software.com/support/topic/didnt-work-203/

As one of those developers pointed out, the right thing to do is open a support post.

There is also a contact form right inside the plugin where you can contact us. Our email is [email protected].

• This reply was modified 7 years, 9 months ago by PressShack.

Hi KJ,

Cool, we are glad it worked.
Sure thing, we will add that to the documentation.

Good idea. Thanks for the suggestions. Adding to the backlog.

Thank you