pugwonk

Hi Animesh – thanks for looking into this! That URL shows the same picture if you retrieve it from both a Seattle-based VPN and a New York-based VPN? I just tried it again now and got two different pictures from the two different physical locations.

Thank you! I’ve submitted a PR on that repo.

A quick way to narrow down where this is coming from is to open up wp-includes\functions.php and temporarily add a stack dump above where this error is generated. To display a stack dump, you can use:

debug_print_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);

And a good place to insert it in functions.php is just above the line number that gets quoted in the error:

* @param bool $trigger Whether to trigger the error for deprecated functions. Default true.
	 */
	if ( WP_DEBUG && apply_filters( 'deprecated_function_trigger_error', true ) ) {
		debug_print_backtrace(DEBUG_BACKTRACE_IGNORE_ARGS);
		if ( function_exists( '__' ) ) {

This will show you the call stack, which should give you some idea of where it’s coming from. For me it was actually in header.php and not a plugin at all. Remember to take it out again afterwards!

Actually I just noticed I think I do have a genuine bug here too. The “Create new post” button still doesn’t appear but if I go to the direct create URL I can create one fine. I did some further investigation… on line 28 of frontier_post_form_list_detail.php, you call:

if (frontier_can_add() && !fp_get_option_bool(“fps_hide_add_on_list”))

However, this actually checks the permissions for the default post type and not the post type you’re actually listing. I think what you need to do is:

if (frontier_can_add($frontier_add_post_type) && !fp_get_option_bool(“fps_hide_add_on_list”))

I know there are a couple of other template files with similar logic in them too. Hope this helps!

Hi there – thanks for getting back to me! I figured this out but thought I’d post here in case someone else has the same problem. The issue was that “Allow users to change status from Published” was not checked in my Frontier settings. I hadn’t realised that this was an implicit part of being able to edit a post.

In case it helps anyone else, you can get the actual error message that Frontier is generating on failed edit by going directly to what the edit URL would be. You can find this by viewing the page as an administrator, copying the URL that the edit button goes to and then going directly there as the user you’re testing. For me this ended up at https://mysite/mypage?task=edit&postid=23681. I then got the error message “You are not allowed to edit post that is published” which set me off on the right track.