Jim Reading

Thomas —

Thank you for the code that might solve this problem. Could you tell us specifically where to add the code?

Edit: Never mind — I just dropped it into my “functions” file & (so far) everything works fine — no more validation error.

Thanks!

• This reply was modified 6 years, 9 months ago by Jim Reading.

On the front end, I hit Caching –> Purge All, and it still doesn’t update. Then when I return to working on the site the next day, the updates show up…

…The CSS is definitely being changed. I know this because I logged into my web hosting account to see if the CSS file has been updated there. It has.

Yet when I refresh my page the CSS hasn’t taken effect. (I use a hard refresh, using Ctrl F5, or Ctrl update button in chrome, or Caching –> Purge All, still no luck.)

As an experiment, I made a change to an element that I have updated with CSS in the past. I just wanted to see if I’m targeting the elements correctly. Even that element which updated fine in the past doesn’t update immediately, so I know there’s no problem with how I am applying CSS… the problem is either WordPress or Chrome.

Turns out it’s just the radio buttons that remain “required”. Are radio buttons automatically “required” fields?

Sorry for the late reply. An update: it appears that the problem is occurring with just one of my email addresses. With the others, autofill works normally (completes just one field).

Since this seems to affect just one email address, I’m going to assume it’s just a Chrome problem & do some further testing.

I’ll update this thread as I learn more about the problem.

Just fyi — It works fine on my iPhone (using Safari) & my Kindle Fire.

Okay — This might not be the solution to your problem, but it was the solution to mine:

When I copied my secret key, I double-clicked to select the whole thing. Google’s page is somehow set up so that if you double-click on the key, you also get the next darn line of text (in my case “Step 1. Client side integration”)… So I was entering aaall that as my key, which of course made it fail.

Once I entered my key correctly, everything worked fine. Hope this helps everyone else.

I’m having the same issue as everyone above. Works fine without the widget. If I add the widget & I get the following message: “An error occurred while sending the message. Try again later.”

I’ve tried:

1. Following the Contact Form 7 instructions here: https://contactform7.com/recaptcha/.
The result: Message doesn’t send if I don’t check “I’m not a robot.” Says “Please verify that you are not a robot.” Good. However the message fails to send if I do check the box.

2. Adding the Google script (<script src=’https://www.google.com/recaptcha/api.js’></script&gt;) to the head of my page, per the Google Recaptcha set up instructions, and using the ContactForm 7 “[recaptcha]” widget.
Result: If I don’t click the box, “please verify that you are not a robot”.
If I click the box, message fails to send.

3.Adding the Google Recaptcha site key to the form, per Google Recaptcha set up instructions, instead of the Contact Form 7 widget.
Result: If I don’t click the box, the form sends the message anyway. And if I do click the box, the form also sends the message.

I should also note that the reason I’m trying to use Recaptcha is because my form was somehow hacked. I received quite a few bounceback messages that look as if some bot was registering people’s email addresses to my form. I have no clue what messages the people were receiving from my form, but I imagine that the hackers were somehow using the autoresponder on my form to spam other people.

• This reply was modified 7 years, 6 months ago by Jim Reading.

Nevermind. I figured it out. Email problem, not plugin problem.

My PHP version is 5.4.43, by the way, and my WordPress version is 4.4.2.

Thanks catacaustic.

Thanks andrew. You’re right, “prevent” isn’t the right word.

What I meant was if the bot can’t find wp-admin (because it’s in a different folder than expected), it cannot launch a “brute force” attack.

I’m guessing that is the only value of using the subdirectory: hiding wp-admin from a brute-force attack.

Besides that, is there some other security value in using a subdirectory?

(Btw, I looked at the link you posted, and I do plan to take other steps to secure the site…)

Thanks jon.

Yes I understand that the site will look like it’s in the root.

Yesterday, I tried putting WordPress in a subdirectory and ran into trouble. I also worry that when I try to migrate my finalized site from localhost, I’ll have too much weird stuff going on with images etc. if I use a subdirectory.

If the only security a subdirectory adds is preventing bots from doing a “brute-force” or “dictionary” attack at wp-admin, I’d rather skip using a subdirectory.

After all, I’m diligent about password security and I plan to take other security steps.

…So am I correct in assuming that the only help the subdirectory provides is thwarting “brute-force” attacks from bots? …Or are there other things bots can do if they find my wp-admin page?

Thanks for your insights.

Not sure if you’re still checking this thread or not, but I achieved what you’re looking to do by just replacing everything inside the “site-info” div with my text.

The Simone theme probably has built in ways to alter that content using widgets and such, but on my site I just went ahead & did it by changing the code.

…So your new code will look like the code below.

<?php
/**
* The template for displaying the footer.
*
* Contains the closing of the #content div and all content after
*
* @package simone
*/
?>

</div><!-- #content -->

<footer id="colophon" class="site-footer" role="contentinfo">
<?php get_sidebar( 'footer' ); ?>
<div class="site-info">

<p>? 2015 Alina Tichacek</p>

</div><!-- .site-info -->
</footer><!-- #colophon -->
</div><!-- #page -->

<?php wp_footer(); ?>

</body>
</html>

(Btw, I’m presuming that you’re editing a new footer.php file for the child theme, and not the original file… That is, I assume that if you’re playing with the code, you know enough to do that… If not, look the theme over to see if there’s a way you can insert that content using widgets…)

YESSS! That worked. Thanks Stephen!

The nuclear approach is cool because I’m enqueuing a custom style sheet for this front page only. It shouldn’t affect the rest of the site (I think). :^)

Btw,

.services-lede a{
text-decoration: none;
}

…doesn’t work, but…

.services-lede a{
background:yellow;
}

…works. :^(