Alex

Thanks, Richard, email sent!

Okay, this is another thing from Payeezy support –

Please contact the plugin creator and advise them to either remove the x_type parameter or to specify it as AUTH_CAPTURE. We have no control over third party plugin code.

Thanks for the suggestion, Richard!

@arsdehnel, 0.9.5 does not resolve critical errors. What you did to “fix” the broken 0.9.4 was to comment out the lines calling for missing files which were still required. amcnab is missing the plugin options page for a valid reason: the function is no longer there in the source code, it must have gone together with the missing files. If you’re too busy to maintain a plugin, taking it down makes a lot more sense than wasting others time. All due respect.

Hi arsdehnel, is there an update for this yet, please?

Hi guys, sorry to have missed this thread for so long.

If you’re still looking for the code to remove parent slugs from the page permalinks, here you go:
OPEN: /wp-includes/page.php
FIND AN REMOVE:

while ($curpage->post_parent != 0) {
$curpage = $wpdb->get_row( $wpdb->prepare( “SELECT ID, post_name, post_parent FROM $wpdb->posts WHERE ID = %d and post_type=’page'”, $curpage->post_parent ));
$path = ‘/’ . $curpage->post_name . $path;
}

FIND AN REMOVE:

// A page cannot be it’s own parent.
if ( $page->post_parent == $page->ID )
return $uri;

while ($page->post_parent != 0) {
$page = get_page($page->post_parent);
$uri = $page->post_name . “/” . $uri;
}

Do not forget to save the file and make sure it’s updated on the test server. Once you did that, go to the Permalinks manager inside wp-admin panel and hit “Save Changes” once to update the permalink settings.

Note: use these instructions at your own risk.

Where do you want me to send the fix to, brianbrandt?

Yes, try changing that plugin line to something like:

if (is_single())
{
	add_action('wp_head', 'myfunction()');
}

I stumbled upon a similar requirement where page parent slugs were not needed in the page URL, so I searched around and found more threads like this with people asking the same thing, but no solution was given.

I finally worked it out but not yet sure how to put it up into a plug-in rather than apply the hack to the core WordPress files so that future WordPress upgrades aren’t affected.

As soon as I have this solved, I’ll upload it to the WordPress Plug-ins directory.

I have figured out how to do this, just that not yet sure how to include the modifications as a plug-in to make the solution friendly to future WordPress upgrades. Still working on that part…