Daniel Milner

Hi Dave,

Sorry for the delayed reply. I just saw this.

The www.ads-software.com (free) version includes the CCB Login Widget and the Online Giving Widget. In addition to that, it lays the groundwork for the future of CCBPress. Our next major release will move to a free + addons model. CCBPress Core will handle the the process of syncing data from CCB to custom tables. The addons will register themselves with the Core plugin and hook into its interface to extend the capabilities.

Hi Chuck,
At the moment, the only way to do that would be to create an event for each service time. We’ll add this to our wish/to-do list though.

Beaver Builder does their add_action right up front, so remove_action should work if you add it to the plugins_loaded action hook. You just have to make sure that remove_action happens after add_action.

The only problem with hooking in to wp_before_admin_bar_render to remove an item, is that by that point, the admin bar is pretty much set in stone. Meaning that any plugins that are going to add their menus or sub-menus to it have already done so. Mainly, what I’m saying is that if you want to remove a menu item, you should probably prevent it from being added in the first place instead of removing it after it’s already there.

In my situation, my plugin (Beaver Tunnels), adds a sub-menu to the Page Builder menu. I can run a check to make sure that the Page Builder menu exists and create my own menu if it doesn’t…but when the menu is removed right before it’s output to the page, everything gets lost.

For now, I’ve added a specific check to look for the apspider_admin_bar_removal action hook and add my own menu if it exists.

Btw, your plugin is great and I see it offering a great value to a lot of people.

If you have any questions or are just stuck on something not working right. Feel free to hit me up. I’d be glad to help out.

Hello peterson4040,

I’m glad you love the plugin. ??

We noticed that issue as well and will be working on adding a setting for it. I’ll update this post when I have more information on it.

Thanks Jeremy. I ended up sending a support request through the jetpack.me website and Carolyn helped me get it sorted out.

I came here to post this same issue that I’m having with my self-hosted WordPress site.

Marked as ‘resolved’

That’s great to hear Hope Cafe! So glad it’s working now ??

No problem dvelluppillai.

PHP v5.2 reached its end of life almost 5 years ago. Your host should be able to update it for you.

@dvelluppillai Hmm…anonymous functions should work in that version of PHP. Are you sure that you’re getting the same error?

It looks like it might be related to the version of PHP that’s running. Can you guys tell me which version of PHP you have running on your sites?

I was missing a “:” before the version number in my main plugin file.

In your example, “group1”, “group2”, “group3”, etc. are the values that are stored in the theme option. That’s why you are getting “group1” when you retrieve that option.

You have two options.

1. Keep your code the way it is and translate the option to the appropriate label when you retrieve it.
2. Change your code so that the value is the same as the label.

'choices'  => array(
    'Group 1' => __( 'Group 1', 'ctotheme' ),
    'Group 2' => __( 'Group 2', 'ctotheme' ),
    'Group 3' => __( 'Group 3', 'ctotheme' ),
    'Group 4' => __( 'Group 4', 'ctotheme' )
)

I checked the error logs, but they were empty.

I think that it may be a problem with the version of PHP. We are on Siteground and got 500 errors with PHP 5.3, but the problems went away when we changed to PHP 5.4.