Jon Brown

cdils – wish I could answer this, but am just hoping this helps Travis help you…

Travis – Perhaps totally unrelated, perhaps not, but a month ago I was having what seems like a similar issue with Genesis bbPress Extend + GSS that Jared Atchinson helped me track down and hack around.

Quoting Jared (this fixed worked for me)”:

The easiest and quickest fix is to add this to print_meta

public static function print_meta() {
if ( is_bbpress() )
return;

This way if any bbPress page is triggers the plugin bails.

Doing a little looking under the hood, it’s the get_meta_singular() function that gets run and ends up killing the loop some where along the way. Im going to come back and see if I can figure out what in the function is screwing things up, but for now I would just use the conditional above that keeps the plugin from running on bbPress pages.

Obviously that won’t work for cdils, but I’m just guessing maybe the get_meta_singular function is similarly to blame here.

same problem

Thanks MattyRob.

I think I was getting emails because “Send Admins notifications for new subscriptions” was checked. I wanted the other admin to get notices, but I’ll settle for no one getting notices. I’m hoping because Send Email From: bloginfo(‘name’) that an email will still get sent to admin_email.

Thanks

Similar to the other thread. I took a look at Marahan.

It’s using:”
define(‘PADD_THEME_PATH’,get_theme_root() . DIRECTORY_SEPARATOR . PADD_THEME_SLUG);

To define the path to the theme, when it should be using get_template_directory

This plugin just does exactly what the Codex outlines for starting a child theme. I coul be wrong not having tested it, but I suspect if you manually created a child theme, you’d have the same problem.

If the parent theme is coded properly this shouldn’t happen.

A blind guess, but if the parent theme is using get_stylesheet_directory to find it’s admin folder instead of get_template_directory this could happen.

Quickly looking at Delicacy it’s doing some unusual conditional logic to determine where to load the admin from:

/*------------------------------------------------------------*/
/* Options Framework Theme
/*------------------------------------------------------------*/

/* Set the file path based on whether the Options Framework Theme is a parent theme or child theme */

if ( STYLESHEETPATH == TEMPLATEPATH ) {
	define('OPTIONS_FRAMEWORK_URL', TEMPLATEPATH . '/admin/');
	define('OPTIONS_FRAMEWORK_DIRECTORY', get_template_directory_uri() . '/admin/');
} else {
	define('OPTIONS_FRAMEWORK_URL', STYLESHEETPATH . '/admin/');
	define('OPTIONS_FRAMEWORK_DIRECTORY', get_stylesheet_directory_uri() . '/admin/');
}

require_once (OPTIONS_FRAMEWORK_URL . 'options-framework.php');

}

I’m not going to dig into it further, but it looks like a non-standard way to define parent/child themes…

How are you creating an all author page more simply than this plugin?

Cool. Hopefully it just needs some added CSS specificity.

Carl tracked down the conflict. Surprisingly it’s not a JS conflict, it’s a CSS conflict. MailChimp loads Flick.css.

I tracked it further to line 299 which sets .ui-datepicker to display:none, without that the GF date picker still works fine, and MailChimp’s shows up but is still off a little…

Anyway, enough trouble shooting for me… I rebuilt the MailChimp signup form using a custom Gravity Forms in about 10 minutes, hours ago… so no more issues for me just wanted to track down the conflict so maybe it’d get fixed.

FWIW, I put up a demo/test site of the conflict here: https://ephemurl.com/2w/xxt

It’ll come down soon though….

Thanks Nate and sorry for the testy tone… 30+ minutes of troubleshooting a problem that seems to have no reason to exist left me rather annoyed.

I’d really like to know if there is any reason that the plugin loads the JQ UI Datepicker to begin with? I’ve looked through the code and as far as I can tell it’s not actually being used anywhere by the plugin. I’m far from a php/js expert though could easily be wrong.

The plugin does seem to setup a pair of extra classes for .birthdate-pick and .date-pick, but again those don’t appear to be used anywhere by the plugin…

Finally, it’s loading datepicker.js on all front end pages, regardless of whether they have a MC signup form on them or not and it’s not loading it from a CDN (not the end of the world).

That’s why your client hired you ??

Either debug ACE (that’s the beauty of Open Source, you can fix it yourself), or write a custom plugin for your client. Personally I found it easier to just custom code a category exclusion option into my clients theme then mess with debugging a 2 year old plugin with lots of features I didn’t actually need. YMMV.

Rather then use the plugin just remove the categories from the query yourself. There is a
Good example in the codex. https://codex.www.ads-software.com/Custom_Queries#Category_Exclusion

Many people will ALWAYS have trouble finding plugin settings, but it’s probably most often because they’ve never used a plugin with settings before.

One setting I’d like to see is the ability to show the count bubble even when the count is 0. It makes for a more consistent look. Just put it on https://foodpractice.com/ using manual placement to appends it to manually placed sharethis buttons.

The other option that is sometimes. I’ve with these types of plugins is to disable it on a single page. (ie. metabox post editor saying check here to not display pinterest on this post)… Might be a bad idea for performance reasons though…

Awesome+ I was just coming to the forum to ask the exact thing: “Please add an option to manually insert the button and a template tag to insert it”.

I can now just leave both boxes unchecked and use do_shortcode(‘[pinit]’) to place it in next to my other sharing buttons

One note, unless it was turned off when updated, I think you changed where you stored the option because after updating (and before putting code in to manually display) the pinterest button stopped showing… could haven’t just been me though.

Also, personally I really don’t like the settings for this being added to the sidebar instead of under Settings ??

+1 for removing tables when the plugin is deleted.

No… Thank YOU!