rcastagna

Got it…I see the auto_prepend_file now, and mine says ‘no value’ for both Local Value and Master Value.

I’m using PHP 5.4.9…I wonder if it’s just a matter of upgrading PHP to produce the same results. I really hope not…upgrading PHP is a PITA on IIS.

@njsent – I just had the chance to double-back to this issue, and I’m still seeing problems. I dropped a phpinfo() page into the site I’m working with, and even though I see the correct path to the php.ini file, I’m not seeing anything in phpinfo where it suggests that it’s loading the wordfence-waf file.

In both the Enviornment:Path and _Server[“PATH”] blocks I see a number of files listed, but nothing pointing to wordfence-waf.

Am I looking in the correct place to see the info I expect?

Thanks again for the help…sorry to be such a repeat pain.

Take care,
Ric

@njsent It just struck me as very odd that by referencing one “instance” of the WF firewall, that all of them started “working”.

I will do the phpinfo() trick and see what’s happening.

Thanks for the help on this…I really appreciate you taking the time to respond.

@njsent – ok, very interesting development on my server…I put in a PATH statement as described above referencing one of my many sites. I just went to another site (actually, a few other sites) and logged it to the dashboard. Although they’re not described in the PATH, they now show the WF Firewall as configured and running. Some sites, if using a premium key, show they’re running the premium version of the firewall.

My guess is that I won’t be able to do any custom configuration to the sites that are not referenced in the php.ini, or, any changes made on one site will affect the same change on all the other site(s) regardless of whether or not they are listed for the auto_prepend_file in the php.ini file.

Very strange.

@njsent

I read through the link you provided as referenced, along with your comments, and I’m still about as confused as a newborn in a Gentleman’s Club.

I’m running single installation of PHP 5.4, and many WP installations that follow the path convention of C:\sites\site_directory.

Are you suggesting for each WP site I need to add the PATH lines to the php.ini?

For example, I have two sites – websiteA and websiteB. Do I add the following to the end of my php.ini file?

[PATH=C:\sites\websiteA\]
auto_prepend_file = 'C:\sites\websiteA\wordfence-waf.php'

[PATH=C:\sites\websiteB\]
auto_prepend_file = 'C:\sites\websiteB\wordfence-waf.php'

I would test this myself, unfortunately, I don’t have a DEV server…everything is in production, and I’d rather not muck up 20-ish active/running web sites. ??

[UPDATE] I just installed the most recent version of Contact Form DB and I’m noticing the same issue with the piped selections.

Could the issue be that [_raw_{field name}] is only supported within the confines of CF7?

Thanks,
Ric

As I said above, I own a motorcycle shop. Autobase does nothing, ABSOLUTELY NOTHING, for me. My understanding was that this plugin was able to run without Autobase so long as it was registered.

My efforts to register the plugin ended up revealing the $149 monthly fee without the Autobase subscription.

Either PGI hasn’t quite figured out how to price/market this plugin, or it does not operate as advertised.

Regardless of the case, at $149/mo this plugin couldn’t possibly generate enough revenue to justify purchase, especially for a motorcycle shop that has no need for an automobile inventory feed.

Well, just got off the phone with the folks at PGI Auto – the company behind this plugin. This is no longer a free plugin. PGI Auto has priced this piece at $149 per month without the Autobase subscription. That’s just way, way, way too pricey for a small shop like me.

Too bad, really…it looked very promising. Oh, well.

I’d love to know the answer to that, as well. As a motorcycle shop, I have no use for Autobase, but this looks like a great plugin!