I am not sure if this helpful or not. As s_ha_dum said, you should post how you are processing the submitted data and sending to db. But for starters, you might look at escaping the outputted data in the form: <input style=”width:100%” type=”text” name=”dataHow to sanitize user input?” id=”title” value=”<?php $title = get_option(‘data_test’); echo esc_attr($title[‘title’]); … Read more
You need to register/enqueue your admin scripts on admin_enqueue_scripts, not on wp_enqueue_scripts. wp_enqueue_scripts is a front end hook. It won’t run on the admin pages. Secondly, is_admin() just checks whether the page is an admin page, not whether the user is an administrator. To check whether the user is an administrator use: $current_user = wp_get_current_user(); … Read more
This Answer relates to the first version of the Question, and I don’t know how to updated it, I’ll leave it here as general reference. Don’t use a plugin folder (or a theme) for this. Maybe your plugin doesn’t have an Upgrade feature and nothing will be overwritten. But the best practice is to use … Read more
Add the jquery script as a dependency for your jquery-ticker.js and site.js files within the wp_enqueue_script function. Example: function bbc_frontend_script() { wp_enqueue_script(‘ticker’, plugins_url(“/js/jquery-ticker.js”, __FILE__), array( ‘jquery’ ) ); wp_enqueue_script(‘sitejs’, plugins_url(“/js/site.js”, __FILE__), array( ‘jquery’, ‘ticker’ ) ); } add_action( ‘wp_enqueue_scripts’, ‘bbc_frontend_script’ ); You also don’t have to enqueue jquery separately if you define it as a … Read more
If you observe how the popular caching plugins like WP Super Cache or W3TC utilize a cache folder within wp-content as well as other plugins who utilize uploads or cachable files it would be appropriate to create a folder within that structure. A side issue may arise if the user has a locked down folder … Read more
WordPress stores the currently active plugins in the options table under the key active_plugins. Hooked actions and filters aren’t stored anywhere, plugins must add their hooks on every request, otherwise they don’t exist.
I think is a better strategy, that you add on the activation a new capability and add this capability to the Administrator role. This makes possible for installations with much different roles to the WP default to add this capability to other roles or for the requirement of a installation to add the view to … Read more
Do I still need to include the update scripts in version 1.2 so people can update the plugin from v1.1 directly to v1.3? Yes. Is there a way for WordPress to automatically download v1.2, run the update scripts, and then download v1.3… No. …is there a way to flag v1.3 of my plugin and say, … Read more
The form action needs to point to options.php, which is WordPress’ built-in handler for all settings pages: <form method=”POST” action=”options.php”> This is documented fairly thoroughly on the Settings API page of the Codex.
Per comments, an alternative is to use the built-in Firefox debugger instead (Inspect Element (Q)) – it’s very good (now) and is (almost completely) unaffected by the WP heartbeat.