monk3

Figured it out:
When using a text field, and using text as a placeholder, the input has to be exact.

@mwrusnak: Your info is very helpful. I didn’t realize inputs.
We do have hulk as well as part of a number of defenses, and the total sum seems to be working well.
Question: in WF, (1) how long do you typically block them for? (2) do you ever make them permanent? (3)How do you determine who to block from the site as compared to locking out from login, and on what basis?

Thanks.

The ubiquitous “sorry”. How about doing the job correctly from the start. The original poster simply pointed out issues that any dev would NOT have allowed in the wild.
Grow up.

@tim: Not seeing any codes. Here’s an example, redacted:

6 failed login attempts to account [email protected] (pop3) — Large number of attempts from this IP: 94.102.xx.xxx

Reverse DNS: user186.xxxxxxxx.net

Origin Country: Netherlands (NL)

@mwrusnak: It gets me another step closer, thanks.

Yes.

We were wanting to add the code as presented on the Piwik page: https://piwik.org/faq/how-to/#faq_176. It states:
“You can however configure Piwik to also track users with Javascript disabled: to do so, edit the Piwik Tracking Tag <noscript> and change:
<noscript><p><img src="https://piwik-server.com/piwik.php?idsite=1" style="border:0" alt="" /></p></noscript>
Replace with the following:
<noscript><p><img src="https://piwik-server.com/piwik.php?idsite=1&rec=1" style="border:0" alt="" /></p></noscript>
After making this change and adding &rec=1, visitors with disabled Javascript will execute the noscript and will load the piwik.php image and will have their traffic recorded in Piwik.

Note: the most famous bots will still be ignored with this technique. To force Piwik to track all bots, add the parameter &bots=1 to the tracking URL, eg:
<noscript><p><img src="https://piwik-server.com/piwik.php?idsite=1&rec=1&bots=1" style="border:0" alt="" /></p></noscript>

Therefore, that is what we were attempting to do, according to their well-written instructions.

Apparently, your plugin is not concurrent with the apps instruction set, and at the least is lacking in adequate instruction.

That doesn’t tell me a thing except that your comment is condescending, dismissive, and quite rude: ie, “If you know what to do here, feel free to do so ;-)”.
Well, yes I do know what to do if the author would put enough ques as to provide the context for the field; which it could be more than one. Granted, you know what your intent was when you wrote it; however, viewed from the other side, the user side, we cannot read your mind, and there is more than one possibility as to what your intent was.
So please, when asked a question, please provide answers that not brief, but actually offer better understanding and accuracy. Then again, we don’t have to send you money, which we do for nearly 100% of the themes, plugins and research we utilize. Then again, for those authors who blow us off by assuming we are illiterate, we offer less, like nadda. So take your choice: help people out and get paid, or be an arrogant ass.

Thank you, I’ll give that a try.

Actually, by taking out the field we entered post-facto, it is back to working. I can only assume that it has to do with the back-end not being able to adjust to the change in the front-end; but I wanted to get confirmation rather than work from assumption.

Anyone else have the same issues???

Solved.

Solved

Okay, thanks.
Maybe in the future.

Thanks for the clarification.

Read the article.
It appears that using the attributes is for the registration page use.
We are hoping to use them a little differently: As we enter a location, we would like to have the same form fields show up on the location creation page, not the registration page.
Example:
The location is XYZ Athletic Fields.
As we create the Location page for that (and all) locations, we would like to have fields for such things as:
– Whether there is lighting
– Whether there are toilets
– Whether there are fees to use the facility
– Etc

We would then enter responses for each location on its page, and then the search function would need to be able to parse that saved information?

Is that possible using Location Attributes; or, am I not seeing a better way of accomplishing this???