Error importing data from Yoast

Actually, I DID find the error … in the wp-admin dir. Why? Because it in fact it’s not a php error, it’s an error integrating with Elementor (I guess). Not going to get into it or show you the error. Plugin isn’t ready for prime time. Too bad, there is definitely a space for a “simple SEO” plugin.

@billhector I am very confused about your comments. Simple SEO does not redirect anywhere. Nor is it phishing for information, you can check the code. I’ve tested the import functionality up to PHP 8.1 without issue.

please explain what is redirecting, and please supply the error you received. I can than better assist you.

@coleds On trying to import Yoast data the action redirects to this link

https://wp.coleds.com/wp-admin/admin-post.php?action=sseo_yoast_import

You can find this link in your options code here:

~/Downloads/cds-simple-seo/app/Admin/Meta/Options.php:33: 		echo '<div class="notice notice-info is-dismissible"><p>'.__('Please').'<a  target="_blank"> '.__('donate to Simple SEO').'.</a> or <a href="https://www.ads-software.com/support/plugin/cds-simple-seo/reviews/" target="_blank">'.__('Leave a Review.').'</a> Or Both! Please email <a href="mailto:[email protected]">David Cole</a> with any questions.</p></div>';
~/Downloads/cds-simple-seo/app/Admin/Meta/Options.php:244: 		$content .= '<a  class="button button-primary" onclick="return confirm(';
~/Downloads/cds-simple-seo/app/Admin/Meta/Options.php:250: 		$content .= '<a  class="button button-primary" onclick="return confirm(';
~/Downloads/cds-simple-seo/app/Admin/Meta/Options.php:256: 		$content .= '<a  class="button button-primary" onclick="return confirm(';

I can’t recreate a php error again, but there was one having to do with Elementor, which doesn’t seem to do with the above.

I’ve been using WP since version .8. You are not dealing with a piker. I’m not a developer, but I know my way around WP. This is an intentional act.

Good luck, pal.

@billhector Thank you for sharing your findings. coleds.com is my main domain for my business. the wp subdomain is my testing environment for Simple SEO and other WordPress plugins I develop. Apparently in the code it is set to go to these URLs instead of the website URL where the plugin is installed. This is an error on my part, not a phishing scam. I will correct it on my next update.

I am aware of a Elementor error with PHP 8+, but not one that involves Simple SEO. If you have this information please send it so I can further debug. I have tested Elementor and Simple SEO on PHP 8.1 without issue.

Simple SEO is not integrated (yet) into Elementor. Errors regarding Elementor will need to be addressed to those developers.

@billhector The issue of the redirects has been resolved. test of the import functionality is 100% working. Thank you for pointing out I left the testing domain URL in the import button HTML. This explains why it worked for me, but not you. Thank you.

@coleds Thanks for the apology (?). Still deleted. Not sure (don’t care) why someone would hard code URLs into a plugin dev and not be using variables. Too bad. As I said, there is definitely a space for this type of plugin (a SEO plugin without feature bloat). The search continues …

@billhector This was not an apology. It was a statement that the issue has been resolved.

Further more, and for the public to know, I have reported you to WP administration. Frankly you are a rude person, quick to judge, and not at all concerned with others. A simple report of the coding error and giving me time to resolve it would have avoided all this “drama” you post.

The issue is resolved, I appreciate that you found the coding issue and let me know; even though it was after your rash claims of phishing and a negative review.

@coleds Duh. I know you didn’t apologize (I was just pointing out that you didn’t).

I was rude? Hothouse flower, you are. Actually, I am very concerned with others, that’s why I took the time to point out this issue and not just delete the plugin immediately.

Dude, I didn’t say anything, but when I found your hard coding I already reported this plugin as a security risk. Way ahead of you! Best of luck.

OK, folks. Moderator here… Let’s cut this out. There was a problem; it’s been solved. No need to go on calling each other names, attribute bad intentions, or anything else. The “win” is to get get a working solution, not to demean the other person. Step back; no need to reply to me or each other. Also, Bill, I see no security issue here.