Title: model13's Replies - page 2 | WordPress.org --- # model13 [ ](https://wordpress.org/support/users/model13/) * [Profile](https://wordpress.org/support/users/model13/) * [Topics Started](https://wordpress.org/support/users/model13/topics/) * [Replies Created](https://wordpress.org/support/users/model13/replies/) * [Reviews Written](https://wordpress.org/support/users/model13/reviews/) * [Topics Replied To](https://wordpress.org/support/users/model13/replied-to/) * [Engagements](https://wordpress.org/support/users/model13/engagements/) * [Favorites](https://wordpress.org/support/users/model13/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 16 through 30 (of 38 total) [←](https://wordpress.org/support/users/model13/replies/?output_format=md) [1](https://wordpress.org/support/users/model13/replies/?output_format=md) 2 [3](https://wordpress.org/support/users/model13/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/model13/replies/page/3/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Events Manager - Calendar, Bookings, Tickets, and more!] Events Manager Creating Subscriber Accounts on Multisite Root](https://wordpress.org/support/topic/events-manager-creating-subscriber-accounts-on-multisite-root/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 6 months ago](https://wordpress.org/support/topic/events-manager-creating-subscriber-accounts-on-multisite-root/#post-6807489) * I am absolutely certain it is every time the user loads a page — any page, not just an Events Manager page — in wp-admin. I’m also absolutely certain it has nothing to do with bookings because, as stated above, the bookings feature is completely disabled across the board. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress Importer] Error in debug mod](https://wordpress.org/support/topic/error-in-debug-mod-5/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 6 months ago](https://wordpress.org/support/topic/error-in-debug-mod-5/#post-5840628) * Came to report the same: * Strict Standards: Declaration of WP_Import::bump_request_timeout() should be compatible with WP_Importer::bump_request_timeout($val) in (path redacted)/wp- content/plugins/wordpress-importer/wordpress-importer.php on line 38 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Events Manager - Calendar, Bookings, Tickets, and more!] PHP Notices on Events Search Submission](https://wordpress.org/support/topic/php-notices-on-events-search-submission/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 7 months ago](https://wordpress.org/support/topic/php-notices-on-events-search-submission/#post-6691292) * I have WP_DEBUG defined as true on this test site, which is why the notice is displaying. WP_DEBUG is off on our production sites. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Events Manager ESS] How often does Events Manager ESS Push to other sites?](https://wordpress.org/support/topic/how-often-does-events-manager-ess-push-to-other-sites/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 7 months ago](https://wordpress.org/support/topic/how-often-does-events-manager-ess-push-to-other-sites/#post-6644043) * I’m not an expert on this plugin, but it looks like the time depends on when the feed (maybe the first feed?) was added. * You can probably tweak the time. The feed update appears to be tied to the cron job ESS_daily_event_hook. I use the WP Crontrol plugin when I need to access the hooks to edit the exact time crons are scheduled to run. * I’m running into the same situation as you are with the feed not showing up. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[wpDirAuth] Multisite questions](https://wordpress.org/support/topic/multisite-questions-5/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 10 months ago](https://wordpress.org/support/topic/multisite-questions-5/#post-5909849) * Thank you! Good idea supporting both. I set up multisite on localhost not long ago, and the hardest part was trying to reconcile the step-by-step on the screen with the instructions on the Create a Network page. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[wpDirAuth] Multisite questions](https://wordpress.org/support/topic/multisite-questions-5/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 10 months ago](https://wordpress.org/support/topic/multisite-questions-5/#post-5909847) * I believe I figured out what’s going on. wpDirAuth checks if the constant WP_ALLOW_MULTISITE is defined and true to determine whether it’s being activated for a single-site installation or multisite. * Newer versions of WordPress don’t necessarily need that constant defined. The constant MULTISITE is used instead. * The plugin itself may need an update to address this, but for a quick fix, add the following to your wp-config.php file: * define(‘WP_ALLOW_MULTISITE’, true); * I tested this on a brand-new installation of multisite that had this problem ( all our old ones were working fine), and it was resolved immedaitely. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Form Manager] PHP Undefined Index Notices on Form Submission](https://wordpress.org/support/topic/php-undefined-index-notices-on-form-submission/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 10 months ago](https://wordpress.org/support/topic/php-undefined-index-notices-on-form-submission/#post-6361457) * Oh, the response page also contains this notice. Sorry I missed it earlier. * Notice: get_userdatabylogin is deprecated since version 3.3! Use get_user_by(‘ login’) instead. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Multiple Roles] Plugin Conflict with wpDirAuth](https://wordpress.org/support/topic/plugin-conflict-with-wpdirauth/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 10 months ago](https://wordpress.org/support/topic/plugin-conflict-with-wpdirauth/#post-6353928) * Thanks, gilzow, for confirming what I was seeing and the possible solution. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Form Manager] Textarea Private Field Not Saving?](https://wordpress.org/support/topic/textarea-private-field-not-saving/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 10 months ago](https://wordpress.org/support/topic/textarea-private-field-not-saving/#post-6335210) * Thank you so much for the prompt resolution. Much appreciated. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Form Manager] no Captcha reCaptcha](https://wordpress.org/support/topic/no-captcha-recaptcha-1/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [10 years, 11 months ago](https://wordpress.org/support/topic/no-captcha-recaptcha-1/#post-6066862) * Yes, please! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] Conflicts with NextGen Gallery and TinyMCE](https://wordpress.org/support/topic/conflicts-with-nextgen-gallery-and-tinymce/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [11 years, 6 months ago](https://wordpress.org/support/topic/conflicts-with-nextgen-gallery-and-tinymce/#post-5564206) * We updated to 0.5.5.1, and I tried, without luck, to reproduce the problems we’ve been having with NextGen and TinyMCE. We updated several plugins at one time this past week, including NextGen Gallery, so our original belief that these problems were indeed caused by something else last spring is probably correct. It looks like the last round of updates fixed those bugs but 0.5.5 introduced a new one so the net change was nil. * Both NextGen and TinyMCE appear to be fully functional with 0.5.5.1, even when I disable the code I wrote to remove the filters added by 0.5.5. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[wpDirAuth] wp_setcookie is deprecated since version 2.5! Use wp_set_auth_cookie() instead](https://wordpress.org/support/topic/wp_setcookie-is-deprecated-since-version-25-use-wp_set_auth_cookie-instead/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [11 years, 6 months ago](https://wordpress.org/support/topic/wp_setcookie-is-deprecated-since-version-25-use-wp_set_auth_cookie-instead/#post-5002932) * I get the same wp_setcookie warning when WP_DEBUG is enabled. We’ve been using the plugin for years and have never had a problem with it, but we’d love to see this updated so the warning would go away. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] Conflicts with NextGen Gallery and TinyMCE](https://wordpress.org/support/topic/conflicts-with-nextgen-gallery-and-tinymce/) * Thread Starter [model13](https://wordpress.org/support/users/model13/) * (@model13) * [11 years, 6 months ago](https://wordpress.org/support/topic/conflicts-with-nextgen-gallery-and-tinymce/#post-5564079) * For clarity’s sake, just a mention that this is with Version 0.5.5 of MU Domain Mapping. However, these two particular issues predate that release. * We’re going to 0.5.5.1 this afternoon, but I had already begun patching things before it became available. We decided to hold off on the update a little longer in order to document the issues. We’re still checking on several other reports of plugin conflicts and disabled features. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] Remote login is not working with recent update](https://wordpress.org/support/topic/remote-login-is-not-working-with-recent-update/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [11 years, 6 months ago](https://wordpress.org/support/topic/remote-login-is-not-working-with-recent-update/page/2/#post-5536303) * We experimented a bit further with the code we developed after finding the removal of the filter fixed logins on two of our multisites but not the third. After more experimenting we added a few more lines: * add_action(‘wp_default_scripts’, ‘fix_remote_access’); add_action(‘wp_default_styles’,‘ fix_remote_access’); add_action(‘wp_loaded’, ‘fix_remote_access’); add_action(‘ wp_enqueue_scripts’, ‘fix_remote_access’); add_action(‘wp_print_styles’, ‘fix_remote_access’); add_action(‘wp_print_scripts’, ‘fix_remote_access’); * Every time the plugin function get_original_url() is called, which is a number of times, it removes the problem filter and then adds it back in; thus, removing the filter one time may fix some features but not all of them. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WordPress MU Domain Mapping] Remote login is not working with recent update](https://wordpress.org/support/topic/remote-login-is-not-working-with-recent-update/) * [model13](https://wordpress.org/support/users/model13/) * (@model13) * [11 years, 6 months ago](https://wordpress.org/support/topic/remote-login-is-not-working-with-recent-update/#post-5536283) * We created a must-use plugin and added two functions that have fixed nearly all of the problems we were having. Here’s the code if you want to try it out: * // Takes care of form action issues to prevent mismatch between the URL of wp- login.php and site_url(), which causes authentication to fail function fix_remote_access(){ if (substr_count($_SERVER[‘PHP_SELF’], ‘wp-login.php’)): remove_filter(‘pre_option_siteurl’,‘ domain_mapping_siteurl’); endif; } add_action(‘init’, ‘fix_remote_access’) * // Used in place of redirect_login_to_orig() // Takes care of login page URL issues to prevent mismatch between the URL of wp-login.php and site_url(), which causes authentication to fail function new_redirect_login_to_orig() { if (function_exists(‘ get_original_url’)): * if ( !get_site_option( ‘dm_remote_login’ ) || $_GET[ ‘action’ ] == ‘logout’ || isset( $_GET[ ‘loggedout’ ] ) ): return false; endif; * $thisurl = (is_ssl() ? ‘[https://’](https://’); : ‘http:/’).$_SERVER[‘ SERVER_NAME’].$_SERVER[‘REQUEST_URI’].’ ‘; $url = get_original_url( ‘siteurl’); * if (!substr_count($thisurl, $url)): $url .= “/wp-login.php”; echo “”; endif; * endif; } add_action(‘login_head’, ‘new_redirect_login_to_orig’); Viewing 15 replies - 16 through 30 (of 38 total) [←](https://wordpress.org/support/users/model13/replies/?output_format=md) [1](https://wordpress.org/support/users/model13/replies/?output_format=md) 2 [3](https://wordpress.org/support/users/model13/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/model13/replies/page/3/?output_format=md)