Forum Replies Created

Viewing 15 replies - 1 through 15 (of 34 total)
  • Thread Starter NickCorcodilos

    (@nickcorcodilos)

    Thanks, that’s exactly what I was looking for – your entries in the wp_options table. Now I can clear out all the garbage some other plugins created and did not remove upon deletion. I’m happy to rate your plugin!

    Thanks, Andrew. I was using reCaptcha by BestWebSoft. Tried everything – couldn’t get error to stop. As you suggested, I tried a different plugin that also uses Google reCAPTCHA and it works fine: “Advanced noCaptcha & invisible captcha”

    I’ve been having the same problem. We use the plugin only for Comments. After a user types a “reply comment” and clicks Submit, they get “Error: You have entered an incorrect reCAPTCHA value. Click the BACK button on your browser and try again.” This happens to admins, too. When click BACK, the comment that’s waiting to be submitted is no longer in a box as a Reply – it’s now a new comment.

    We tried changing reCaptcha version from 3 to 2 – no change.

    The plugin works great to block comment spam but now we’re losing lots of legit commenters. Thanks for any help!

    Thread Starter NickCorcodilos

    (@nickcorcodilos)

    Thanks! That worked!

    I get the same problem. The link in the confirmation e-mail generates a page not found (404) error. Plugin doesn’t work. WP is up to date.

    richard – thanks for your testing and explanation. I don’t have 4.1.5 in my archive. Can’t find it online. Any idea where we can get the older version? I’ve uninstalled 4.1.6 because it locks me out of my dashboard, but I hate running without it! Thx again!

    @bestwebsoft: I have the same problem – but please note that your explanation doesn’t make sense. My server runs php 5.5.25. The plugin started failing after I did the last WordPress update (to 4.4).

    Please revisit this and advise. Thank you. It’s a great plugin, btw. Never had a problem with it til now, but I’ve had to disable it.

    Documentation is at http://urbangiraffe.com/plugins/redirection/
    But I would not call it instructions. First thing is, the images in that file are apparently quite old – the controls don’t really look like that. A free plugin is a free plugin, but the doc should at least demonstrate a few simple setups and walk users thru them.

    Thread Starter NickCorcodilos

    (@nickcorcodilos)

    Thanks, Boz. I’m using the WordPress module – it’s not working. Could indeed be the local dev setup I have. I checked httpd.conf, and the rewrite module is set correctly. I’m going to test the plugin on a production server next. That will be telling. Thanks.

    PS – I failed to add something critical. My way of moving an old HTML site to a new WP site involves manual labor. I set up the new WP site. Added some content. Then I copied the HTML files over to the new site from the old site EXCEPT the index page. So both the new blog and old HTML pages are all in the same site. (I’m testing all this on a localserver, by the way, before I do the actual move.)

    Then I set up WP so the homepage is a new PAGE, not the newest POST. The homepage is designed as a sort of menu. It gives access to everything in the new blog, and it includes a menu to all the old HTML pages on the new site. When a visitor comes to the newsite.com, they get the menu first – that’s controlled by the redirection at oldsite.com. If they try to visit a specific page on the old site, the .htaccess on the old site sends them to the same page ON THE NEW SITE. Okay so far?

    The old pages are STILL HTML pages on the new site and anyone trying to access them at the old URLs (especially via links or bookmarks) will still find them. Here’s the heavy labor. I’m going to manually copy/paste each old HTML page into WordPress as PAGES. This also lets me edit/improve/update them as I go. As I recreate each old HTML page in WP, I’ll use a redirection plugin (probably Redirection) to get visitors to the new version of the material. A lot of work? Maybe. But I believe it will work well.

    Hope this helps you in your own endeavor. It actually helped me to write it out! Good luck! I’d love to know what you do and what you learn.

    My hosting company, KnownHost, gave me the best solution, which is so easy I want to cry. No plugin is necessary to redirect an old HTML site to a new WP site.

    The key is, you control redirection from your OLD site, not the new one – so no plugin is necessary. If your old site is on same server as new site, all the better. If your old site has cPanel support, this is a piece of cake. (I think this may require that your server is Apache, but not sure. I’m not a tech savant.)

    Go into old site’s cPanel, under Domains, go to Redirects. You give it the old site, the new target location, and cPanel writes code to your .htaccess file on the old site. You can apparently delete everything from the old site EXCEPT the .htaccess file, which is where the redirection code resides.

    The great thing about this is, it does a “wildcard” redirect. Every subdirectory and file within the URL you specify gets redirected to the new URL.

    If your old site doesn’t have cPanel, you’d have to figure out what it writes to the .htaccess file to accomplish the redirection.

    If you think about it, you MUST do the redirection from your OLD site, otherwise, how would a user’s browser know where to be redirected? The new site cannot possibly control this.

    I hope this helps you out. It seems the Redirection plugin is really only good for redirecting URLs within one WP site. If it does more, I can’t find any info to confirm it.

    While I’m at it, I’ll give a plug to KnownHost, my new hosting service. I love them. Their tech support is outstanding. They go way beyond the call of duty in supporting WP issues I’ve had. That’s who helped me with this.

    Here’s some great source info:
    https://documentation.cpanel.net/display/ALD/Redirects

    Good luck!

    I’ve been researching the same thing – how to redirect an old HTML site to a new WordPress site. Instructions about the available plugins (one called redirection seems to get great reviews) seem to suggest you put the plugin on the new WP site, and redirection is taken care of.

    Pardon my newbie-ness, but this makes no sense. If someone uses a browser to go to the old HTML website, a nameserver directs it. How does adding a plugin – or even doing this via .htaccess on the new site’s server — redirect the person to the new site?

    I may be missing something here – pls educate me. I don’t get it. I’d really like to understand the details. Thanks!

    Big mistake to eliminate image controls for padding. A goof. An error. So please just bring those controls back. Basic controls like this are core. They should not have been taken out.

    That image padding can be done with a plugin is not the point. The point is that it was quick and easy to do image padding in any theme using the built-in editing controls. Please bring this feature back – it was quick and easy and didn’t require adding anything to a WordPress installation. This is an ease-of-use issue, not a matter of whether there’s “another way to do it.” I think lots of users have made their wishes clear. We’d like the image padding controls brought back. Thank you.

    Version 6.0 of the ShareThis plugin seems to fix this problem. In the old settings, it didn’t matter whether you checked the feature ON or OFF — it still appended the hash. Now if you check the feature OFF, the copied text is clean. Just update your ShareThis plugin.

Viewing 15 replies - 1 through 15 (of 34 total)