Troubleshooting

If the playlist does not populate, double check to make sure that you have not manually edited the HTML / PHP code that the Customizer tool output. Use the Customizer tool again to make any modifications to the file.

Access wimpy.sql.php directly with your web browser to see if you get any errors.

Example:

http://www.yoursite.com/wimpy.sql.php

Often times there is a username and password misconfiguration in the wimpy.sql.configs.php file. accessing wimpy.sql.php directly will display errors if there is an issue with the config settings, or any issue connecting to the database.

Double check your configs.

Check to make sure that the "public user" defined in wimpy.sql.php has enough privileges to access the database you've defined in the configs.

Try accessing wimpy.sql.php with a query string.

Example:

http://www.yoursite.com/wimpy.sql.php?queryWhere=myid&queryValue=28

If the result looks like:

&totalitems=0&datasetup=&my_filename=...

It could be that you are not using a proper queryWhere or a proper queryValue. Double check that your using the proper information.

If your getting something similar to:

&item0=28|http%3A%2F%2Fwww.yoursite.com%2Fwimpy_build%2Ftest%2Fwimpy_mp3 ...

This is good,, double check myWimpy.php for any modifications you may have done. (Or you may want to use the Customizer tool again). You can refer to the "myWimpy.php" file that came in the MySQL connection script package -- upload it to the same folder as wimpy.swf and give it another whirl.

When using the Customizer tool:

Be sure that you are setting "Wimpy Script" to wimpy.sql.php

Double check that none of the following options are used:

Do not use:

Embedded playlist
Encrypt HTML
Force XML playlist (forceXMLplaylist)
Play Icecast stream (icecast)
Startup folder (startDir)

If you're using a wimpyConfigs.xml file.

Try removing the wimpyConfigs.xml file and just get things running through standard HTML. Once things are working with standard HTML, you can go back and work out how to set up the wimpyConfigs.xml later.

Browser caching is a big problem.

Often times you get things set up wrong at first, then make some adjustments and nothing changes and things still don't work. So you try to make other changes and nothing is working. In reality the problem was corrected when you made the first change, but your browser did not retrieve the latest update to the page you modified because the page was cached locally. This can drive you bonkers. Always, always, always empty the browser cache after making a change.

Sometimes i will put a number or word on the page that i am editing, and after each change, i change the number or word, so that when i refresh the page, I can see if the number or word has changed, if the number or word hasn't changed, I know that the browser is still using the file in the cache and not the new file.

I recommend using FireFox during development, there are tons of great "plugins" that **really** empty the cache and ensure that you have the latest HTML. Plus the default "clear cache" works just great (unlike Safari or Internet Explorer).