I’ll not answer your questions in order, but in a way that make me easy follow a logical path. I’m assuming I should be using the wp_is_mobile(); wp_is_mobile() is a good way to go. In my experience it recognizes majority of mobile devices, and if you don’t care about an ipotetic and very low percentual … Read more
I finally included the external PHP file in a WordPress function in my plugin PHP file. function get_conf_function(){ require_once(dirname(__FILE__) .”/parts/conf.php”); } Now, I can access to wp functions when I call that function (with Ajax or not).
The Problem This turned out to be a common case of needing to use stripslashes();. How did I figure this out? I logged into phpMyAdmin, navigated to the options table, found my option name, and edited it. Here’s what I discovered… s:11:”description”;s:90:”<span style=\”text-decoration: underline;\”>This is supposed to be underlined text.</span>”; So obviously my plugin is … Read more
take a look at https://tommcfarlin.com/multiple-sections-on-wordpress-options-pages/ You can… add_settings_section(“owlish_license”, “SECTION NAME”, null, “theme-options”); add_settings_section(“owlish_settings_group”, “SECTION NAME 2”, null, “theme-options”); add_settings_field(“owlish_display_notes”, “Display Notes”, “callback1”, “theme-options”, “owlish_license”); register_setting(‘owlish_settings_all’,’owlish_display_notes’); add_settings_field(“owlish_display_notes2”, “Display Notes 2”, “callback2”, “theme-options”, “owlish_settings_group”); register_setting(‘owlish_settings_all’,’owlish_display_notes2′); after you can use this wrapper on page settings_fields(“owlish_settings_all”); do_settings_sections(“theme-options”); Have a nice day.
Sounds like you are trying hard to shot yourself and you will likely succeed. Every framework has its own assumptions and limitation so if the assumptions of wordpress do not fit your needs then just don’t use wordpress for the project. If you (ok, probably the client) have decided that for reasons of cost, delivery … Read more
Handling form fields is not related to WordPress and is off-topic here, BTW I’m answering this on how to use the options table. And your code you presented here is not relevant to your question. Ok, first of all having form data into a field after submission could put you in risk of entering duplicate … Read more
You just create must-use plugin for your multisite instalation (https://codex.wordpress.org/Must_Use_Plugins), hook to post save action there (https://codex.wordpress.org/Plugin_API/Action_Reference/save_post), and inside action callback check if current user is admin/super admin (https://codex.wordpress.org/Function_Reference/is_super_admin), if so, you find current blog user with ‘author’ role (https://codex.wordpress.org/Function_Reference/get_users) and update post (https://codex.wordpress.org/Function_Reference/wp_update_post) with his ID as author ID. At least it is first, … Read more
Settings API is (also) about the modularity of the settings, settings can be removed (never heard of anyone do it but it is possible) or amended (my favorite technique right now). When you separate the HTML and PHP you are breaking the modularity so maybe the setting API should just not be used by you. … Read more
The obvious problem is that you are trusting user input (http headers) which makes your code suspicious from security POV. Other then that, no real problems with it, but my experience is that such hacks have a tendency to just move whatever problem you are trying to solve this way to another place.
So far the only solution I’ve been able to discover is to write individual customize_value_{$setting_id} filters for each and every setting I add. I hope someone knows of a better way.