cm258

So, I upgraded to 3.0.1 again, thinking I’d just try creating a new slider and drop it in instead (I only have the one on the home page). But even that doesn’t work:

Trying to add images from the library causes a fatal error:

PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 72 bytes) in /Library/WebServer/axstv/wp-includes/post.php on line 2380, referer: https://localtest.axs.tv/wp-admin/admin.php?page=easingslider&edit=26816

But no image will actually be added. And, I eventually get to a place where the “Update” button won’t enable.

Finally, I am also not able to delete the new slider I’ve made by clicking the “Trash” button in the “All Sliders” view. Nor, for that matter will it duplicate an old slider…

cm

Yes, I see the successful upgrade, no matter how I do it, even when I just nuke the whole easing-slider directory and replace it with the update.

Perhaps this will help: there’s something strange going on with the ID for the slider. It seems that at one time, the slider had a different ID. Here’s the code I have in my template to display the slider:

<?php if ( function_exists( "easingsliderlite" ) ) { easingsliderlite('21358'); } ?>

However, when I look at the slider in the admin, the code it suggest is the following:

<?php if ( function_exists( 'easingslider' ) ) { easingslider( 21384 ); } ?>

Which also works with 2.2.1.1. However, when I do the upgrade to 3.0.1, I get errors until I log into the admin, then they go away and the slider just doesn’t show up any more.

cm

I’m upgrading from 2.2.1.1.

Yeah, I get something similar to what John got: I update the plugin, get an error in the log:

Cannot use object of type stdClass as array in /Library/WebServer/wp-content/plugins/easing-slider/src/Foundation/Options/OptionArray.php on line 25

Then, if I log into the WP admin, look around at the Easing Slider editor, just to confirm it’s there, when I go back to the home page, no slider loads.

Like John, restoring the old version of Easing Slider Lite works fine…

PHP Version 5.4.45
WP version 4.5.2.

cm

For what it’s worth, though this is marked as resolved, I did find another interesting fact: ‘hierarchical’ can still be set to true if ‘query_var’ is set to true as well when you set up the custom post type.

This actually makes more sense to me, I think, if I read the documentation correctly.

cm

Hmm. I’ve been hit with this on some of my custom post types (not on others, though).

Here’s what I’ve been able to determine:

They’ll display again if I use this setting in the register_post_type function:

'hierarchical' => false,

Then I re-save the permalinks page (flushing the rewrite rules).

I also dumped the rewrite rules in both 3.6.1 and 3.7.1 and found some differences. I have this rule in my 3.6.1 dump:

["programs/(.+?)(/[0-9]+)?/?$"]=>
    string(68) "index.php?post_type=hdnet_programs&name=$matches[1]&page=$matches[2]"

Based on a process of elimination, I believe that the corresponding rule in 3.7.1 is this:

["(.+?)(/[0-9]+)?/?$"]=>
    string(72) "index.php?post_type=hdnet_programs&pagename=$matches[1]&page=$matches[2]"

Hope this helps…

cm

You’re welcome…

Maybe the author will fix it in the plugin…

Looks like he just updated to 1.0.9, and incorporated those three fixes…

I’ve had to fix those errors every time I update this plugin for a while now. I actually make three edits:

Add a line before line 752 right after the function declaration for “wgba_debug”:

function wbga_debug($message) {
  global $wbga_debug_enabled;  // insert this line
  if ($wbga_debug_enabled) {

Then, go to the function “wgba_track_user” and change the third line of that function to make it look like this:

if (!($user_level)) {

Finally, I also have to make a change to the in the Stat Dashboard Settings section. There’s a missing “php” opening a block of PHP code that will cause issues on some systems. It’s on line 1076 in the file and looks like this:

<? if(!class_exists('SimpleXMLElement'))

I alter it like so:

<?php if(!class_exists('SimpleXMLElement'))

cm258

Hey Rafael,

See if the solution I posted in another thread helps.

I found what looks like a fix in the forums here:

add_filter( 'get_media_item_args', 'force_send' );
function force_send($args) {
	$args['send'] = true;
	return $args;
}

I just added that code to the top of the functions_post.php file in the plugin and the “Select” button (which is apparently really the “Insert into Post” button, just renamed later in the plugin) shows up once again for me.

Your error is on the last line:

add_shortcode(showmyads', 'adsenseads');

should be:

add_shortcode('showmyads', 'adsenseads');

(You’re missing a single quote mark just before “showmyads”).

cm

I got rid of the error two ways:

1. comment out the following line:

add_filter('post_limits', 'relevanssi_getLimit');

2. Leave the previous line as-is, but add back this function (taken from 2.9.1) that is no longer in 2.9.2:

// This function is from Kenny Katzgrau
function relevanssi_getLimit($limit) {
	global $wpSearch_low;
	global $wpSearch_high;

	if(is_search()) {
		$temp 			= str_replace("LIMIT", "", $limit);
		$temp 			= explode(",", $temp);
		$wpSearch_low 	= intval($temp[0]);
		if ($wpSearch_high == 0) {
			$wpSearch_high 	= intval($wpSearch_low + intval($temp[1]) - 1);
		}
	}

	return $limit;
}

I haven’t decided which to go with for sure, but either one stops the error appearing (and fixes another problem I have with version 2.9.2 of the plugin).