Support » Plugin: podPress » [Plugin: podPress] Auto detect file size and doesn't work after upgrading to 8.8.9

  • Resolved jersnav

    (@jersnav)


    After I upgraded to 8.8.9 it seems that the auto detect size and time features do not work any more. Anyone else having this problem?
    Thank you!
    Jeremy

Viewing 15 replies - 1 through 15 (of 39 total)
  • Plugin Author ntm

    (@ntm)

    Hi Jeremy,

    please, try the ID3 tag detection (ID3 Tag Info: [Show] – click on Show). This function might show a error message which could help to solve that problem.

    Regards,
    Tim

    Thanks for the help Tim!

    When I click the “Show” button it seems to endlessly search for the info without finding it. No error message is displayed.

    However I did copy the following out of the “File Size” and “Duration” fields after clicking the “auto detect” button. Instead of displaying the size or duration it seems to populate the field with an entire page of code:
    [Moderator note: snipped code block, please use the pastebin as per the Forum Guidelines]

    Plugin Author ntm

    (@ntm)

    Jeremy,

    I’m sure that the content of the File Size and Duration field is helpful. Please, use that pastebin. I will take a look at the code there.

    Thanks,
    Tim

    Thank you! Here is link to postbin http://wordpress.pastebin.com/download.php?i=EwJD4Rrf
    Jeremy

    Jeremy,
    The last line in the text you posted is:
    `<!– WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! –>’
    Have you tried disabling the “WP Super Cache” plugin (and other plugins that might be conflicting) to see if it fixes the problem?

    -Ray

    Plugin Author ntm

    (@ntm)

    Jeremy,

    is the code you have posted at pastebin.com from the file size field or from the duration field?
    Is the code in both field the same?
    The procedures behind these two buttons are different and it possible that they produce different error messages.

    BTW: it is the code of the 404 “Page not found” page of your blog.
    I agree with Ray. Maybe you should fix the WP Super Cache plugin first or deactivate it temporarily to test if it makes a difference. Maybe deactivate temporarily the other plugins too. But start with the Super Cache plugin.
    Please, check also the permissions of the podPress files and folders. For instance the permissions of the files podpress_backend.php and podpress_admin_functions.php should be set to 0755. But that this is a permissions problem seems less likely.

    Regards,
    Tim

    Plugin Author ntm

    (@ntm)

    Jeremy,

    which role has the user account which you have used to auto detect the file size and the duration?
    In general it will work only if it is an Editor or Administrator account (level_7).

    Regards,
    Tim

    Plugin Author ntm

    (@ntm)

    Jeremy,

    if you know that this has something to do with the user level or role then you could try the current Development Version (8.8.9.2 RC 1) of podPress and take a look at this thread: http://wordpress.org/support/topic/plugin-podpress-auto-detect-file-size-and-doesnt-work-for-contributor

    Regards,
    Tim

    Hey All,
    Thanks for the help.
    This error seems to be occuring only on sites I have hosted at Host Gator. My other WP installations at another server are working ok in this regard.

    To try to narrow down problem here’s what I’ve done:
    I just installed a fresh copy of WordPress on a brand new domain at HostGator and am getting the same problem. I have not installed Super-Cache or any other plugins except PodPress.

    Here are the error messages that appear in the respective fields on this new installation. They appear to be the same.

    File size error message
    http://wordpress.pastebin.com/download.php?i=QsScn0Zx

    Duration error message
    http://wordpress.pastebin.com/download.php?i=WGvrUtnV

    Regarding user level, I am logged in an admin.
    Regarding file permissions I changed all to 755. Most were 644.
    Interestingly the Podpress files seem to be 644 on my other host (Apollohosting) and things are ok there.

    Thanks again for the help!
    Jeremy

    Plugin Author ntm

    (@ntm)

    Okay, the problem is not caused by other plugins.

    They appear to be the same.

    I agree. Both code snippets seem to be the front page of the blog. This and your observation that it seems to be limited to a certain hosting provider makes me think that might be related to some entries of the .htaccess file. if this file exists, you can find it in the same folder as the wp-config.php file (root directory of the blog). (It might be a hidden by the default view settings of your FTP or SSH program.)
    Does this file exists? Is it empty? What is content? Is the content different compared to the content of .htaccess of the blog where the auto detection works?

    Besides this you could also try to activate the Log function of podPress which logs the activities of the auto detection process.
    In order to do that you need to edit the podpress.php file.
    This file includes the line:
    if ( ! defined( 'PODPRESS_DEBUG_LOG' ) ) { define( 'PODPRESS_DEBUG_LOG', FALSE ); }
    change it to
    if ( ! defined( 'PODPRESS_DEBUG_LOG' ) ) { define( 'PODPRESS_DEBUG_LOG', TRUE ); }.
    This should create a log file in the folder of podPress with the name podpress_log.dat or a different error message in the file size field.
    This may happen because the script needs the permission to create and write into this log file. This sometimes not allowed.
    The log file will probably contain file and folder names of your blog. If you don’t want to post the content of this log file at pastebin then you may send it via email to me (timberge at cs dot tu-berlin dot de).
    You can watch the status of this DEBUG constant at the general settings page of podPress.

    Regards,
    Tim

    Here is pastebin link to error log:
    http://wordpress.pastebin.com/download.php?i=3DwiD7P2

    Regarding .htaccess, the file did not exist, until I enabled permalinks just before writing this message, at which point the .htaccess file appeared to be created.

    Thank you!

    Also here is the pastebin link to the two .htaccess files:
    http://wordpress.pastebin.com/download.php?i=GsTkqPsw
    It shows the file from the functioning site and the one from the site with the error.
    They appear to be the same.

    Another quick interesting item:
    If I enter a filename in the “location” field without using http:// I don’t get an error message. “UNKNOWN” is displayed. Can I upload a .mp3 to a local directory and reference it without http://.
    Most of the time I’d want to host the .mp3 offsite however.

    Thanks!

    Jeremy,
    I think you may be trying to use the filesize and duration functions with a remotely hosted MP3 file. That is not supported. You can add MP3s to your podcast using the URL but unless podpress is configured to use a local dir and local files it can’t scan them to see how long they are (using local filesystem calls I assume).

    Does that clear it up?

    -Ray
    P.S. file permissions of 644 should be fine for all the files. Normally the directory permissions are the only things set to 755. But when you have possible permissions issues (especially if you see an error like “permission denied” you may want to temporarily change the podpress and .htaccess file permissions to 666 and the podpress folder permissions to 777 because some shared hosting servers run apache as a different user than your account user. Just remember to go back to the appropriate permissions when you are done (usually 644 and 755) for your hosting setup so you don’t leave a security hole for hackers to find.

    Plugin Author ntm

    (@ntm)

    I think you may be trying to use the filesize and duration functions with a remotely hosted MP3 file. That is not supported.

    That is not completely true.
    The file size retrieval should work in almost all cases. Because podPress requests the HTTP header of the file and tries to retrieve the content-length information from the HTTP response. That does not take long and should work for local files on the server of the blog as well as for files on a remote server.

    podPress retrieves the duration from the ID3 information of the media files with the help of getID3 and it seems that the media files need to be on the same server as getID3. In order to get the duration of a remote file podPress tries to download that file to the tmp-folder of the local server or if it is not possible to create a tmp file then to a folder which is called podpress_tmp which will become a sub folder of wp-content/uploads. The downloaded file will be deleted after the duration detection.
    But if podPress is not able to create the tmp file or the tmp folder or not able to download the file then it is not possible to retrieve the duration (There is a notice near the button because a download may take some time).
    In other words podPress needs the permission to write to the local file system for the duration (and ID3 tag) detection. But sometimes this permission is not granted.
    Other limits for the duration detection are time limits like max_execution_time. But the current podPress version stops before this limit is reached.

    At least the file size detection should work and since it was no problem to create the podpress_log file, the duration detection should work for files on remote servers too – at least for relative small files.

    Jeremy, the error which you have found in the log file was helpful.
    It seems that the URL which has been submitted in this attempt was only “http://” or maybe it has been cut off somehow after the click on the Auto Detect button.
    The “Location:” has to be a full, complete URL (with http://) OR a file name which has been selected via the dropdown menu which you get if you configure the option “Absolute path of the media files directory (optional)” at the General Settings page of podPress. This dropdown menu has also the possibility to “Specify URL”. In this case you need to insert also the full URL.

    I have made some changes and the current Development Version (8.8.9.2 RC 2) catches this error and will write a custom message to the log file. This version has also some further control points which will probably help debug this problem.
    I would appreciate it if you could download the Development Version and if you could try this again. But it is necessary that you change the PODPRESS_DEBUG_LOG constant again.
    Please, use a full URL as the “Location:”.

    file permissions of 644 should be fine for all the files. Normally the directory permissions are the only things set to 755

    Ray, thank you for clarifying that. I was not completely sure about that.

    Regards,
    Tim

    @tim, thanks for clearing up my misunderstanding. For some reason I thought podpress could not get info on remote files. Did you add this functionality? It seems like it didn’t work for me years ago when I used podpress to link to some remote files.
    I understand now how podpress can get the filesize attributes for remote files from the HTTP response. But I did not realize that it actually downloaded the entire file and got the length too! Many (most) of my audio podcasts are 10MB+ and videos can be even bigger. Doesn’t this cause issues? Maybe Jeremy’s files are bigger than the PHP filesize limits? Would that matter?
    Sorry I didn’t take the time to experiment with remote files – I am running busy and it’s easier just to ask the developer!

    -Ray

Viewing 15 replies - 1 through 15 (of 39 total)
  • The topic ‘[Plugin: podPress] Auto detect file size and doesn't work after upgrading to 8.8.9’ is closed to new replies.