codejp3

@ajtruckle – 2 things real quick

1.) Version 5.6.1 has been released which includes the auto-cache clearing functionality. If you EVER find that you still have to manually clear cache, I’d love to hear when/where/why you had to do so.

2.) I used your code snippet for custom CSS to test the exact scenario you had to manually clear AutOptimize, and while doing so I noticed some tweaking to your CSS snippet that I had to do to make it work exactly as expected. Here’s a revised snippet that you may want to also apply to your site:

.trucklesoft-topic-buttons, 
#bbpress-forums a.trucklesoft-topic-buttons, 
#bbpress-forums a.trucklesoft-topic-buttons:visited  {
    border: solid 1px #248ed0;
    color: #fff;
    background: #248ed0;
    padding: 8px 25px 8px;
    font-size: .86666667em;
    line-height: 1.384615em;
    margin-top: 5px;
    margin-bottom: 5px;
    display: inline-block;
    text-transform: uppercase;
    font-weight: normal;
}

.trucklesoft-topic-buttons:hover, 
#bbpress-forums a.trucklesoft-topic-buttons:hover {
    color: #248ed0;
    border: solid 1px #248ed0;
    text-decoration: none;
    background: #fff;
}	 

Cheers!

I’ve tried to isolate the exact issue without success. I’ve reached out to miniOrange in their support forum for this plugin to try to figure out a permanent solution to this conflict.:
https://ww.wp.xz.cn/support/topic/plugin-conflict-396/

Until it’s resolved, I’ve tested the actual Moderation Tools and confirmed that they do indeed work as expected with or without the minOrange OTP Verification plugin activated.

The only conflict seems to be with trying to enable/disable Moderation Tools in the “Moderation” tab ( /wp-admin/options-general.php?page=bbp-style-pack&tab=modtools ).

A temporary ( janky-but-effective ) workaround would be to temporarily disable the OTP Verification plugin, enable Moderating Tools in Style Pack, and then re-enable the OTP Verification plugin. That way you can have Moderation Tools & OTP Verification.

We’ll try to identify the conflict and come up with a permanent solution.

Thanks for reporting it!

Perfect! I’m going to mark this as resolved, but feel free to post here again if you have any other issues related to this.

@ajtruckle – Good news! I was able to get a class method that I we can use to force AutOptimize to reset its’ cache.

I’ve implemented this into the next upcoming release of Style Pack.

You get to be the official guinea pig for thoroughly testing this. 🙂

I’ve already tested it and can confirm that AutOptimize is clearing its’ cache whenever any settings are changed that regenerate CSS/JS files, but I’m mainly interested in if you ever run into ANY situation where you make a change to Style Pack, but STILL HAVE TO do a manual reset of AutOptimize. Thanks in advance for your feedback!

This new version should be released sometime this weekend.

@naielah – It’s been 2 days. Just checking back in with you.

Sorry you’re experiencing issues.

I just checked the stats, and thousands of people have updated to the new version, but you’re the first (maybe only one) to experience this. We will troubleshoot it, but there’s a chance it may not be directly related to Style Pack.

Considering it’s a private site, troubleshooting will be a little more difficult, but let’s start with some basics.

1.) Did you update anything else recently or at the same time as Style Pack?

2.) Do you have moderation tools enabled?

3.) Do you have any words or phrases in the WP Discussion settings for blacklisted/disallowed words.

4.) Do you have debugging enabled and are there any recent entries in the debug log file?

5.) When you make a post, you say it shows up empty/blank. Do the post actually save in the DB? Can you see the empty/blank post in the WP admin panel? Or is it not being saved at all?

6.) Does it only affect the admin user or every user?

7.) Have you gone through the standard troubleshooting procedures of disabling plugins except for Style Pack and bbPress, verifying that works properly, and then re-enabling plugins one at a time, retesting after each one, until you find the conflict?

8.) Have you tried uninstalling v 5.6.0 and rolling back to v 5.5.9 to see if the issue still persists?

There’s other things we can try, but it starts to get complicated quickly. These are the basics to try first.