Jazzy CDN
Forum Replies Created
-
Forum: Plugins
In reply to: PODPRESS – Default Upload Directory – iTunes Killer?PS – re: Status[Resolved]
… while I am optimistic about the results, and in a slightly celebratory mood given it being July 4th and all (even if I’m not in the US) … resolved feels a bit ‘rosy’ at this point.
Let’s hope, but the show has yet to get re-listed on the iTunes Store, and so far, maybe [Resolved-ish] or [To Be Continued] … no firm answers yet, only questions, and hope!
Thanks
Forum: Plugins
In reply to: PODPRESS – Default Upload Directory – iTunes Killer?Ok, good to know the HTACCESS file is unrelated to the iTunes Store pinging problem.
Armed with your comments, those of Roger and feedback from Godaddy, I’m going to make another approach to iTunes Store.
As I mentioned above, the iTunes Store stopped updating the show initially for about 3 weeks and then re-started updating again for a couple of weeks before finally packing it in completely.
Initially I didn’t ask podcast support at Apple why it restarted the first time, but recently I did thinking it might shed some light on the current situation.
The reply back was that they didn’t do anything, it was the host (Godaddy) that changed something. However, I know for a (almost pretty sure) fact that Godaddy didn’t do anything on my behalf the first time.
I called them, they said everything is working fine from our end … and that was the end of it.
So too now, as far as I can tell, for them it’s just business as usual. And of course, the podcasts are serving off their servers, and other podcasting platforms are getting the shows up and listed (one example: podcaster.fm)
So, I’ll see what iTunes Store support replies after I send the current info. I’ll update when I have a reply – which can take days.
More, soon!
Forum: Plugins
In reply to: PODPRESS – Default Upload Directory – iTunes Killer?All very interesting (and I’m learning a lot, sadly though, not enough to solve the problem yet).
So, I altered the absolute path to actually BE the absolute path and immediately saw the drop down menu correctly operating within the plugin to select media, for the first time … listing all the files in the podcast folder. Nice!
So, to test-drive this new functionality, I opened a new post and randomly pointed at different mp3s in the ADD MEDIA FILE section, and hit the auto-detect button to see if file sizes and durations would detect properly now.
Results were poor BUT intermittent. Generally file size calculated right (not always) and duration calculation usually (but not always) failed.
Sometimes, I’d get a string of question marks for the duration, sometimes an odd symbol and letter … BUT sometimes … duration was right – and sometimes BOTH file size AND duration was right.
In a random sampling of some mp3s from the drop down list, duration calculated correctly on mp3s: 363 380 386 390, however not necessarily file size. But then immediately previous or following mp3s would fail: ie: 379 and 381 didn’t calculate duration right, while 380 did.
But I didn’t test every mp3. All but the first are at 96K, the first is at 80K. All have some ID3 tagging, slight variations, and file size is almost identical (except the lower coded one).
NEW QUESTION: .HTACCESS
WordPress is installed in a subfolder in the podcasts folder among all the podcasts. It appears WP (I assume) placed a .HTACCESS file in the podcast folder right around the time I updated WordPress and PodPress plugin. I never placed a .HTACCESS file in that folder.
The contents of that .HTACESS follow:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /podcasts/
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /podcasts/index.php [L]
</IfModule># END WordPress
I know HTACCESS files can interfere with access to folder contents (and do other ‘stuff’ as well) … do you thing the contents of this HTACCESS file is tripping up functionality somehow?
I have no idea what the programming of that HTACCESS file is doing to anyone trying to reach the podcasts, calculate their duration, or what would happen if the iTunes Store tried pinging that directory.
Forum: Plugins
In reply to: PODPRESS – Default Upload Directory – iTunes Killer?Tim,
I don’t know if you’re on to something with the Absolute Path field but currently both ARE indeed the same:
URL of the media files directory: http://jazzboulevard.ca/podcasts
Absolute path of the media files directory: http://jazzboulevard.ca/podcasts
And now that you bring my attention to it there is a warning message below the latter stating “This directory is not valid or not accessible.”
There is also a suggested url that begins with “home/content/m/o/…” and ends with “…wp-content/uploads”
I wonder if I should enter this as suggested, or maybe alter the ending to direct to the actual folder containing the podcasts?
It indicates this interacts with the time/duration calculation (something that has been a problem) and these are longer programs running almost 2 hours each (1:52 generally and about 80Mb).
I wonder if this is causing some sort of timeout on the iTunes Store pinging before it can get to the actual latest podcasts?
Any thoughts?
Forum: Plugins
In reply to: PODPRESS – Default Upload Directory – iTunes Killer?Hi Tim,
Thanks for the reply.
Let me add some info culled from some fields within podPress – maybe there’s something I’m not understanding in completing this info (when I updated the podPress plugin, I just left everything to defaults since I assumed the info would carry over) (and my problems with iTunes Store preceded upgrading the plugin).
* GENERAL SETTINGS PAGE *
URL of the media files directory: http://jazzboulevard.ca/podcasts
Absolute path of the media files directory: same
* FEED/ITUNES SETTINGS PAGEiTunes:FeedID 274055615
iTunes:New-Feed-Url = Disable Then within that text, it shows the correct RSS feed you found on the iTunes blog – I assume disabled. Although looking now, it’s the only place I actually see the correct RSS feed anywhere).
(further down under PODPRESS FEEDS)
current Feed URL: http://jazzboulevard.ca/podcasts/feed/podcast (which seems wrong, shouldn’t that be the RSS feed?).
iTunes: New-Feed-Url = disable
iTunes:New-Feed-Url – the new Feed url = blankNow, as I’m looking at it, I’m wondering why the “current Feed URL” is pointing at the folder and not showing instead the actual RSS feed http://jazzboulevard.ca/podcasts/?feed=podcast
Is there something ‘fishy’ here or does everything look normal?