Appreciate your further inputs here.

Some Final thoughts:

1. Our Cloudflare Plan is free and has served us well.
2. Per our Server Admin, Disabling mod_security is a no-go because the site is under constant attack. Example in the time you worked on the site, there were 27 exploit attempts (uploading PHP exploit) that were all blocked.
3. As we mentioned above, our challenge is one of maintaining existing simplicity. Our Site has been working flawlessly with all existing plugins for many months. We expected the  SimplePress Plug-in to also work seamlessly and flawlessly “out-of-the box. And were we to mover forward with any changes in existing configurations/processes or, we run the risk of causing issues with other plugins that are all fine at present or new I suppose our challenge is simplicity. Our Site has been working flawlessly with all existing plugins for many months. We expected the  SimplePress Plug-in to also work seamlessly and flawlessly “out-of-the box. And were we to mover forward with any changes in configurations/processes, we run the risk of causing issues with other plugins that are all fine at present. We simply don’t have the time/resources and can’t run the risk of more bumps in the road going forward.. We simply don’t have the time/resources and can’t run the risk of more bumps in the road going forward.

Mr Papa said
Thanks Doc!  

Glad to be of assistance. 

Personally I will never go back to site hosting without cloudflare handling the dns. RocketLoader is a huge performance boost but it is challenging. They are working on a replacement for it. 

Http/2 server push is another great feature of cloudflare, but my server whm does not support it yet in easy apache. That will really open the flood gates when it’s active. 

Dennis Pitocco said
Appreciate your further inputs here.

Some Final thoughts:

1. Our Cloudflare Plan is free and has served us well.

1. Per our Server Admin, Disabling mod_security is a no-go because the site is under constant attack. Example in the time you worked on the site, there were 27 exploit attempts (uploading PHP exploit) that were all blocked.

1. As we mentioned above, our challenge is one of maintaining existing simplicity. Our Site has been working flawlessly with all existing plugins for many months. We expected the  SimplePress Plug-in to also work seamlessly and flawlessly “out-of-the box. And were we to mover forward with any changes in existing configurations/processes or, we run the risk of causing issues with other plugins that are all fine at present or new I suppose our challenge is simplicity. Our Site has been working flawlessly with all existing plugins for many months. We expected the  SimplePress Plug-in to also work seamlessly and flawlessly “out-of-the box. And were we to mover forward with any changes in configurations/processes, we run the risk of causing issues with other plugins that are all fine at present. We simply don’t have the time/resources and can’t run the risk of more bumps in the road going forward.. We simply don’t have the time/resources and can’t run the risk of more bumps in the road going forward.

  

SimplePress works fantastic out of the box on a standard php wordpress environment. Putting cloudflare in front of your server / hosting account requires fine tuning. 

Thanks again Doc – we really do appreciate the advice and assistance. Seems like they plan to go with bbPress instead.

My last thought is that if they don’t sort out their httpXMLRequest and get it working properly then their problems are going to get more frequent with future plugins. But they have made the call and I wish them well.

Please understand that prior to testing SimplePress, we had BBPress (and Buddypress) up & running and fully-functional within our current configurations, cloudflare included. Our plan to now go an alternative route is a very reluctant one, as we selected SimplePress as a better BBPress alternative based on features, functions, simplicity, support etc.

I did not read this whole post last night, laying in bed posting from my smartphone. Just noticed you are running a caching plugin. That is not recommended with CloudFlare if you are using it’s cache feature. You are caching the cache – that will not work well at all.

SimplePress has more bells and whistles than WordPress posts / pages. It is superior to other wordpress forum plugins. Therefore it’s making many more database calls than a normal wp install. It’s like comparing a Chevrolet to a Ferrari. You want that performance of the Ferrari but’s it’s a temperamental beast with it’s hood up more than the Chevy. 

I suggest turning RocketLoader OFF. 

Mod security should be ok since you are not running cf waf firewall.

Disable your caching plugin – and dump the cache on cf.

I believe this will solve most of your problems. 

Plus you will never find a more supportive bunch than in this forum.

Regards, Ed

Another suggestion related to Mod Security.

If you are running the default rule set – check to see if any false positives are logged. This will be under security > mod security tools. Common false positives include, 960009, and 981247 that is commonly triggered by WordPress admin bar. When false positive rules are triggered mod security redirects the url to the root domain. 

Regards, Ed

Just a final word of appreciation to YellowSwordfish, Mr. Papa and Fidosysop for your noteworthy efforts to help us get SimplePress up and running over the past month since purchase – a real testament to the quality of your Support versus that of many other Support Teams we’ve encountered over the years. Unfortunate that we are moving away on a sour note having now received a notably arbitrary response from Andy regarding our Refund Request. Not so much about the $$$ and time wasted, but rather the nature of Andy’s response. Unfortunate and disappointing, indeed.

Thanks again for your help!

Dennis