billseyLCIS

Temporarily I’ve regressed the site to PHP 5.6 and the upgrade completed…

You have to manually edit file.php to change line 159 to:

if ( empty( $filename ) || ‘.’ == $filename || DIRECTORY_SEPARATOR == $filename ) {

and things will then work with Windows. When is this going to go into the base code?

4.3.1 and the problem is not yet fixed for Windows hosts. You have to manually edit file.php to change line 159 to:

if ( empty( $filename ) || ‘.’ == $filename || DIRECTORY_SEPARATOR == $filename ) {

and things will then work with Windows. When is this going to go into the base code?

Finally found the thread with the fix, which will likely break again with the next update…

file.php line 149:
if ( empty( $filename ) || ‘.’ == $filename || DIRECTORY_SEPARATOR == $filename ) {

Remember that Windows uses a backslash separator, not the forward slash that’s hard coded into the current code.

OK, so I did a manual update to WP 4.2.3 from 4.2.2 on the empty site and I still get the same error when trying to update the plugin.

Been a week or so and the problem persists. Does anyone have any idea what I can do to get it fixed?

And it looks like there’s an update to the base WordPress available, which also doesn’t install with the same error.

Heheh, I am my host. That’s why it was so easy to bump it up to 256M from the default. The update is supposed to be happening via FTP… When I look at the FTP server log files I see that the script:

1. logs in
2. sets PASV mode
3. NLST – tries to list the local filesystem folder for wp-content (not available since you only have relative paths from the root of the WP install)
4. PWD (returns ‘/’)
5. CWD – again, trying to get to the filesystem path (fails)
6. sets PASV mode again
7. NLST ‘/’ (succeeds)
8. CWD ‘/’ (succeeds)
9. PWD (returns ‘/’)
10. CWD ‘/’ (succeeds)
11. PWD (returns ‘/’)
12. CWD ‘/’ (succeeds)
13. sets PASV mode again
14. LIST -a (succeeds)
15. CWD ‘/’ (succeeds)
16. SYST (succeeds with ‘UNIX emulated by FileZilla’)
17. sets PASV mode again
18. NLST – tries to list the local filesystem folder for wp-content/plugins (still not available)
19. PWD (returns ‘/’)
20. CWD the filesystem path for plugins
21. PWD (returns ‘/’)
22. sets PASV mode again
23. NLST ‘/’ (succeeds)
24. CWD ‘/’ (succeeds)
25. PWD (returns ‘/’)
26. CWD ‘/’ (succeeds)
27. PWD (returns ‘/’)
28. CWD ‘/’ (succeeds)
29. sets PASV mode again
30. LIST -a (succeeds)
31. CWD ‘/’ (succeeds)
32. sets PASV mode again
33. NLST ‘/wp-content/’ (succeeds)
34. PWD (returns ‘/’)
35. CWD ‘/wp-content/’ (succeeds)
36. sets PASV mode again
37. LIST -a (succeeds)
38. CWD ‘/’ (succeeds)
39. sets PASV mode again
40. NLST filesystem path to the web root (fails)
41. PWD (returns ‘/’)
42. CWD filesystem path to the web root (fails)
43. PWD (returns ‘/’)
44. sets PASV mode again
45. NLST ‘/’ (succeeds)
46. CWD ‘/’ (succeeds)
47. PWD (returns ‘/’)
48. CWD ‘/’ (succeeds)
49. PWD (returns ‘/’)
50. CWD ‘/’ (succeeds)
51. sets PASV mode again
52. LIST -a (succeeds)
53. CWD ‘/’ (succeeds)
54. PWD (returns ‘/’)
55. CWD ‘/wp-includes/’ (succeeds)
56. PWD (returns ‘/wp-includes/’)
57. CWD ‘/’ (succeeds)
58. sets PASV mode again
59. NLST ‘/.maintenance’ (fails)
60. PWD (returns ‘/’)
61. CWD ‘/.maintenance/’ (fails)
62. PWD (returns ‘/’)
63. RMD ‘/.maintenance/’ (fails with 550 Directory not found)
64. disconnects

Now, if I ignore the lack of optimization, the error hits when it tries to remove the non-existent directory called ‘.maintenance’. I assume that the existence of that directory turns on Maintenance Mode for the site. It’s possible something else is the culprit, but it hasn’t actually uploaded the new version yet at this point that I can see.

I just checked it out, even with the triple ‘=’ sign (I think that’s a bug, but I’m not a PHP guru so it might be valid) and it’s not working. I still get the error with either trying to update the Twenty Fifteen theme or trying to update the core.

And then I got a brainstorm! I’m running on a Windows server, so path names use a backslash instead of a forward slash. I changed the ‘fixed’ code from

|| '/' === $filename
to

|| ‘\\’ === $filename
and it seems to have worked.