Michael Ecklund

Forgot to mention… I of course have full permissions of the account and properties.

A simple solution to Yoast on this one:

Limit this feature to the first time the user visits any settings page related to your plugin after install/update. THEN redirect to this: Thank you // What’s new // Overview // what ever page. Your users are still forced to see this page before configuring plugin settings.

That way you’re not totally hijacking WordPress; Especially after bulk updating plugins.

NGG is adding that snippet via anonymous function, which is super annoying by the way.

Thankfully there is a temporary solution by @toscho on WordPress Stack Exchange.

Copy his function and paste it into your currently active WordPress theme’s functions.php file.

Then copy/paste this into your currently active WordPress theme’s functions.php file as well.

function kill_anonymous_example(){
    remove_anonymous_object_filter(
        'wp_footer',
        'C_Photocrati_Resource_Manager',
        'print_marker'
    );
}
add_action('wp_footer', 'kill_anonymous_example', -2);

That removed it and my feed works again.

Thanks for responding. I wasn’t sure what the intended functionality was.

I’m not sure if WordPress SEO plugin respects the public or publicly_queryable parameters of register_post_type() arguments. In theory, it should. So if you set those parameters to false, maybe the WordPress SEO plugin (among other plugins as well) won’t automatically create sitemaps for that post type.

Although, I don’t know how that would effect the functionality of your plugin.

@photocrati

Using WordPress multisite 3.6

Tried v2.0 and Beta 2.2 of your plugin.

Getting errors like:

Warning: Invalid argument supplied for foreach() in /wp-includes/query.php on line 1702

Caused by your plugin I believe. When disabled, errors disappear.

PLUGIN CONFLICT

WordPress Version 3.6
Better WP Security Version 3.5.5
NextGEN Gallery by Photocrati Version 2.0.0

Issue:
NextGen “Gallery Settings” and “Other Options” pages stopped displaying content on the admin page after saving settings once. (odd — displayed fine before saving settings)

Temp Fix:
Navigate to: Dashboard -> Security -> System Tweaks

Uncheck “Prevent long URL strings” under “Other Tweaks” and save changes.

Solution: WordPress Social Login : Unspecified error. #6 With Twitter

Incorporate The Ultimate htaccess Blacklist from Perishable Press.

Upgraded both plugins to latest versions.

Dashboard -> Performance -> Minify -> Rewrite URL structure (UNCHECK) -> Save all settings.

Remember to empty “page cache” afterwards.

I had the same problem… Map is displaying / functioning correctly again.

Yes. There is a solution. Not ideal, but it works. Just save the settings once. All the errors should then go away.

WordPress Version: 3.5.1
Google Analyticator Version: 6.4.2
Steps to reproduce: Dashboard -> Settings -> Google Analytics -> Save Changes
Issue: Upon saving the settings page, the following errors are displayed:
Warning: stripslashes() expects parameter 1 to be string, array given in /wp-includes/kses.php on line 1257

Warning: stripslashes() expects parameter 1 to be string, array given in /wp-includes/kses.php on line 1257

Answered from this thread.

Summary:
The .htaccess redirect for www/non-www…

# www redirect
RewriteCond %{HTTP_HOST} ^subdomain.com
RewriteRule ^(.*)$ https://www.subdomain.com/$1 [R=301,L]

Put it ABOVE your WordPress rules on domain.com. Should work.

Example:

RewriteEngine On

# DOMAIN #1 - Redirect non-www urls to www
RewriteCond %{HTTP_HOST} ^domain1.com
RewriteRule ^(.*)$ https://www.domain1.com/$1 [R=301,L]

# DOMAIN #2 - Redirect non-www urls to www
RewriteCond %{HTTP_HOST} ^domain2.com
RewriteRule ^(.*)$ https://www.domain2.com/$1 [R=301,L]

# DOMAIN #3 ... ETC - Redirect non-www urls to www
RewriteCond %{HTTP_HOST} ^domain3.com
RewriteRule ^(.*)$ https://www.domain3.com/$1 [R=301,L]

RewriteBase /
RewriteRule ^index\.php$ - [L]

# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]

Marking topic as resolved. It would be nice if someone could explain how to force a trailing slash to each of my domains as well (if not present).

Example.