WordPress.org

1. Oliver Aaltonen
   Member
   Posted 1 year ago #

   I setup a new server with a clean install of WordPress 3.0.1 and P2 1.1.7, and the following functions to not work:

   1) The edit function on posts does not work. Pressing edit results in the content disappearing, and no edit box appears. Comment editing works. Chrome reports the following error at line 491 of /wp-content/themes/p2/js/p2.js?ver=1289506386:

   Uncaught TypeError: Cannot read property 'type' of null
   thisCommentEditArea.editable.event
   b
   c.extend.ajax.g.x.onreadystatechange

   2) Live updates do not work. Refreshing the page works. I attempted a previous fix, but this does not resolve the issue.

   Here's a screencast showing the behavior:
   http://screencast.com/t/ycvcD2vy

   I have tried in both Chrome 8.0.552.200, Firefox 3.6.12 and IE 9 on Windows 7 and Safari 5 on a Mac. Has anyone else experienced these issues?

   Regards,

   Oliver

2. Lance Willett
   Theme Wrangler
   Posted 1 year ago #

   Hi Oliver,
   Can you double check that you have the latest JS file? Line 491 in version 1.1.7 is something totally different:
   var postContent = jqe.find('.postcontent');

   Another thing to check is if any plugins are changing the jQuery version in your WP install.

3. Oliver Aaltonen
   Member
   Posted 1 year ago #

   Lance,

   I've reproduced the issue on a 2nd fresh installation. I manually downloaded and unzipped the P2 package this time, instead of using the built-in theme installer. Here are the details of the p2.js file:

   [root@p2 js]# ls -l p2.js
   -rw-r--r-- 1 root root 34024 Sep 30 13:53 p2.js
   [root@p2 js]# md5sum p2.js
   057a86c002f86b006b039e32096d33a0  p2.js

   Line 491 is:

   if (post.type == 'post') {

   I haven't installed or activated any plugins. This installation is as vanilla as it gets.

   Regards,

   Oliver

4. Lance Willett
   Theme Wrangler
   Posted 1 year ago #

   That looks like the correct JS file. I cannot duplicate the error, unfortunately. :(

   I installed a new 3.0.1 instance an activated P2 1.1.7 (downloaded the ZIP from Extend) and do not see any errors in Firebug.

   We'll be pushing a new P2 release to the directory soon—you can try it and see if it fixes the issue. Otherwise could be an OS-level thing.

5. Jay Versluis
   Member
   Posted 1 year ago #

   Hi guys,

   I can confirm I've got the same problem in Firefox as described above. I thought it was just me ;-)

   This second (spooky!) I've seen that P2 is now in version 1.8 - so I've upgraded and the problem is gone.

   Thanks!!

6. Oliver Aaltonen
   Member
   Posted 1 year ago #

   I just downloaded P2 1.1.8, but the issue is still present. Since I've been poking around the existing installation trying to troubleshoot the issue, I'm going to build another VM and perform a clean LAMP and WP installation with the new version. I'll post back here when I have feedback either way.

7. Lance Willett
   Theme Wrangler
   Posted 1 year ago #

   Jay—that makes me think it could be a cache issue.

   Oliver—keeps us posted. :)

8. Oliver Aaltonen
   Member
   Posted 1 year ago #

   I just installed the same WordPress 3.0.1 and P2 1.1.8 packages on a fresh Ubuntu 10.10 instance, and everything is fully functional. Thanks!

Topic Closed

This topic has been closed to new replies.