sem101

Are you running the same Chrome version as me?
Yes, I’ve disabled all Chrome extensions.
I’m going to try on another computer right now…

Thanks!

Thanks

Ah ha! That’s the culprit ?? I do have the Github Updater plugin installed. Thanks Ajay.

I am now getting this…

Contextual Related Posts
You have version 2.1.1 installed. Update to 2.2-beta20150712. View version 2.2-beta20150712 details.
Compatibility with WordPress 4.2.2: 100% (according to its author)

ATTN MOD: Not resolved. Why marked as resolved?

Nah. Some people in the company do not have accounts nor will they get them.

I’m going to my option #1 and I’m going to create a “hidden” category and hide the category within my loop and be done with it. Posts from that category will still be live (published) but will not show in Archives (sitewide).

I just thought someone else might have better ideas. Nah.

Sorry, to be clear, basically the reason why I need to hide a post is to give the URL for review before it goes live: to people who do not have an account. That’s all.

But I was requested to not have password protection.

I’ve got it working now. I had to map the static values required by the CRM.

I just decided to used a HTML form, wrap it into a plugin, and enqueue jQuery form validation instead.

The POST action URL is an external site. I’m trying to use CF7 as a newsletter form with fname, lname, email to post to a newsletter CRM. Your help is appreciate. Thank you

OK, the only way I was able to get this to work was…

1. WPSEO, uncheck “Strip the category base”
2. Install WP No Category Base plugin

Unfortunately, that didn’t work. Thank you for your reply.

After I do the Network Admin Permalink Structure “trick” to remove “blog” from slug – I’m cautious to never reset site Permalinks. I think that’s what you were suggesting?

i’m gonna try to do a fresh Multisite install and see what happens. Or am I fighting an uphill battle? Primary site requires /blog/ in the Permalink in a subfolder install?

It was working beautifully in my subdomain install ??

Thanks

Thanks songdogtech,

I like the Whitelist idea. I usually never whitelist or blacklist because I know IPs can get spoof. But I will implement that added layer.

As for HTTP Basic Auth, I never had hack attempts get past that. So they never were even able to access wp-login.php before. But now they are accessing wp-login.php so my first thought was that they found the password for HTTP Basic Auth. I agree with you, I will have to audit my server logs to confirm if this is true or not.

Yeah, I tell customers it’s 24/7 defense. But I have seen heavy activity this month. I very big spike.

Thanks

OMG thanks you! this was so easy! *happy dance*

Thanks