Plugin broke with WP 3.5 update

Everything is there after the update but I get this all the time.

I read several posts about putting (array) in front of the variable and while I am clueless about how or why it works, it stopped the darn error messages on my web site! Yay!

/**
 * Builds URI for a page.
 *
 * Sub pages will be in the "directory" under the parent page post name.
 *
 * @since 1.5.0
 *
 * @param mixed $page Page object or page ID.
 * @return string Page URI.
 */
function get_page_uri($page) {
	if ( ! is_object($page) )
		$page = get_post( $page );
	$uri = $page->post_name;
/* Added (array) in the offending line below */
	foreach ( (array)$page->ancestors as $parent ) {
		$uri = get_post( $parent )->post_name . "/" . $uri;
	}

	return $uri;
}

Yep, case-typing helps a lot with how loosely PHP is designed. Which is why I try to use case typing with classes and arrays.

I’ll take a look at this problem later on tonight when I do a debug with the update. I thought things were good when I tested with the pre-release, but they were still working on things too.

Thanks for the heads up ??

Hello, by any chance you get some kind of error about Line 990 in wp-db.php ? If not, just ignore my post.

Thanks.

You must edited your post…I’ll give it a test run in debug mode, and see what exactly is going on.

If this is a big issue that be more for WP crew to fix, then I will provide an answer, but if I can fix it on my end then I may also end up doing so.

Quick question, if someone wants to answer it…when did 3.5 get released, today?

It pushed through yesterday.

Ah ok.

Well, I was able to find a ticket in trac already, and the APL plugin doesn’t use the wpdb class, but other functions within WordPress have been effected (like get_posts()).

Ticket #22863 (closed defect (bug): invalid)
Ticket #22262 (closed defect (bug): fixed)

Everything on my end seems to still be running fine. Well, apart from all the other plugins. In some situations, some other plugins can effect APL and some other plugins. Usually happens when loading the plugins, and is caused by a plugin loaded beforehand.

I’m still unsure if the query operations of the APL have been effected. Can you try deactivating all the other plugins one by one and see if that changes any thing. May want to try changing your theme to see if the list will reappear, since themes typically use the WP_Query class as well.

Is the APL preset unique in any way? You may need to include the preset being effected. The presets that I have aren’t triggering any errors, and I have tried a few methods that I thought would trigger it.

Either submit the json file in a zip at [email protected] or EkoJr – Issues & Support