adapt our existing Wordpress plugin to make sure it will be indexed by wordpress here : https://wordpress.org/plugins/

this is what you can add in the offer [10:56] We are looking for someone to fix these issues in our WP plugin code: ## Please use wp_enqueue commands Your plugin is using <style> and/or <link> tags to insert CSS/JS You should be using the built in functions for this: [login to view URL] [login to view URL] If you're trying to enqueue on the admin pages you'll want to use the admin enqueues [login to view URL] [login to view URL] [login to view URL] echo '<script src="[login to view URL]"></script> That should use enqueues. ## Please sanitize, escape, and validate your POST calls When you include POST/GET/REQUEST calls in your plugin, it's important to sanitize, validate, and escape them. The goal here is to prevent a user from accidentally sending trash data through the system, as well as protecting them from potential security issues. SANITIZE: All instances where generated content is inserted into the database, or into a file, or being otherwise processed by WordPress, the data MUST be properly sanitized for security. By sanitizing your POST data when used to make action calls or URL redirects, you will lessen the possibility of XSS vulnerabilities. You should never have a raw data inserted into the database, even by a update function, and even with a prepare() call. VALIDATE: In addition to sanitization, you should validate all your calls. If a $_POST call should only be a number, ensure it's an int() before you pass it through anything. Even if you're sanitizing or using WordPress functions to ensure things are safe, we ask you please validate for sanity's sake. Any time you are adding data to the database, it should be the right data. ESCAPE: Similarly, when you're outputting data, make sure to escape it properly, so it can't hijack admin screens. There are many esc_*() functions you can use to make sure you don't show people the wrong data. In all cases, using stripslashes or strip_tags is not enough. You need to use the most appropriate method associated with the type of content you're processing. Check that a URL is a URL and don't just be lazy and use sanitize_text please. The ultimate goal is that you should ensure that invalid and unsafe data is NEVER processed or displayed. Clean everything, check everything, escape everything, and never trust the users to always have input sane data. Please review this document and update your code accordingly: [login to view URL] I know you have a sanitize_slaask() function, but it's only using sanitize_text which is not really appropriate for all things. That's why we have sanitize_key and so on and so forth.