condor111

Fixed and yes it was human error thanks Dave I looked at this too quickly and then relooked again today it was the smtp key I was making. not the API

https://a.supportally.com/i/XFhuuK

• This reply was modified 1 year, 4 months ago by condor111. Reason: added link for others

Hi David yeah that is the catch 22 on this one since I set up two prior to this install and they worked as directed. Everything in the tutorial has been done. I even created new API keys before and after changing the DNS requirements. That is why I am baffled. the two other sites worked perfectly. I will recheck all SPF DNS DMIK settings. It is crazy.

Hi right, I found that and now have changed the review to not include that part. The more I use this the more I learn about what can be done and it eliminates so many other plugins that were needed before I found you. Thanks

How I fixed this issue: I had tried an older version of WP no help, but I was deleting my database and renaming it the same thing and that could have been an issue. so I created a database with a different name but used the same user and credentials.

I use backupbuddy to import the theme and wp. it gives you the option to rename the file the database if built in. not sure if the WP version allows for this.

so instead of wp_ I changed it to cm_ and the config installation warning and url redirect left for good.