laurenbersaglio

Okay, that’s all I was wondering, thanks.

@johnny5 I realize this. Back to my original question:

Is there any way to easily export a .csv file of the blog posts and pages that have 404 issues without getting a bunch of other 404 errors that aren’t relevant for fixing?

@johnny5 okay, so going back to my initial question: is there any way to easily export a .csv file of the POSTS (i.e. blog posts) and pages that have 404 issues without getting a bunch of other 404 errors that aren’t relevant for fixing?

I have someone who is ready to help create a spreadsheet of 301 redirects to upload to the site, but without a way to easily export the posts/pages that are having issues, we won’t be able to do this efficiently.

Thanks!

@johnny5 it’s found here:

Tools > Redirection > 404s (see screenshot: https://drive.google.com/file/d/1tFRMmWcfxQuXgBcc0Q87HMw77NIZoI-2/view?usp=sharing)

@johnny5 thank you for your quick response! There is nothing I can think of that could be interfering…we do have other plugins, but other than Yoast SEO, none that deal with redirects. We also manage our Redirects directly through your plugin, so I don’t think Yoast would be interfering.

I do realize this feature is in BETA (I was so excited when I saw it!) and I hope /%postname%/ to /%category%/%postname%/ is something it will be able to support!

One thing to note: (and this was the case before trying the new BETA feature), as long as there is an input of anything in the /%category%/ part of the string, a redirect directs to the proper location. For example, if you put liberomagazine.com/mental-illness-stigma-its-time-to-talk/ nothing happens, but if you put liberomagazine.com/ANXIETY/mental-illness-stigma-its-time-to-talk/ it will redirect to the appropriate URL: https://liberomagazine.com/MENTALHEALTH/mental-illness-stigma-its-time-to-talk/

I’m not sure if this offers any valuable insight but thought I’d share this information in case it does.

Let me know if there is anything else I should try as I’m anxious to try and get it to work.

Thanks again!

• This reply was modified 4 years, 1 month ago by laurenbersaglio.
• This reply was modified 4 years, 1 month ago by laurenbersaglio. Reason: formatting

Thank you so much! This info was definitely helpful! Since a complete redesign is planned, the owners have decided to simply revert to the parent theme and not use the child theme. Once I switched away from the child theme, all of the contact forms are working with recaptcha V2.

I appreciate the help!

UPDATE: I made a silly mistake. When in troubleshooting initially, I forgot to enable this plugin (I only enabled Contact Form 7) — I apologize. It was my first time using the troubleshooting plugin and it was a rookie mistake.

That being said, I now see where our current theme is missing </html> — once I enabled a default theme it worked. In addition, once I enabled Organic Nonprofit (our parent theme) it worked.

It seems the error is with our Child Theme. When I enable the child theme, that is when </html> disappears and the recaptcha no longer works.

I know this may be outside of your scope of support, but any chance you could let me know how to add </html> to the end of our child theme?

Hi, it’s not a plugin conflict issue, either; as my previous message said, I had everything disabled — all plugins and non-default theme — and the issue persisted.

I enabled Debugging and received this error message:

Notice: Undefined index: rcommentid in /www/wp-content/plugins/wp-recaptcha/recaptcha.php on line 348 Notice: Undefined index: rchash in /www/wp-content/plugins/wp-recaptcha/recaptcha.php on line 349

Thanks I will look into all of this and get back to you!

If it’s a theme issue, then why is it that when in troubleshooting mode I disabled the theme and activated the default WordPress theme and the issue persisted?

I have sent one, thanks. However, due to the nature of the error, there is not much to show in a screenshot as all looks normal but clicking on “select color” or one of the suggested colors simply does nothing.

Thanks, @data443, unfortunately, I’ve had to disable the entire GDPR Framework plugin as it is not compatible with GIVEWP (our donation platform) and glitches with the STRIPE gateway. I hope this will be fixed in the future!

Thanks for including this fix in your update. I have not tried it yet, but will (I was using @davidhorizon’s fix)

I am having the same issue only with all my donation forms (I use GiveWP). I have no idea how much money in donations I’ve lost as I just discovered the bug today after using the plugin for a couple of months.

Error is: “ERROR: You need to accept the terms and conditions to post a comment.”

I am having the same issue only with all my donation forms (I use GiveWP). I have no idea how much money in donations I’ve lost as I just discovered the bug today after using the plugin for a couple of months.

Error is: “ERROR: You need to accept the terms and conditions to post a comment.”