Forums

[Plugin: Podpress] Cannot auto detect file size/length/ID3 (5 posts)

  1. BenandHamSoup
    Member
    Posted 5 months ago #

    Hey guys,

    I've just run into this issue today after successfully uploading and auto-detecting these tags in an earlier podcast last week.

    It seems coincidental that this would occur after upgrading to WP 3.3, but nevertheless I've tried to resolve the issue through older posts (checking permissions, disabling other plugins etc).

    Anyway, I've got the error code that shows up. I wish I had more to add, but any information/help would be much appreciated!!

    The error is here:

    http://pastie.org/3029367

    That's the entire error as I see it/can copy it; the end does cut out like that.

    Again, many thanks!

    Ben

  2. BenandHamSoup
    Member
    Posted 5 months ago #

    Quick follow-up, I thought this would only be an issue for those viewing the website through wordpress and not seeing the duration/download size etc.

    The podcast has been put up on iTunes and unfortunately is currently showing 0:01 run time and no download size. This does change when the podcast has been downloaded, but on the iTunes page this is an issue. I'm guessing it's related as podpress creates the feed.

    Anyone with any help, it's much appreciated!

    Thanks,

    Ben

  3. ntm
    Member
    Posted 5 months ago #

    Thanks posting the error message (and for using this pastbin service). This error message is basically parts of the HTML code of the 404 page of your blog.
    Have you copied this code from the box which should show the detected file size or duration?

    Although I cannot say why this happens in your blog, I can say that this has most likely nothing to do with the upgrade to WP 3.3 or at least that this is not a problem in all blogs with WP 3.3 (I have upgraded to WP 3.3 and have no such problems).

    Have you installed further plugins recently?

    The Auto Detect buttons use AJAX technique to retrieve the file size, the duration and the ID3 tags. This means that a click on one of these button starts a HTTP request for a certain file of podPress which includes the necessary functions. Something stops or interrupts those requests and the result is the 404 page of your blog.
    One cause is usually that the URL of request was wrong or that the permissions which regulate the access to the file (or the folder) are to restrictive. But there are other possibilities too.
    Please, control the permissions for the podpress folder and the file within. 0644 and 0755 should be okay.
    A security plugin or a plugin which influence the Permalink scheme might be involved. That is why I would like to know which other plugins are installed and active in your blog.
    Does it change the situation if you deactivate the other plugins? (If it does make a difference, could you find out which one of the other plugins is involved?)

    There is a further mechanism to get more information about the process of retrieving these meta data from the media files.
    In the file podpress.php you can find the line (127):

    if ( ! defined( 'PODPRESS_DEBUG_LOG' ) ) { define( 'PODPRESS_DEBUG_LOG', FALSE ); }

    Change it to

    if ( ! defined( 'PODPRESS_DEBUG_LOG' ) ) { define( 'PODPRESS_DEBUG_LOG', TRUE ); }

    and podPress will try to log all actions which follow a click on one of these 3 buttons in a log file in the podpress folder.
    But this is only possible if the configuration on the server of your blog allows PHP scripts to create files and to write into files. Sometimes that is not allowed. In this case you would get different error messages and you should set the constant back to FALSE.
    But if podPress is allowed to create a log file then it would be great if would document one attempt to retrieve the file size and one attempt to retrieve the duration.
    I recommend that you set the constant back to FALSE afterwards.

    ...and unfortunately is currently showing 0:01 run time and no download size...

    You feed includes the duration and the file size data for episode 1 and 2. I guess iTunes is going to update this at least with the next episode.
    But you are right if you would not declare the duration and the file size, it is not possible to use the play button of the episode if one views the page of your podcast inside the iTunes client software. That why it is it is important to insert those values manually if the auto detection does not work.

  4. BenandHamSoup
    Member
    Posted 5 months ago #

    Thanks for the reply. I've manually changed the duration, although nothing has changed as of yet within iTunes (if it ever will).

    As far as the logging goes, I've changed that to true, but I'm unsure which log file contains all the relevant information you were looking for. Right now, it's still set to TRUE.

    As for installed plugins (and active at the moment), they include: Contact Form 7, Google Analytics, Google XML Sitemaps, Lightbox Plus, Facebook/Twitter Share buttons, Podpress, Sidebar Login, a video embedding plugin for Youtube and a twitter feed.

    Struggling to see how these would interfere as you've mentioned.

    I've checked and all the folders and files were 755 or 644 (I actually changed a few to 755 like backend etc, to no avail. So I'm still getting these errors.

    One last thing, if it's relevant. If I try to edit my earlier episode post (which successfully worked), it can't auto-detect the duration etc again, it actually fails now.

    I'm lost!! :P

    Thanks for your time and effort,

    Ben

  5. ntm
    Member
    Posted 5 months ago #

    Hi Ben,

    thank you for the list of the plugins. I will do some tests.

    The file name of the log file is podpress_log.dat and it should be in the main folder of the podPress plugin.

    That the auto detection does not work for all the file is a further detail which helps to find the problem. But I have still no concrete idea about what could be the cause of the problem.

    Tim

Reply

You must log in to post.

About this Topic

Tags