2013-08-13

Google Play Music Manager Takes a Silent Bow


Is it a crash? Is it a polite exit, like a date that goes badly but the girl has the kindness never to call again? 

Something like it seems to be going on with Google Music Manager, which is responsible for uploading files to Play's cloud music storage. The application launches, occupies its rightful place in the tray, but a mouseover event causes it to close. Nothing is thrown in the event log.

Google Support is accessible through Play help screens, using an Amazon-like Click-to-Call. On the second day of trying, contact with support was made. That was when the presence of this log was mentioned. Echelon 2 help will now take a look.

Analysis There's an application log, but the user isn't given any hints as to its location or how to interpret its contents. This is intentional, but for knowledgeable users -- equipped with a thoughtful FAQ -- some problems may be solved without help from the vendor. Whether it would help with this problem or not is unknown.

Update (28 Sep 2013) The only way to successfully re-install the application was to remove and recreate the working folder where the logs and other message files are stored. If you need the logs to later analysis, store them elsewhere before recreating the folder. The installer, probably by design, leaves the contents intact, but if there are problems there, they are never resolved. The original cause of the problem remains unknown, but the app becomes usable again after following this recipe.

C:\Users\[username]\AppData\Local\Google\MusicManager

2013-08-05

Disable Magic_quotes_gpc in PHP for Joomla 3.1 (Pair Networks)

Joomla logo
Joomla 3.1 requires that magic_quotes_qpc, a PHP setting, be turned off -- for a security reason related to PHP. As others have noted, this can be done in various ways --maddeningly -- depending on numerous configuration permutations.

How can you tell if it is turned off? Check phpinfo if the Joomla preinstallation checklist is not providing that information. 

At Pair networks, changing .htacesss and php.ini did not work. The web host technician advised using user.ini. It is worth reading the PHP documentation (and comments) regarding user.ini. This setting is apparently per-directory, in this documentation, but this StackOverflow post indicates user.ini works recursively. 

Whether this solution works for you depends on the specific configuration, so check that first.

The issue is broad in scope and complex, as pointed out in this lengthy and ongoing post by "AITPro Admin" titled "PHP5.3.X – PHP5.4.X .USER.INI FILE DOES NOT WORK – KNOWN PHP5.3.X .USER.INI FASTCGI WORDPRESS ZEND APACHE ISSUE."  Read this if you are contemplating a career in software and expect it to be smooth technology sailing.