Barbara Feldman

I just got the same message, and it appears to be a “false positive.” I bulk edited 41 posts to add them a new category. I got the “You just changed URL…” message 3 times when the edit was complete. However, my posts do NOT include a category in the permalink, so there should not have been any URL changes made.

Also, as dslippy pointed out, the error message did not reference a specific post, making it hard to track down the actual source of the error.

The solution on my server was found in a Suhosin setting.

Suhosin is a PHP security system. In order to allow null values, I added some configuration lines to php.ini.

suhosin.cookie.disallow_nul = Off
suhosin.get.disallow_nul = Off
suhosin.post.disallow_nul = Off
suhosin.request.disallow_nul = Off

Me, too. have re-created the problem without any plugins, using default theme, and on both WP 4.4.2 and WP 4.4.1

WordPress 4.4.2
PHP Version 5.6.18
MariaDB 10.1.11
Apache 2.4

4.4.16 fixes it for me.

Thanks!

Yup. Here too:

Warning: Missing argument 1 for ITSEC_Lockout::__construct(), called …..

I worked around the problem just using a handcrafted excerpt, so the above example will not show the issue. But I did discover that it is WordPress that scrubs shortcodes from excerpts.

Mike, that did it exactly! Thank you.

And for those that want to CHANGE the search engine URL, try this:

function change_json_ld_search_url( $str ) {
$home_url = trailingslashit( home_url() );
$str = $home_url . ‘?s={search_term}&post_type=product’;
return $str;
}
add_filter( ‘wpseo_json_ld_search_url’, ‘change_json_ld_search_url’, 10, 1 );

Boom! Solved it. I knew it was something systemic … as if the plugin did NOTHING at all!

I changed permissions on /wp-content/ to 777 because that’s where the input data file is saved.

An error message would have been APPRECIATED!

??

Barbara

The products are not imported. There are no new download posts either in my WordPress control panel, nor in the database when I look for them there (post_type=”download”).

Barbara

Just to clarify the typo in my last post so that others will benefit from my lesson:

“Featured image has invalid permissions” error from the CSV Manager was resolved when I changed the featured image field from a full URL (starting with “https://”) to a relative path off the “wp-content/uploads/” folder. For me this path was “store/image.jpg”.

I also learned that the CSV Manager will import this image into the Media Library. All I needed to do was to FTP the images up to a folder below “wp-content/uploads”. And of course, set the correct permissions.

Another lesson was that the post_status field is REQUIRED, and should be either “draft” or “published” per your needs. And that the post_date field is recommended, as well as the excerpt field (even if it is blank).

One last lesson: The error “file 8 missing from line 13” means that your image file is 404.

Both problems are now solved when I changed the image field from a full URL (“https://blah-blah.com/wp-content/uploads/store/image.jpg”) to a relative path from wp-content/uploads/ (ie “store.image.jpg”).

Let me restate this a little clearer.

The wp-login hits I am seeing in my access_log ARE NOT taking advantage of the “wp-login.php?loggedout=true” loophole.

The access is straight to “”wp-login.php” … and the server is responding with a “200 all okay status code” NOT the “302 redirect to /notfound” that I see when I try and read the status code from “wp-login.php”.

@giti

I did read the comments, but the access_log is NOT showing hits to “wp-login.php?loggedout=true” … the only hits to “wp-login.php?anything-at-all” are the ones that include my WP-Better-Security secret key (and these are all legit!)

I am baffled. When I read the header response for:
https://www.mysite.com/wp-login.php
I get a 302
(which makes sense since I am HIDING the BACKEND using WP-Better-Security.)

However, in my access logs for the last 24 hours, I see about 4000 attempts to access wp-login.php that get a 200 response. For example:

1XX.1X.1XX.XX6 – – [12/Jul/2013:09:17:06 -0400] “POST /wp-login.php HTTP/1.0” 200 3880 “mysite.com/wp-login.php” “Mozilla/5.0 (Windows NT 6.1; rv:19.0) Gecko/20100101 Firefox/19.0”

How is this possible?

Of course, they are being locked out per the LIMIT LOGIN parameters, but they are still eating up my resources.

I think I am looking at a different error_log!!!

How do I verify which log it is getting? How do I modify which log it is reading?

Barbara