iggyvolz

I’ll mark this as resolved unless the issue comes back.

Odd… it now seems to be working afer I set up the debugging as you asked. It may be related to the fact that I changed my URL scheme from the default to Day and Name, or the 4.1.1 upgrade.

I do not have my httpd configured to write error logs out to the folder but rather I have it configured to send everything to the global error log, where there is nothing related to my wordpress there. wp-content/error.log does not exist.

Setting post_status to publish makes “Auto Draft” show in my “All Players” view.

This needs to be put into a patch. It’s a very simple fix, documented by doublesharp. Unfortunately WordPress uses Subversion instead of Git so there is no such thing as a “pull request”.

First of all, if you’re on a production site, you shouldn’t be seeing any error, whether it occurs or not. Make sure you’re not in debug mode (check your wp-config.php). If you don’t have debug mode enabled, add this code: ini_set('display_errors','0'); which will hide errors.

The only true errors are the notices, the warning is an error that results from the notices showing. The problem looks to be that $q_config[‘language’] is not set for some reason, which is setting off the chain reaction of errors. If your site is working fine besides the error messages, you can safely ignore it (make sure you set display_errors to 0 as described above).

That’s a bug in the qtranslate system, it should only compare the minor version (it’s compatible with 3.8.x) instead of the patch version (which is distributed with no notice whatsoever and should’t break compatibility).

This happens every time a new release is out. Because this is just a patch version, you can safely trick qtranslate into thinking that it is configured to run with 3.8.3. Change qtranslate.php line 90 from:
define('QT_SUPPORTED_WP_VERSION', '3.8.2'); to define('QT_SUPPORTED_WP_VERSION', '3.8.3');