moritzjacobs / wordpress-boilerplate Goto Github PK

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method NPWP_Sanitize_uploads::sanitize_filename_on_upload() should not be called statically in /Users/mo/Dropbox/LAB/htdocs/wp-testbox/core/wp-includes/class-wp-hook.php on line 300

As of 2 minutes ago I was trying to debug an issue, where wp-migrate-db returned almost empty DB dumps. Turns out, it was because of the way wpnp-sanitize-upload.php erroneosly appended a . to a tmp file that had no extension.

Fixed in latest commit 53703f1

Update your projects accordingly

It would be beneficial to install Wordpress into its own (sub)directory.

Pros:

• The working tree of this project remains clean
• This project can be split up into multiple files (styles, classes, template files)
• The resulting Wordpress installation is clean, no files need to be deleted

Cons:

• The resulting Wordpress installation needs to be moved or the server config needs to be updated to the new web root