foxydot

Thank you! Adding the cachetime param to the shortcode worked a treat!

• This reply was modified 11 months, 3 weeks ago by foxydot.

good catch, helpful. fixed it for me. that was VERY frustrating!

ok, I need to move on from this, but here’s what I found so far:

Widgets_On_Pages_Admin::wop_register_sidebar() $loop seems to be hijacking the page type in the admin screen. I’m not sure exactly how, but if I change the params on my Metabox generator to include ‘turbo-sidebar-cpt’, my metaboxes show up on the admin screen again. (of course they also show up on the edit panel for each turbo-sidebar-cpt as well, not)

So whatever is going on with the loop, it’s somehow fooling this custom method in WPAlchemy (https://github.com/farinspace/wpalchemy/blob/master/wp-content/wpalchemy/MetaBox.php#L1001) into thinking that the “post” is now a “turbo-sidebar-cpt”.

One thing you might want to add, although it didn’t help fix this issue, is a wp_reset_postdata() after your while statement. I thought it should fix that problem, but it did not.

As I expected, the diff was kind of useless because of the full rebuild. I’m switching back to beta in my dev env and going to start some incremental tests . ;D

I’ll let you know if I find anything that seems to be useful.

Either way, six months and 4 new releases later, and this still isn’t corrected. It’s generating 404s on my sites. I’m thinking I might fork the plugin since it seems that all the new releases do is “confirm WPx.x compatibility.”

I stand corrected! Thanks for the resource here. I forgot about content_url(). But overall, yeah, making it self-referential is preferred when possible.

Better yet, use the constants:

https://codex.www.ads-software.com/Determining_Plugin_and_Content_Directories#Constants

…here’s how I do it:
$this->the_path = plugin_dir_path(__FILE__);
(of course this is inside a class structure)

oops. just noted i gave you a path when you needed a url. both should be constants, really, because well, both are editable in the framework.

`$this->the_path = plugin_dir_path(__FILE__);
$this->the_url = plugin_dir_url(__FILE__);`

Hrm. That setting is a little misleading then. When I “Let WordPress Choose” it no longer breaks the entire site. But if a template is selected, that template overrides the default template everywhere a specific template isn’t specified, not only on bracket post types.

My client is no longer using the plugin and it’s well into March Madness, (I think they went with ESPN), but it’s probably not a hard fix. I’ll see if I can’t hunt down the greedy code and submit a patch over the weekend.

+1 on this. Took me all of five minutes to patch, but I don’t want to have to do that every time my client upgrades the plugin without asking me first.

add_filter('jpb_visual_shortcodes','add_visual_shortcode_image');
function add_visual_shortcode_image($shortcodes){
	$shortcodes[] = array(
		'shortcode' => 'gravityform',
		'image' => get_stylesheet_directory_uri().'/images/form.png',
		'command' => NULL,
	);
	$shortcodes[] = array(
		'shortcode' => 'entry_grid',
		'image' => get_stylesheet_directory_uri().'/images/listings.png',
		'command' => NULL,
	);
	$shortcodes[] = array(
		'shortcode' => 'inline-login',
		'image' => get_stylesheet_directory_uri().'/images/login.png',
		'command' => NULL,
	);
	return $shortcodes;
}

hope this helps someone.

I’m having a similar problem. I *love* this plugin and use it all the time. I have the pay-to-play Backup Buddy and for simple back and forth, I far prefer this one. But the text widget issue does pose a problem.

I am a coder and will see what I can do about working up a patch.

Hrm. I’ve used this plugin to move a few (granted, smaller) multisites. I usually just remove the https://www. from the url change item and everything seems to work pretty smoothly. The only thing that doesn’t seem to transfer is, for some reason, text widgets.

I have not tried to do it with any kind of domain mapping applied, as I usually handle that after I “go live” with a site. I wonder if I’ve been missing something.

Same problem in FF & Chrome on a Mac. Worked fine before latest update. ??

Thanks for the heads up. Just purchased wpcincinnati.com, will make the switch this afternoon!