Forums

WordPress › Support » Plugins and Hacks

12

[Plugin: podPress] podPress 8.8.5 beta testing (33 posts)

  1. ntm
    Member
    Posted 2 years ago #

    If you have the possibility to test a beta version in some kind of test blog (NOT your regular, productive blog !) then it would be great if you could try the Development Version of podPress http://wordpress.org/extend/plugins/podpress/download/.

    This beta version has a lot of minor fixes like a different layout for the video player preview or the listen wrapper for the audio player.

    But it has a major change in the part which produces the RSS, ATOM and XSPF feeds which includes a change of the option "Aggressively Protect the Feed". This includes a fix for the problem with 8.8.4 it's requirement of a relatively new PHP version and a fix which should help that non-ASCII characters in the podcast episode descriptions are displayed right in iTunes (and other feed readers).

    Please, write your experiences with the Development Version down. Good and bad. And if you discover problems then try to explain the circumstances and the details.

    In every case: Thank for testing and helping!

    Regards,
    Tim

  2. blanchbiz
    Member
    Posted 2 years ago #

    Hi Tim - I assume you are on the development team for pod Press? In previous posts I read that this plug in was not being actively developed and/or supported. In your post above, it sounds like there are current changes, correct? thanks for verifying this for me (and others) who are hoping to use the tool.

  3. ntm
    Member
    Posted 2 years ago #

    Last year, I have written some patches for the most visible problems like the problem with not working media uploader on the editor pages of the last WP versions and have contacted Dan Kuykendall (Seek3r) the original author and owner of podPress and Andrew Ozz, who is like fiduciary for this plugin.
    Dan answered my first email and told me that would try to put the patches into a new version he is(was) working on. But that was at the end of last October. Since this time I had no further contact with Dan. But Andrew Ozz has contacted me during Christmas days and added the patches.

    Because I have built in unfortunately some own new bugs it was necessary to make some emergency releases in the first week of January. I'm deeply sorry for the confusion I have probably created!

    With help of some diligent and thorough bug reporters have created some more patches which are partially included in the current development version (v8.8.5 beta 2). But most of them will be added in the next days. I can not tell when v8.8.5 beta 3 will be ready because I have no permission to add the patches myself to the repository and Andrew is sadly very ill.
    When these patches are in the development version I will post a message here.

    If podPress will become one of these "Canonical" or "Core" plugins is still undecided. Because at the moment I'm the only one who is maintaining this plugin and one part of the definition of this new group of plugins is that there should be more than one maintainer to assure continuous support in the future.
    But whether podPress will become such a special plugin or not I would like to make and keep podPress working (at least this year). Beyond the maintenance work I have some ideas for further customization options.

    podPress is a very complex plugin and there are a lot of source code lines which should be reviewed after more than one year without real development. Because of that and the fact that I'm only an enthusiastic podcast listener and no podcast producer help is appreciated!

    In conclusion: Yes, there is maintenance for podPress.
    But if there will be big development depends on the original plugin author or further helpers.

  4. raymer
    Member
    Posted 2 years ago #

    Since the original developer has indeed stopped supporting this plugin and also closed his support forum there is no place for the community to get help or offer fixes except here. I really appreciate Tim's work in incorporating fixes so that I can keep using the oficial svn repository version of podpress in my sites.

    One other thing that should probably be done is to update the player.swf to the latest and greatest (2.0). Although this will add a valuable feature (volume control), I feel like it is more of a maintenance request rather than a feature request. Since podpress simply wraps a third party flash player http://wpaudioplayer.com/standalone
    for playback features it should continue to be able to use the latest version of that player for security as well as feature updates.

    Do you think you could move to the 2.0 version of this player.swf in the next svn version?

    Thanks and best regards,
    Ray

  5. ntm
    Member
    Posted 2 years ago #

    Yes, that is good idea!
    I have created a Ticket (Ticket #1061) concerning this matter and I'm confident that the latest player will be in the next podPress release.

  6. raymer
    Member
    Posted 2 years ago #

    Cool. thanks.

  7. ntm
    Member
    Posted 2 years ago #

    There other propositions for v8.8.5 which are not yet in the development version:

    • Ticket #1089 - a new customizable XSPF player
    • Ticket #1085 - enhancement for loading time of the podpress pages
    • Ticket #1083 - a reworked player preview
    • Ticket #1080 - fix for podPress_downloadlinks container
    • Ticket #1079 - fix for the "Before <!- More -> tag:"-functionality
    • Ticket #1074 - better handling of invalid input data in the feed generating functions
    • Ticket #1073 - additional descriptions for the feed settings pages of podPress
    • Ticket #1068 - patch for an error free stats counter (Thanks to avatarworf)
    • Ticket #1066 - Podango message at the general settings page of podPress
    • Ticket #1061 - update of the 1PixelOut player a.k.a Audio Player

  8. geeknews
    Member
    Posted 2 years ago #

    One of the reasons my team built PowerPress and have updated it nearly ever month is because of all of the issues Podpress had and still has. We are glad to see someone help the podpress users as they were left out to dry for over a couple of years while wordpress moved on.

    We have a full time developer who maintains powerpress so we will be here for the new media community regardless of the status of this plugin.

    Good luck... Todd..

  9. raymer
    Member
    Posted 2 years ago #

    Tim,
    Any idea when the 8.8.5 version will be added to svn. I am using the head and am willing to test but I'd like to check out of svn so I can rollback if necessary.

    -Ray

  10. ntm
    Member
    Posted 2 years ago #

    Hello -Ray,

    thank you for your willingness to test the beta version!

    But I'm sorry that I'm not able to tell you when this beta 3 will be in the svn repository.
    Nonetheless I'm on it and I have made some more changes. Until the this beta version is released I'm going to collect the changesets in one cumulative patch for the podPress-trunk-version. It is attached Ticket 1093.

    This cumulative patch includes most of my previous patches but It includes corrections of some bugs which have been discussed in the last forum posts (with the tag podpress) and new features, too like a new adjustable XSPF player.
    All the changes are listed in the Changelog section of the readme.txt file. I have made some additional remarks in the Installation and the Configuration section, too.

    I'm confident that there will be a new podPress beta and maintenance release soon. But that depends on the WP team, too and I know that the WP team was busy in the last weeks e.g. with WordCamp in San Francisco and is still very busy with WP 3.0.

    But if you like to test what probably will be next beta version then you could checkout the current trunk-version and apply the 1093_cumulative_patch_885b2_to_885b3_v6.patch patch. Furthermore there are 3 files which have to be applied too. Please, have a look to the attachments section of Ticket 1093.

    I would like to hear about your experiences with the changes!

    Regards,
    Tim

  11. raymer
    Member
    Posted 2 years ago #

    Tim,
    Sorry if this is my newbie mistake. Bu when I run
    user@server% patch < 1093_cumulative_patch_885b2_to_885b3_v6.patch
    I get the following:

    (Stripping trailing CRs from patch.)
patching file skin.xml
(Stripping trailing CRs from patch.)
patching file variables.txt
(Stripping trailing CRs from patch.)
patching file skin.xml
(Stripping trailing CRs from patch.)
patching file variables.txt
(Stripping trailing CRs from patch.)
patching file license.txt
(Stripping trailing CRs from patch.)
patching file podpress.css
Reversed (or previously applied) patch detected!  Assume -R? [n] y
(Stripping trailing CRs from patch.)
patching file podpress.js
Hunk #1 FAILED at 33.
Hunk #2 FAILED at 143.
Hunk #3 FAILED at 181.
Hunk #4 FAILED at 189.
Hunk #5 FAILED at 207.
Hunk #6 FAILED at 235.
Hunk #7 FAILED at 243.
Hunk #8 FAILED at 262.
Hunk #9 FAILED at 274.
Hunk #10 FAILED at 306.
Hunk #11 FAILED at 341.
Hunk #12 FAILED at 358.
Hunk #13 FAILED at 374.
13 out of 13 hunks FAILED -- saving rejects to file podpress.js.rej
(Stripping trailing CRs from patch.)
patching file podpress.php
Hunk #1 FAILED at 1.
Hunk #2 FAILED at 37.
Hunk #3 FAILED at 91.
Hunk #4 FAILED at 154.
Hunk #5 FAILED at 205.
Hunk #6 FAILED at 217.
Hunk #7 FAILED at 271.
Hunk #8 FAILED at 420.
Hunk #9 FAILED at 546.
Hunk #10 FAILED at 731.
Hunk #11 FAILED at 765.
Hunk #12 FAILED at 781.
12 out of 12 hunks FAILED -- saving rejects to file podpress.php.rej
(Stripping trailing CRs from patch.)
patching file podpress_admin.js
(Stripping trailing CRs from patch.)
patching file podpress_admin_class.php
(Stripping trailing CRs from patch.)
patching file podpress_admin_feed_class.php
(Stripping trailing CRs from patch.)
patching file podpress_admin_functions.php
(Stripping trailing CRs from patch.)
patching file podpress_admin_general_class.php
(Stripping trailing CRs from patch.)
patching file podpress_admin_player_class.php
(Stripping trailing CRs from patch.)
patching file podpress_admin_stats_class.php
Hunk #1 FAILED at 76.
Hunk #2 FAILED at 183.
Hunk #3 FAILED at 216.
Hunk #4 FAILED at 234.
Hunk #5 FAILED at 259.
Hunk #6 FAILED at 266.
Hunk #7 FAILED at 282.
Hunk #8 FAILED at 291.
Hunk #9 FAILED at 323.
9 out of 9 hunks FAILED -- saving rejects to file podpress_admin_stats_class.php.rej
(Stripping trailing CRs from patch.)
patching file podpress_admin_wp27plus.css
(Stripping trailing CRs from patch.)
patching file podpress_class.php
(Stripping trailing CRs from patch.)
patching file podpress_feed_functions.php
(Stripping trailing CRs from patch.)
patching file podpress_functions.php
Hunk #1 FAILED at 82.
Hunk #2 FAILED at 112.
Hunk #3 FAILED at 150.
Hunk #4 FAILED at 296.
Hunk #5 FAILED at 329.
Hunk #6 FAILED at 347.
Hunk #7 FAILED at 388.
Hunk #8 FAILED at 441.
Hunk #9 FAILED at 474.
Hunk #10 FAILED at 980.
10 out of 10 hunks FAILED -- saving rejects to file podpress_functions.php.rej
(Stripping trailing CRs from patch.)
patching file podpress_theme.php
Hunk #1 FAILED at 23.
Hunk #2 FAILED at 36.
Hunk #3 FAILED at 119.
Hunk #4 FAILED at 162.
Hunk #5 FAILED at 183.
5 out of 5 hunks FAILED -- saving rejects to file podpress_theme.php.rej
(Stripping trailing CRs from patch.)
patching file podpress_xspfplaylist.php
(Stripping trailing CRs from patch.)
patching file readme.txt

    Copying the three attachement files if fine but I am having trouble with the .patch file...

    -Ray

  12. ntm
    Member
    Posted 2 years ago #

    That could have something to do with the fact that I create these patches on a Windows PC. But I don't know it for sure. Andrew Ozz had problems, too applying my patch files.

    But it is probably no big problem. I have tried to do what I have described above myself today: I created a new folder for a working copy, downloaded the podPress /trunk/ content via SVN and applied the ... _v6.patch without any problems. But I have used the TortoiseSVN client for Windows.

    I'm going to search later today a little bit more and report back.

    Tim

  13. ntm
    Member
    Posted 2 years ago #

    Hi -Ray,

    I have read in many forums that often the line endings are the cause for such error messages. Now, I have converted all line endings from CRLF to LF. Have you time to try it again with 1093_cumulative_patch_885b2_to_885b3_v6a.2.patch -> Ticket 1093 ?

  14. ntm
    Member
    Posted 2 years ago #

    I have tried apply my patch to a working copy on a Linux system with same error messages. But I will try to create this patch on this Linux system. Maybe that can solve the problem.

    Regards,
    Tim

  15. ntm
    Member
    Posted 2 years ago #

    I have made 1093_cumulative_patch_885b2_to_885b3_v6e.patch on a Linux system. Apply it with

    patch -p0 -d {name of the working copy folder if you are not in this folder} < {patch file name and location}

    The list of updated files should look like this:

    patching file players/xspf_jukebox/dynamic/skin.xml
patching file players/xspf_jukebox/dynamic/variables.txt
patching file players/xspf_jukebox/dynamic_slim/skin.xml
patching file players/xspf_jukebox/dynamic_slim/variables.txt
patching file players/xspf_jukebox/license.txt
patching file podpress_admin_class.php
patching file podpress_admin_feed_class.php
patching file podpress_admin_functions.php
patching file podpress_admin_general_class.php
patching file podpress_admin.js
patching file podpress_admin_player_class.php
patching file podpress_admin_stats_class.php
patching file podpress_admin_wp27plus.css
patching file podpress_class.php
patching file podpress.css
patching file podpress_feed_functions.php
patching file podpress_functions.php
patching file podpress_gettext.bat
patching file podpress.js
patching file podpress.php
patching file podpress_theme.php
patching file podpress_xspfplaylist.php
patching file readme.txt

    The /players sub folder should have a new sub folder: xspf_jukebox which should contain two own sub folder.

    (With svn export you get a clean directory tree.)

    ((after the export) Don't forget to copy the 3 other files to their locations:

    • podpress_icon_r2_v2_16.png to /podpress/images/podpress_icon_r2_v2_16.png
    • 1pixelout_player.swf to /podpress/players/1pixelout_player.swf
    • xspf_jukebox.swf to /podpress/players/xspf_jukebox/xspf_jukebox.swf
    )

    Regards,
    Tim

  16. ntm
    Member
    Posted 2 years ago #

    I like to remind every one that the patches in Ticket #1093 are leading to the next beta version! Do NOT use beta versions of this plugin in your regular blog!

  17. ntm
    Member
    Posted 2 years ago #

    I have added 3 further pictures to the ticket and a further patch.
    This patch (1093_cumulative_patch_885b2_to_885b3_v7_part ...) consists of two parts.
    I have tried to apply to a working copy of the podPress /trunk/-version on a Linux system without problems. It seems that the cause of the error messages (which were described above) was the usage of the wrong type of line ending characters in the header lines of my patch files.

    If lines like these:

    Index: podpress_admin_stats_class.php
===================================================================
--- podpress_admin_stats_class.php	(Revision 247380)
+++ podpress_admin_stats_class.php	(Arbeitskopie)
@@ -76,59 +76,118 @@

    are ending with a LF and not with a CRLF then it seems to work on both Linux and Windows computers.
    (I have tried to convert all lines of the patch file to the LF line break bad that did not work. I had to convert only lines like these separately).

    I'm hoping that these files are working now for everyone else too and that these changes will find their way into the repository soon.

    It would be nice to read what you think about the reworked statistic pages and the new bot filter.

    Regards,
    Tim

  18. raymer
    Member
    Posted 1 year ago #

    Hi Tim,
    I am on FreeBSD Unix on a shared host. I just ran the latest patches agains the svn head and they worked fine. 

    patch -p0 -d podpress < 1093_cumulative_patch_885b2_to_885b3_v8_part1.patch
patch -p0 -d podpress < 1093_cumulative_patch_885b2_to_885b3_v8_part2.patch

    Thanks for all your work on this plugin and for your work to make the patches OS-generic.

    I will check it out later today and comment when I have a chance.

    -ray

  19. raymer
    Member
    Posted 1 year ago #

    I did a quick once over of the admin pages and the user content I have. It looks fine. I should have done a diff of what I usually fix by hand because there are still some little things not right about the svn. One I noticed is that this file is missing:
    podpress/images/embed_youtube_button.png

    If you use podpress to embed youtube video the missing icon file will be noticed. Also I noticed that embedded youtube videos now play automatically when I load the page. I'm pretty sure this didn't happen in previous versions.

    Once again, thanks for your efforts to update this venerable plugin. If I notice any other little nits I will post.

    Blessings,
    Ray

  20. ntm
    Member
    Posted 1 year ago #

    Thank you for the first report. I have changed the autoplay setting and added this button image. I believe that there was no such image before. I have not found an old version in the repository.

    (You can find the changes and the images in Ticket #1093 1093_cumulative_patch_885b2_to_885b3_v9_part1.patch and part2)

  21. ntm
    Member
    Posted 1 year ago #

    Yesterday, I changed a lot. I have added new buttons to the Feed Buttons widget, fixed some things of the Feed/iTunes settings page and the procedures which producing the RSS feeds. Further more I have fixed a problem with one of the new statistic pages.

    @Ray: Please, use v10 of the patch.

    Thanks,
    Tim

  22. ntm
    Member
    Posted 1 year ago #

    @all: I have put all files and patches to the repository. The latest version is the Development Version. You can download it at http://wordpress.org/extend/plugins/podpress/download/.

    The current Development Version is 8.8.5 beta 3. I am sure that there will be a beta 4 and eventually a RC before the 8.8.5 will be marked as stable.

    That is new or changed in 8.8.5 beta 3:

    • new ATOM feeds: podPress adds now an feed with the name "torrent" which contains only posts (or pages) with .torrent files and a feed with the name "enhancedpodcast" which contains only posts (or pages) with .m4a/.m4v files
    • more options for the podPress - Feed Buttons widget: more buttons (new buttons added: feed-enhpodcast.png, feed-torrent.png, button_comments_rss_blog.png, button_atom_blog.png, button_comments_atom_blog.png)
    • more options for the podPress - Feed Buttons widget: feed buttons mode or text mode (In the text mode there is in front of each text a feed icon, but only for WP 2.2+. For older WP versions it is possible to add an icon via the Filter Hook: podpress_legacy_support_feed_icon)
    • more phrases ready for internationalization (http://codex.wordpress.org/I18n_for_WordPress_Developers)
    • frappr.com maps advice on the General Settings page of podPress removed
    • contains a fix for a problem (WP.org forum post 379290) with single and double quotation marks in the media file titles (Thanks to John Halton)
    • the appearance (incl. paging) of the tables on the statistic pages is updated
    • new feature: a bot filter for the download statistic - users can select (and deselected) IP addresses and user agent names which are probably search engine bots. The statistics will be computed without the download numbers of these bots. (for FULL / FULL+ stat logging)
    • The display of the statistics of the different collecting method Count Only, FULL and FULL+ are now separated. If the Count Only logging is active then the statistic page will have now besides the Quick Counts a comparable graph. This table and the graph and the Statistic Summary on the Dashboard are based on the numbers of the db table wp_podpress_statcounts. In Full or Full+ logging mode the number come from the wp_podpress_stats. That is important to know because the counter which counts the downloads on the wp_podpress_statcounts table counts when one of the 3 logging modes is active but the other counter which collects the data in the wp_podpress_stats table counts only during Full and Full+ mode. In other words: the numbers of the 2 tables can differ if someone uses the Counts Only mode for a while and than one of the others. Furthermore it is not possible to display the numbers of the Counts Only mode without the download numbers of the bots.
    • a new 'Downloads Per Media File' and a new 'Downloads Per Post' overview (for FULL / FULL+ stat logging)
    • The <object> element of the players has the class "podpress_player_object".
    • each podPress page and the Admin Menu has an icon (podpress_icon_r2_v2_32.png and podpress_icon_r2_v2_16.png added)
    • a new button and icon for YouTube videos embedded with podPress (embed_youtube_button.png / embed_youtube_icon.png)
    • a new button and icon for WMA files embedded with podPress (audio_wma_button.png / audio_wma_icon.png) (Now, podPress handles WMA file internally as audio_wma and not as video_wma.)
    • podPress uses now the DB_CHARSET or DB_COLLATE constants to create the 2 statistics tables
    • a new customizable XSPF player (Ticket #1089)
    • a reworked player preview
    • fix for podPress_downloadlinks container
    • fix for the "Before <!- More -> tag:"-functionality
    • better handling of invalid input data in the feed generating procedures
    • additional descriptions for the feed settings pages of podPress
    • patch for an error-free stats counter
    • Podango message at the general settings page of podPress
    • compared to 8.8.5 beta 2 the last patch of this Ticket #1064 makes that the enclosures which are added with podPress listed always before the enclosures from the custom fields with the name "enclosure". That is important because podcatchers like iTunes tend to recognize only the first enclosure of a RSS item. (Is a fix for this problem.
    • update to 1PixelOut player a.k.a. Audio Player 2.0
    • update to getID3 1.7.9

    Please, help to test this beta version. Before you start testing make a backup of your database and your files!
    Report your bug in this forum and if your start a new thread then use at least the tag "podpress".

    Regards,
    Tim

  23. ntm
    Member
    Posted 1 year ago #

    I have updated the Development Version. The current Dev. version is now podPress 8.8.5 beta 4.

  24. raymer
    Member
    Posted 1 year ago #

    I went to try out the latest and greatest, but I ran into some problems. I am using svn and when I checked out the trunk I got version 8.8.5 beta 10 reported in my admin console (WP 2.9.2) but the player doesn't appear on existing posts anymore.

    The ply in popup windows shows this error:

    Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Timestamp: Thu, 24 Jun 2010 13:30:23 UTC

Message: Invalid argument.
Line: 380
Char: 3
Code: 0
URI: http://www.mysite.com/wp/wp-content/plugins/podpress/podpress.js?ver=2.9.2

Message: Invalid argument.
Line: 380
Char: 3
Code: 0
URI: http://www.mysite.com/wp/wp-content/plugins/podpress/podpress.js?ver=2.9.2

    I thought maybe the trunk is too unstable so i tried to rollback to the experimental tag using
    http://plugins.svn.wordpress.org/podpress/tags/experimental/
    But then my entire site fails to load because of this error
    Warning: require_once(/path/to/my/wordpress/wp-content/plugins/podpress//podmighty.php) [function.require-once]: failed to open stream: No such file or directory in /path/to/my/wordpress/wp-content/plugins/podpress/podpress.php on line 79

    Which tag should I use now from svn? Do I still have to run any patches manually? I thought it was all committed now?

    Thanks,
    Ray

  25. ntm
    Member
    Posted 1 year ago #

    Thank you for this report!

    When does the error occur? Only when you try to use "Play in Popup"?
    (This popup player problem seems to occur specially in IE browsers. I'm going to fix it.)

    You wrote "... ran into some problems". Which other problems occurred?

    The experimental branch contains files which are mostly older than 2 years. I have not touched a file of it.

    So the Development Version (trunk/) contains the most recent version.
    All patches are applied and I put all my further changes directly to the trunk.
    BTW: You don't have to use an svn client to download the latest version. You can download it (Development Version) from http://wordpress.org/extend/plugins/podpress/download/.

    Regards,
    Tim

  26. ntm
    Member
    Posted 1 year ago #

    Good news. I found the source of the problem with the popup player and fixed this problem. (It was actually built in by me. Sorry!) Furthermore I could fix another problem with podPress embedded YouTube videos and the IE6. Now, it is also possible to set a dimension for these YouTube videos (again?). (But I don't want to make )

    @Ray: So far, Thanks for your thorough testing!!

    8.8.5 beta 11 is now the Development Version. A list with all the changes I made since 8.8.4 is in the readme.txt.

  27. raymer
    Member
    Posted 1 year ago #

    My problem is vey basic. The 1pixelout player has disappeared from my posts. I noticed that after updating the "enable listen wrapper" option was unchecked. When I tried checking it I noticed a couple of things.
    #1 the listenwrapper image is missing from the images
    #2 when I tried to save the settings I got a 404 error at this url:
    http://mywebsite.com/wp-admin/admin.php?page=podpress/podpress_players.php&updated=true

    My wordpress install is in a subdirectory and it looks like maybe you are getting the blog url incorrectly? E.g., the correct url above would be: http://mywebsite.com/wp/wp-admin/admin.php?page=podpress/podpress_players.php&updated=true

    Will continue troubleshooting later.

    -Ray

  28. ntm
    Member
    Posted 1 year ago #

    If you update podPress resp. deactivate and re-activate it then it is necessary to control all settings. Because podPress seems to set them back to default during this action. That may be the explanation for the unchecked listenwrapper checkbox.

    The listen_wrapper.gif is definitely in the repository: http://plugins.trac.wordpress.org/browser/podpress/trunk/images
    But yes indeed, there was problem which should be fixed by now -> Please, upgrade to beta 13.

    To the 404 problem: I have tested again on my local XAMPP server and on my "real" test blog http://undeuxoutrois.de/wp/. The blogs are in sub folders on all systems. I have on my XAMPP system also a multi site blog. But I could not reproduce this 404 error, yet.
    But the way podPress loads the player settings page (and all its other settings pages) after saving the settings is eventually a little bit odd. But if that is true then this 404 would occur on each podPress settings page after or while saving the settings. Because this procedure is the same on each podPress settings page.

    Does this 404 problem occur only after saving the player settings or on the other settings pages too?

  29. raymer
    Member
    Posted 1 year ago #

    Tim,
    In order to reproduce this you need to set up a blog like this:
    http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory

    That's how I do it and it seems like podpress can't get the right directory for the player anymore as well as the admin settings pages. Yes, the other settings pages 404 too. some of the pictures like the listen_wrapper.gif and the frame around the video aren't being found on the admin page and I'm pretty sure it's because the path is being calculated incorrectly somewhere.

    I think this is a regression bug. I remember vaguely the same thing happening a long time ago and I had to fix it manually (probably pre WP 2.6) but then it seemed to get fixed and I forgot exactly where I made the change. Please check that podpress is getting the blog directory correctly. I will try to help find the problem line(s) when I get a chance but I am extrememly busy right now and it might be a few days...

    -Ray

  30. ntm
    Member
    Posted 1 year ago #

    Hello Ray,

    I believe that I understand the problem now. My blogs are installed into sub folders like yours but I did not change the WordPress URL or the Site address after the installation. They are the same in my blogs. That probably the reason why I have not discovered this problem. I'm going to look into the matter and report back later.

    Thanks,
    Tim

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags