Now Reading

Page.ly Multi-Edit 0.9.8

Finally got around to updating our Multi Edit plugin.

The new version 0.9.8 has some bug fixes and a couple new features like Short Tag support. Get it here.

Comments
  1. Why are you not using wp_enqueue_script and wp_enqueue_style to include you style and js files to the header? The way you have done it makes the code printed before anything else event before the opening HTML tag. I’m now getting this error because of this: Warning:

    Cannot modify header information – headers already sent by (output started at /****/wp-content/plugins/pagely-multiedit/multiedit.php:146) in /****/wp-includes/pluggable.php on line 897

  2. On many of our sites we have had to revert back to the old version of this plugin. After 7 hours of painstaking head scratching and near suicidal moments we found out it’s a conflict between the plugin and the following code which caused none of the multiedit regions to display when on the same page.

    query(‘showposts=3&cat=3′);
    while ($featuredPosts->have_posts()) : $featuredPosts->the_post(); ?>
    (used to display a feed/loop of testimonials, news etc in an area of the page)

    We absolutely love the plugin and totally appreciate your hard work developing it, it has been brilliant for us and clients love the ease of using the CMS.

    If you could suggest a fix for the above then it would be great,
    In the meantime we’ve downgraded the plugin on all websites with a problem.

  3. we’ve just answered our own question!
    The code above
    query(‘showposts=3&cat=3′);
    while ($featuredPosts->have_posts()) : $featuredPosts->the_post(); ?>

    must now not be between

    and

    It must be outside this area, all page.ly multi edit regions must be within this area. Hope this helps others.

  4. extra comment which will help anyone who finds this…. infact you just need to reset the query. IN our case it’s after the featured code, this ensures it doesn’t interfere with other post queries from the database such as those for multiedit content.

  5. You have this line of code:

    define ('PLUGINASSETS',WP_PLUGIN_URL.'/'.dirname(plugin_basename(__FILE__)).'');

    Can you please make use of plugins_url() instead so that if the admin screen is behind a https connection the .js and .css files are loaded from https too. Your plugin at the moment is loaded insecure files because of this.