Title: Peter Massey-Plantinga's Replies | WordPress.org

---

# Peter Massey-Plantinga

  [  ](https://wordpress.org/support/users/pwp2/)

 *   [Profile](https://wordpress.org/support/users/pwp2/)
 *   [Topics Started](https://wordpress.org/support/users/pwp2/topics/)
 *   [Replies Created](https://wordpress.org/support/users/pwp2/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/pwp2/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/pwp2/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/pwp2/engagements/)
 *   [Favorites](https://wordpress.org/support/users/pwp2/favorites/)

 Search replies:

## Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Accessibility] ScrollTo not being included](https://wordpress.org/support/topic/scrollto-not-being-included/)
 *  Thread Starter [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/scrollto-not-being-included/#post-3737378)
 * They’re related, but they’re definitely separate issues.
 * I found this issue because we had a jQuery handler on an `<a href="#">` element,
   which wasn’t firing because of this error. So I discovered this error because
   of the other one.
 * Once this error is fixed, the call to jQuery(‘#’) doesn’t actually do anything
   but throw a few warnings (which still should be cleaned up for other developer’s
   debugging pleasure).
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WP Accessibility] ScrollTo not being included](https://wordpress.org/support/topic/scrollto-not-being-included/)
 *  Thread Starter [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 3 months ago](https://wordpress.org/support/topic/scrollto-not-being-included/#post-3737337)
 * scrollTo is also not being called correctly.
 * It should be:
 * `$(document).scrollTo( inPageAnchor, {duration: 1000} );`
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[CMS Tree Page View – Reorder Pages with a Drag-and-Drop Tree] Notice: trying to get property of non-object](https://wordpress.org/support/topic/notice-trying-to-get-property-of-non-object/)
 *  Thread Starter [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/notice-trying-to-get-property-of-non-object/#post-3493053)
 * I have a few custom post types, but I’m pretty sure I never added a CMS Tree 
   Page View for them and they’re still active. Looks to me like the custom post
   types could be the reason, though.
 * btw, adding/removing a tree view on custom post types results in a lot of notices
   and a WSOD. After this, the tree view works fine, so it’s not super important,
   but could be worth looking into.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Magazine Columns] header in column causes space](https://wordpress.org/support/topic/header-in-column-causes-space/)
 *  [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/header-in-column-causes-space/#post-3428215)
 * Sorry, bad code. Update:
 *     ```
       function fix_columns( $content ) {
           $content = preg_replace( '/(<p>)?((<\/div>)?<div class="column c\d">)<\/p>/', '\2', $content );
           return $content;
       }
       add_filter( 'the_content', 'fix_columns' );
       ```
   
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Magazine Columns] header in column causes space](https://wordpress.org/support/topic/header-in-column-causes-space/)
 *  [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/header-in-column-causes-space/#post-3428214)
 * I’ve had these problems too.
 * I fixed it by adding this to my code:
 *     ```
       function fix_columns( $content ) {
           $content = preg_replace( '/(<p>)?((<\/div>)?<div class="column c\d">)<\/p>/', '\2', $content );
       }
       add_filter( 'the_content', 'fix_columns' );
       ```
   
 * Perhaps this can be added to the plugin?
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] html5 validity](https://wordpress.org/support/topic/html5-validity/)
 *  Thread Starter [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/html5-validity/#post-3156333)
 * Appreciated. Unfortunately, it seems as though instead of removing the `<a name
   =...>` that I was referring to, the developers have changed the “name” to “id”
   on this element, which creates a different problem: there is now a duplicate 
   id. The form which immediately follows this anchor has the same id. I suppose
   the easiest fix would just be to remove the id on either tag.
 * Thanks for your help.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[Jetpack - WP Security, Backup, Speed, & Growth] html5 validity](https://wordpress.org/support/topic/html5-validity/)
 *  Thread Starter [Peter Massey-Plantinga](https://wordpress.org/support/users/pwp2/)
 * (@pwp2)
 * [13 years, 9 months ago](https://wordpress.org/support/topic/html5-validity/#post-3156324)
 * Thanks so much!

Viewing 7 replies - 1 through 7 (of 7 total)