podPress 8.8.5.3 in WordPress 3.0.x makes browsers crash
-
After updating to podPress 8.8.5.3 and then WordPress 3.0, the WP-bundled Tiny MCE editor in the post admin failed to load (only the HTML editor was showing) and the podPress section of the post admin failed to load. The post admin itself failed to fully load and locked up all my Mac 10.6.4 browsers (Safari 5.0.1, Firefox 3.6.8, Chrome 5.0.375.126, all current versions). I had to restart the computer each time.
I narrowed the problem down to the podPress plugin by deactivating all plugins and activating just the podPress plugin and by just deactivating the podPress plugin.
-
Hello Jeff,
what is your Max Number of Media Files value (podPress > General Settings)? More than 10?
What is the status of the Podango Integration? In use or not in use?
Did these problems occur while trying to edit an existing post or a new one?
Would you do a further test? In general one possible reason that the editor page does not load completely can be e.g. a Javascript error. You can find out whether there is an JS error or not if you are using the error console of Safari or Chrome. In Safari you can open this error console via the Developer menu. Open it, clean it if conatins already error messages and load the editor page of your blog (while podPress is activated). I hope that if there are JS errors the error messages shows up before the browser freezes.
Please, post the error messages here.BTW: Why do you have to restart the whole computer if “only” the browser freezes? Is there no other possibility in Mac OS to end processes which are not responding?
Can you tell if this problem exists with WP 2.9.2 and podPress 8.8.5.3?
(Or with 2.9.2 and podPress 8.8.4?)Regards,
TimIf you can not find Javascript errors, try to find out why your browser(s) crashed. Firefox has something called Breakpad. Maybe you need to activate this first. You can read here https://kb.mozillazine.org/Breakpad#Location_of_crash_reports where you can find the crash reports.
Did you have the possibility to determine whether this happens only on your Mac or if this happens on other Macs to?
I am getting this issue as well – well the browser doesn’t crash, it just doesn’t allow for me to add or edit posts.
If I load it in chrome it never finishes loading. If I load it in firefox I get this in firebug
Syntax error line 30436 document.getElementById(‘podPressPlayerSpace_0’).innerHTML = podPressGenerateVideoPreview (0, ”, , , document.getElementById(‘podPressMedia_0_previewImage’).value, true);
it might be important to note that the line immediatly before and after this line are
<script type=”text/javascript”><!–
–></script>wordpress 3.0.1 and podpress 8.8.6.3
@reidgivens: Thanks for the snippet of the source code resp. error message!
The problem in this line are two empty parameters. It should bedocument.getElementById('podPressPlayerSpace_0').innerHTML = podPressGenerateVideoPreview (0, '', 320, 240, document.getElem ....
or at least 0 instead of 320 and 240 but not nothing between these commas.It is relatively easy to fight the symptoms and to make sure that there will be always some values but the more interesting thing to me is why resp. under which circumstances that happened.
I’m currently trying to reproduce this but is not very easy. Can you tell me a little bit more about your installation? Do you use podPress the first time? Or did you have updated the plugin just before that error occurred the first time?Thanks for the report.
Regards,
Tim@reidgivens:
Does this problem occur only when you try to start a new post or only when try to edit an existing post or in both situations?If this problem occurs when you try to edit existing posts with podPress media files then could you tell what kind of media file is attached to the post? .mp3? .ogg?
Could you please look into the source code of the edit page and look out lines like:
<!-- podPress dbx for modern WP versions - post --> <script type="text/javascript"> var podPressMaxMediaFiles = 10; var newMediaDefaults = new Array(); newMediaDefaults['URI'] = ''; newMediaDefaults['title'] = ''; newMediaDefaults['type'] = 'audio_mp3'; newMediaDefaults['size'] = ''; newMediaDefaults['duration'] = ''; newMediaDefaults['dimensionW'] = '320'; newMediaDefaults['dimensionH'] = '240';
What are the values of dimensionW and dimensionH?
Regards,
TimIt seems on posts that already have an attached audio file this doesn’t happen, but on new and editing posts that do not have an audio file attached, it does as specified below.
It takes every edit page a long time to load (2 minutes or so), but the posts with attached files do not error.
On all of the edit pages it has
<!– podPress dbx for modern WP versions – post –>
<script type=”text/javascript”>
var podPressMaxMediaFiles = 5;
var newMediaDefaults = new Array();
newMediaDefaults[‘URI’] = ”;
newMediaDefaults[‘title’] = ”;
newMediaDefaults[‘type’] = ‘audio_mp3’;
newMediaDefaults[‘size’] = ”;
newMediaDefaults[‘duration’] = ”;
newMediaDefaults[‘dimensionW’] = ‘320’;
newMediaDefaults[‘dimensionH’] = ‘240’;
newMediaDefaults[‘previewImage’] = ‘https://www.***.com/***/wp-content/plugins/podpress/images/vpreview_center.png’;
newMediaDefaults[‘rss’] = false;
newMediaDefaults[‘atom’] = true;
newMediaDefaults[‘feedonly’] = true;
newMediaDefaults[‘disablePlayer’] = false;
newMediaDefaults[‘disablePreview’] = false;
newMediaDefaults[‘content_level’] = ‘free’;
newMediaDefaults[‘showme’] = false;and always mp3 files.
I have been using podpress for about 5 years.
sorry – in the previous message I put “as specified below” – I meant to say “as specified above” referring to my first post in this thread.
Hmm… That helps a little bit.
But I still have problems understand why these paramters of the JS function call are empty.
Would you edit one of the podPress file in order to retrieve some more debug information?Please, open the podpress_admin_class.php file in an text editor and insert between the lines 754 and 755 some new lines of code:
old:while ($num < $this->settings['maxMediaFiles']) { if(!isset($post->podPressMedia[$num])) { $num++; continue; } $thisMedia = $post->podPressMedia[$num]; if ( $thisMedia['showme'] == 'true' ) { $display_text = 'block'; } else {
new:
while ($num < $this->settings['maxMediaFiles']) { if(!isset($post->podPressMedia[$num])) { $num++; continue; } $thisMedia = $post->podPressMedia[$num]; echo "\n <!-- ### podPress debug: \n"; var_dump($num); var_dump($this->settings['maxMediaFiles']); var_dump($thisMedia['dimensionW']); var_dump($thisMedia['dimensionH']); echo "\n --> \n"; if ( $thisMedia['showme'] == 'true' ) { $display_text = 'block'; } else {
You can find these code line probably two times in this file but the section around the lines 754-755 is the relevant one if you are use WP 3.0.1.
These lines will output the W and H dimension values into the source code of the edit page. I would like to know when the dimensionW and dimensionH value become empty. In the lines which you have posted above, they are obviously not empty and they should not be empty in the line 755 either.After you apply these modifications, you should find in the source code of the edit page multiple section like this one:
<!-- ### podPress debug: int(0) int(10) string(3) "320" string(3) "240" -->
Are there section where some of the values are NULL or empty?
e.g.:<!-- ### podPress debug: int(0) int(10) NULL NULL -->
One place which maybe not ok, is line 680 in the same file.
Please, try to modify this section like this:
old:if ( FALSE !== empty($post->podPressMedia) ) { $num = 0; } else { $num = count($post->podPressMedia); }
new:
if ( FALSE !== empty($post->podPressMedia) ) { $num = 0; } else { $num = count($post->podPressMedia); $num = intval($num); if ($num > $this->settings['maxMediaFiles'] ) { $num = $this->settings['maxMediaFiles']; } }
If you do not know how to edit such PHP files, I could upload a modified file and post a link.
@readgivens: Maybe the page hits a time or a memory limit of your server. Please, check e.g. with the WP System Health plugin what your time and memory limits are.
- The topic ‘podPress 8.8.5.3 in WordPress 3.0.x makes browsers crash’ is closed to new replies.