WordPress.org

1. Dwenaus
   Member
   Posted 2 years ago #

   This plugin basically works for 2.9. it has a minor bug, in that it shows post tags when you want them hidden. Otherwise it works well.

   http://wordpress.org/extend/plugins/wp-cms-post-control/

2. eljkmw
   Member
   Posted 2 years ago #

   I agree with dwenaus when this plugin runs under WP 2.9.
   Anyway, is there a feature to hide the Comments metabox in Edit Post? Hope that's included in the next release.

   Cheers ...

3. _Krap_
   Member
   Posted 2 years ago #

   Same here, but the fix is simple : edit the wp-cms-post-control.php file, search for #tagsdiv' => __('<strong style="color: #2583ad;">Post:</strong> Tags', 'wpcms_post_control'), and replace #tagsdiv with #tagdivs-post_tag.
   That's all, you're done, you can hide tags too.
   Cool plugin !

4. Jonnyauk
   Member
   Posted 2 years ago #

   Just to let you guys know, I have just updated this plugin to v2.0 and it now has full compatibility with WordPress v2.9.

5. dlmfisher
   Member
   Posted 2 years ago #

   I'm getting an error message with the updated plugin:

   Invalid argument supplied for foreach()...wp-cms-post-control.php on line 69

6. linlah
   Member
   Posted 2 years ago #

   I also get that message and then when deactivating I got that message and this message.

   Warning: Cannot modify header information - headers already sent by (output started at().../wp-includes/pluggable.php on line 868

7. Gersprenz
   Member
   Posted 2 years ago #

   Same to me - "Invalid argument supplied for foreach()...wp-cms-post-control.php on line 69 " and can't save the options, got this: "Warning: Cannot modify header information - headers already sent by (output started at().../wp-includes/pluggable.php on line 868"

8. linlah
   Member
   Posted 2 years ago #

   I noticed this morning there is a new update 2.12. After updating and activating the plug-in I no longer get any errors.

   Thanks so much for a great plug-in and the quick fix.

9. Jonnyauk
   Member
   Posted 2 years ago #

   Yup, sorry about that - as Linlah mentioned the bug is now fixed in v2.12 that caused the error message.

Topic Closed

This topic has been closed to new replies.