Hey! Podpress is working fine, except for a vital part: the player doesn't show...
look: http://omovimento.blog.br
can someone help me?
[resolved] [Plugin: PodPress] Player doesn't show (22 posts)
-
daniaversa
Posted 1 year ago # -
Hi,
podPress needs to add some lines of Javascript code to the header of your blog. It also includes Javascript code from a .js file and CSS from a .css file. None of these lines of code is in the header of your blog.
If your are using WP 3.1 then podPress uses the WP Action Hooks wp_print_scripts and wp_print_styles to do that.
If you are using an older WP version it uses simply the wp_head Hook to add the necessary lines.It seems to me that something in your theme or different plugin prevents these actions.
Does one of the PHP files of your theme contains
wp_head();orget_header();?
What happens when you are using the default theme (Twenty Ten)?
Does it make a difference if you deactivate other plugins?Regards,
Tim -
Posted 1 year ago #There's no other plugin activated. On Twenty Ten the player appears... I'm not using wp_head or get_header.
I didn't get the codes on the header. In the installation guide nothing is said about this. I'm using WP 3.1.
What should I do?
-
I'm not using wp_head or get_header.
That is the problem.
What should I do?
If you have created this theme or if know how to modify the code then add a call of the function
wp_head();to the header.php file. Maybe take a look at the header.php of the Twenty Ten theme to see how it is done.
Or maybe better read about this in WP Theme Development > Document Head.Otherwise ask the designer of the theme do that.
This wp_head(); call is not only important for the podPress plugin. A lot of other plugin rely on that too.
Regards,
Tim -
Posted 1 year ago #It did the trick! Thank you!!
-
oscarhelm
Posted 1 year ago #I got exactly the same problem.
The problem only occurs in Google Chrome.
Check this out in Google Chrome: http://vandaagvrouwenversieren.nl/interview-met-dating-expert-mark/
I already have the wp_head(); in my header.php.
The player worked before but not anymore in Chrome. Now you have to click on 'Play Now' before you see the player.
I already tried everything in the settings but it doesn't work.
Also, the whole layout of the player is changed.
As anyone the solutions?
-
@oscarhelm: The problem in your case is different. You may start a new thread.
On a first look into the source code of your page I can say that the
<head>exists twice and the error console of Chrome and Safari will show you a lot of errors.
I will look into this further. But you should try to find out why this section is printed twice. You can do that by deactivating all other plugins temporarily and by activating them one by one while watch whether or not it changes something.
Also make sure that the them does not call wp_head(); twice.Regards,
Tim -
@oscarhelm: I have done some tests and it seems very likely that this problem is caused by the doubled
<head>section.
The second<head>section is somewhere in the middle of the <body> section and on a second look it seems that only the podPress scripts are doubled.But I have difficulties to reproduce that behaviour. The error seems to occur in combination with your theme or one of your other plugins.
So please, try to find out which plugin interferes with podPress.When I know the plugin name, I can try to fix the problem.
Regards,
Tim -
Posted 1 year ago #@ ntm
I indeed noticed that I copied headsections etc. in mij HTML text widgets.
I deleted those so now there is just one headsection.
It fixed 3 errors in the w3 validation markup.
It is still the same: http://vandaagvrouwenversieren.nl/interview-wild-fm/
The podPress code is doubled, maybe that's a problem for Chrome.
Any suggestions how to get rid from one of those?
-
You are right the second
<head>section is gone.The cause for the doubled podPress section is maybe a different plugin or maybe it is something with your theme.
podPress prints these lines of code via the WP Action Hook wp_print_scripts. Maybe another plugin interferes at this point somehow.
The best way to find out whether this guess is right or not and which plugin might be involved is to deactivate the other plugins for a moment. Reload the page and look into the source code.
You could also switch the theme as a test.... and if we know which plugin else is involved, I can try to find out why and how.
But the reason why the player or the Play button appears only when you click on Play Now is most likely that you have activated the option "Disable Preview Player:". You can find this option in the podPress box below the post editor.
Leave that checked and the Play button will appear on page load in Chrome and Safari.Regards,
Tim -
davekropf
Posted 1 year ago #It seems that since last Friday, Podpress has stopped working for me. The player no longer shows in the feed and the show files are no longer being embedded into the feed.
-
@davekropf: It would be better if you could start a new thread. The problem in your case has nothing in common with the problem which occured in the blog of daniaversa nor oscarhelms blog.
It would also be helpful if you could tell me what you have changed last Friday. Have you upgraded podPress to 8.8.10 (Which was released last week)? Or did you make an update from an older version to 8.8.9.2?
I would say you are running currently 8.8.9.2. That and the problems you have described let me guess that you have downgraded from 8.8.10 to 8.8.9.2. If that is right then I would like to know why you have downgraded. Also upgrade again to 8.8.10 or if you want to stay with 8.8.9.2 rename the meta_key (in the postmeta db table) values _podPressMedia, _podPressPostSpecificin back to podPressMedia and podPressPostSpecific.
Regards,
Tim -
Posted 1 year ago #Sorry. I didn't mean to hijack a resolved thread. :)
I just upgraded to 8.8.10, and that's all I've really done since Friday. I do use feedburner.
-
@davekopf:
and you would say that 8.8.10 is still installed?I'm asking only these question because the source code of your feeds says something different. See your self: http://validator.w3.org/feed/check.cgi?url=http%3A%2F%2Fdrummertalk.org%2Ffeed%2F
There is still the line
<!-- podcast_generator="podPress/8.8.9.2" -->. If your current version would be 8.8.10 the version number there would be 8.8.10. I'm very sure that currently you do not use 8.8.10 or 8.8.10.1.Well, and if have upgraded to 8.8.10 and downgraded afterwards you get exactly these kinds of problems you have now. It is not that easy to downgrade from 8.8.10.
However if you say that you have not downgraded then it seems very likely that the upgrade is somehow incomplete. Repeat the upgrade or better: delete all the files in the wp-content/plugins/podpress folder and upload the files of 8.8.10.1.
Regards,
Tim -
Hi Dave,
I have looked into the readme.txt of your current podPress version ("http://drummertalk.org/wp-content/plugins/podpress/readme.txt") and it is the readme.txt of podPress 8.8.10.1.
But the podPress version number in the feeds like http://drummertalk.org/feed/ is still 8.8.9.2.
Something is clearly not right. The numbers should be equal. My guess is that something went wrong during your last upgrade attempts.
Can you describe to me how you did the upgrades to 8.8.10 and 8.8.10.1?
Did you use the automatic upgrade of WP or a plugin?Do you have access to the data base of your blog through a phpmyadmin interface or something comparable? Do you know how to use such an interface?
If you do have access to such an interface open the wp_postmeta data table of your blog and look whether the meta_key values _podPressPostSpecific and _podPressMedia have an underscore character or look like podPressPostSpecific and podPressMedia.Regards,
Tim -
What is the version number of podPress at the plugins page of your blog?
Please, have also a look to the System Information section at the general settings page of podPress. Is there any sign of a version conflict? Or what is the current podPress version there? -
Dave,
please install the current Development Version of podPress. (Download the .zip file, extract all the files and sub folders, connect via FTP to your blog, remove the old files and folder of the podPress plugin and upload the new ones.)
This version contains further selftest mechanisms. When you have installed and activated the Development Version go to the general settings page of podPress and watch the section "System Information". are there any conflicts listed? Or can you see the notice "old meta_key names detected"?
You would help me a lot if you could also answer the questions from my previous posts.
Thank you for your help!
Regards,
Tim -
Posted 1 year ago #Tim,
To answer your previous post, I am running the latest version of PP, and I cannot explain why the validator is indicating an older version. I've tried uninstalling and reinstalling the plugin with the same results. I will try installing the Dev version today.
I really appreciate all of your help!!
-
Posted 1 year ago #I've discovered the issue, although I don't know how to resolve it.
Due to some other Buddypress issues, I've recently moved my WP install from a sub dir into the root. It seems that while WP is upgrading and installing files in the root directory install, the plugins are still being pulled from the old sub directory.
What happened this weekend was I upgraded to the latest podpress, and while the plugin files were upgraded in the proper install directory (root), WP is still pulling the plugins from the old install.
Now this is a whole new batch of problems ...
-
That would explain also the problems with podPress. podPress 8.8.10 renames the meta_keys podPressPostSpecific and podPressMedia. But if they are renamed, podPress 8.8.9.2 can't see them anymore and it is like you have not attached a podcast episode with podPress.
A quick fix would probably be installing podPress 8.8.10.1 (or better the Dev Version) in both of your plugin folders.
-
Posted 1 year ago #Done. Turns out there was some code in my index.php calling for the header.php in the old sub dir. That was throwing off everything!
Whew. Thanks again for all your help!
</hijack thread>
-
I'm glad that it works now.
There is one little thing: You should control and maybe update the URLs of the RSS and iTunes images.
Topic Closed
This topic has been closed to new replies.
