noahj-champion

Ok.

You’re welcome and thanks.

Appreciate it!

Ok.

Let me know when you have the CC item up and I’ll check it out.

Thanks! Appreciate it!

I’m using the latest VC version. I didn’t see anyone else mention this so not sure if it was just me or users are using an olver vc version or most are using the popup theme’s for their popup.

I guess later maybe you can add support for the custom css to output…

Example value…

See screenshot @ https://take.ms/cV30o

This is so if the Vc is using a custom background row color, etc. that custom css style will output on the frontend of the site. For now, I just grabbed it from the value option and put it in my theme’s custom css.

Thoughts?

Hi.

I have some code that should permanently fix this issue by filtering the Visual Composer editor status on the popup post type itself. This also will make it more intuitive for user because VC will automatically be an option without them having to select it to be from VC.

Here is the code raw without a class… not sure how you might want to place it in your class. Let me know how you do so I can update the tweak I made.

See the gist @ https://goo.gl/ETtD49

Valentin,

Thanks, appreciate it!

Thanks champ!

Will do. Apologies man, I don’t remember getting your first reply ??

Tu,

Thanks! Appreciate it.

Tu, good deal. Good thoughtful and purposeful slogan ??

Well, hopefully you will find something useful in my testimonial and no problem about the MiniComposer.

Question, are you still open for purchases for including themes with KC?

Oh, and I had question about addons package. How do I know what the addons are?

I didn’t find anywhere what pro addons are so i can see the difference between free and the other options. Is there a demo link for this or are they the addons to come?

Oh, by the way, good move from leaving the Envato site. It took me awhile to locate your plugin. So glad when I saw someone post about in the Avada or Divi theme group ??

Word is out, haha. It took me awhile to check and see that this was the same plugin from Codecanyon. Then I saw… Mini Composer is still in your website title. So then I knew. So maybe you can change that when you get the time. It was the browser tab title.

Ok, sounds good.

Yeah, I wondered how they were enqueueing their css that it wasn’t being caught by Autoptimize.

Thanks for the info.

[SOLVED]

No worries now.

Sorry, forgot. Part of the issue is that an update from CC version will overwrite the pro version with the free version ??

Hi.

I don’t have the same issue when using this plugin.

You should first fix the errors given by your child theme and see if those adjustments fix the issue.

OTW, has been around for awhile and sells premium plugins, so support for their free plugins is probably limited or comes available only as they are become available to provide it.

I took a look at the plugin and it seems (at the least) a file has been left out, but they are still referencing it.

In otw_blog_manager_light.php on line 873, try commenting that line out so it looks like…

//include( 'social-shares.php' ); because this file doesn’t exist, which is why you are getting the class not found error.

I’m not sure how commeintgin that out will affect eh display of the plugin though. But after which you should comment out the action called to that function.

So starting at line 129, you can make it to look like…

// Ajax FE Social Share
//add_action( 'wp_ajax_social_share', array($this, 'otw_bm_social_share') );
//add_action( 'wp_ajax_nopriv_social_share', array($this, 'otw_bm_social_share') );

There would still be a few optimization to be done since the social-shares.php file is missing. Ultimately the best solution is for that file to be included, which might of been left out by mistake, or the plugin could just use some adjustments.

At least, that is what I see so far.

Hey, no problem. Yeah, I switch between the 2 because each serves it’s own purpose/UI.

By the way, the plugin works out of the box. I chose to keep an updated Github version incase this repo leaves because I have been using Dev Monitor for about a year so far, with no problems.

It helps when you need a much lighter version of Query Monitor. I use this plugin more than Query Monitor a lot, because it gives me just the necessary things I need to know and some options to disable or enable what I need, so I run it light. A must install for me for awhile now.