Hi Matt,
I have seen that the development version does not work in your blog and could observe the same login behaviour.
In order to find more out about what is happening in your blog and why the login does not work, I have made some modifications to the current development version. All the function which are involved in the login process will save status messages in a log file if you switch on a certain PHP constant.
Besides defining the constant the plugin (the script) should be allowed to create and write to the log file. Sometimes this is allowed by default. On other servers it is necessary that the log file folder has the same owner and group as the PHP scripts (or nobody:nogroup).
A good way to define the constant is to create in the folder /wp-content/plugins/ the sub folder podpress_options/ and create a PHP file with the name pordpress_config.php in this folder. This file may contain this:
<?php
if ( ! defined( 'PODPRESS_DEBUG_LOG' ) ) { define( 'PODPRESS_DEBUG_LOG', TRUE ); }
?>
podPress recognises the file and the definition in this file and writes all its actions into the podpress_log.dat file in the /wp-content/plugins/podpress/ folder. (You may use the podpress_config-sample.php in the podPress folder. Instructions are in that file.)
You can control whether all things are setup correctly on the general settings page of podPress. The section System Information contains an info about the status of the PODPRESS_DEBUG_LOG constant.
If the constant is defined, please define a new Premium Subscriber user, login with this user and open afterwards the premium feed and (try to) login there too.
Afterwards set the constant to FALSE to prevent unnecessary load and logging actions.
Please, send me the podpress_log.dat file via email.
Tim
