Forum Replies Created

Viewing 9 replies - 16 through 24 (of 24 total)
  • Plugin Author metamorpher


    Hello scpears0n

    Sorry for taking so long to reply this message, but I was very very busy. About your issues, I must say Bulk Me Now doesn’t send the stored messages to your e-mail account. It stores the messages in the database of your wordpress installation so you don’t get spam in your mail account.

    Instead, you can receive a notification in your e-mail account when you get new messages. This is a feature added in the version 1.5, and it relies on the pseudo cronjob that wordpress implements. So, it really depends on your traffic for you to receive those notifications. Again, it doesn’t send the messages to your e-mail account. That is not the purpose because the plugin was designed.

    Also, going to be looking for other problems and will consider to add the possibility to send the message to the e-mail account, since it was a constant request in other e-mails I got.

    If you have further questions about the plugin, please contact me in, best way to catch my attention right away 🙂

    Thanks again for using Bulk Me Now!

    well I “solved” it long before… sorry for not replying this on time, but madpress was right… you better use single names for the taxonomies before sinking in a glass of water like I did.

    just used underlines to separate names and it did the difference… thanks for your time guys!!

    don’t think so… ’cause I went to the edit-tags.php and echoed the $taxnow var, and WP already uncapitalized the name and removed the space… Long story short: It doesn’t matter the name syntax, ’cause the system adapts it.

    At the same time, I also use the function get_taxonomy() in my functions.php file, and I’m using it with capital letters and spaces, but I can still get the thing to work without problems.

    Well, by checking the 3.0 version of the edit-tags.php and comparing it to the 3.1 version, I can show you the following:

    3.1 version

    /** WordPress Administration Bootstrap */
    $tax = get_taxonomy( $taxnow );
    if ( !current_user_can( $tax->cap->manage_terms ) )
    	wp_die( __( 'Cheatin’ uh?' ) );

    3.0 version

    /** WordPress Administration Bootstrap */
    wp_reset_vars( array('action', 'tag', 'taxonomy', 'post_type') );
    if ( empty($taxonomy) )
    	$taxonomy = 'post_tag';
    if ( !taxonomy_exists($taxonomy) )
    	wp_die(__('Invalid taxonomy'));
    $tax = get_taxonomy($taxonomy);

    You do the math 🙂

    Sorry for that boy… you have to use it like your first function:

    You have to declare a function and add it like an action into admin_init, like this:

    function admin_init()
    		 remove_post_type_support('post', 'title');
    	add_action("admin_init", "admin_init");


    actually this is wrong…

    you shouldn’t edit the wp core files ’cause they’re not going to survive an update…

    I mean, on every update, every core files would be replaced, then your editing will be overwritten…

    I recommend you to use the remove_post_type_support function. Just add the following code everywhere in your functions.php file:

    remove_post_type_support('post', 'editor');

    where the first parameter is the post type and the second parameter is the item you want to remove. You can use this function with the following items:

    title, editor, author, thumbnail, excerpt, trackbacks, custom-fields, comments, revisions

    That way is better for your wp installation, and also in case you want to modify independently your themes…

    See you 🙂

    Everything is managed inside the php file which have the same name of the plugin.

    I think it also corresponds to the name of the folder.

    I mean, the convention is “If you have a plugin called Foo Plugin, then your folder should be named foo-plugin, and the file inside it is foo-plugin.php”

    For neat purposes, some coders create external files within, but they call them all with the php include function(), which in common words “inherits” those functions (Actually the term inherit belongs to the OOP architecture, but well, in common words looks like that).

    As I see in your error, the mistake is within buddypress folder, exactly in the line 1971 of the bp-groups.php file.

    not checking the isset($POST) which I should’ve use to prevent this…

    sorry 😛

    yeah… should be banned, also for the poor service they give… promise you the stars and the moon, and all you get is 200 MB of storage

Viewing 9 replies - 16 through 24 (of 24 total)