Support Forum » User Profile

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 57 total)
  • Author
    Posts
  • Infolu OfficialInfolu Official
    Participant

    Hi Peter, thanks for the information!
    After reading your comment, I took a closer look and noticed something unusual. Since I hadn't manually configured the label fields, I decided to run a test.

    I discovered that when I create a post type with WordPress set to English, everything works fine — the labels are generated correctly. However, when I switch to another language and create a post type, the system ends up using a % symbol in place of the plural label.

    Note that I only register the fields on the General tab.

    exemple

    Exemple

    Infolu OfficialInfolu Official
    Participant

    Hai Anh Tran thanks for the information, I was thinking when I saw this counting on the dashboard and sites.

    exemplo

    Infolu OfficialInfolu Official
    Participant

    There is the "%" I am not using any wordpress translation plugin + metabox io only

    exemple

    Infolu OfficialInfolu Official
    Participant

    Please disregard my previous comment, I posted it in the wrong thread. Attached is the requested image.

    exemple

    in reply to: ℹ️Behavior when disabling feature #48645
    Infolu OfficialInfolu Official
    Participant

    Hello,

    Thank you for your response and clarification.

    I understand that it's currently expected behavior for Meta Box AIO to require at least one extension to remain active. However, I’d like to share some feedback:

    I use Meta Box via Composer to have more control over what's loaded in my project. My goal is to use only the native field types, without the additional extensions, ensuring a lighter setup and the flexibility to enable or disable features as needed.

    In this case, it doesn’t make sense to be forced to keep at least one extension active if I only want to use the custom fields. It would be great to have more flexibility and be able to deactivate all extensions without having to disable the entire plugin.

    Thank you for considering this suggestion.

    Infolu OfficialInfolu Official
    Participant

    Hello,

    Thank you for your response and clarification.

    I understand that it's currently expected behavior for Meta Box AIO to require at least one extension to remain active. However, I’d like to share some feedback:

    I use Meta Box via Composer to have more control over what's loaded in my project. My goal is to use only the native field types, without the additional extensions, ensuring a lighter setup and the flexibility to enable or disable features as needed.

    In this case, it doesn’t make sense to be forced to keep at least one extension active if I only want to use the custom fields. It would be great to have more flexibility and be able to deactivate all extensions without having to disable the entire plugin.

    Thank you for considering this suggestion.

    in reply to: ℹ️Behavior when disabling feature #48638
    Infolu OfficialInfolu Official
    Participant

    New information: I’ve noticed that, in practice, Meta Box IO does not allow disabling all extensions at the same time. Even if there are posts registered with the MB Custom Post Type extension, I’m able to deactivate it — but only if at least one other extension remains active.

    This means the plugin requires at least one extension to stay enabled, which can limit flexibility for users who prefer managing post types via code or other plugins.

    Is there a way to disable all extensions without having to deactivate Meta Box IO entirely?

    Infolu OfficialInfolu Official
    Participant

    I tried to use defini within my plugin so that when metaboxAIO loads it recognizes the license, but AIO sometimes says that no license was found.
    if ( !defined( 'META_BOX_KEY' ) ) {
    define( 'META_BOX_KEY', 'ABCDEFGHIJKLMNOPQRSTUVWXYZ123456' ); // Your Meta Box license key.
    }
    I was thinking that Metabox AIO could retrieve the key directly from a wp_options entry, this way my plugin would enter the license directly into the database.

    Infolu OfficialInfolu Official
    Participant

    Guys, any news about this?

    in reply to: License Invalid + Error in Meta Box AIO #41762
    Infolu OfficialInfolu Official
    Participant

    Guys, I came to this topic for the same reason, I need a way to activate the metabox io with a key, it is integrated into my plugin and using define( 'META_BOX_KEY' doesn't seem like a good thing to do

    Infolu OfficialInfolu Official
    Participant

    Guys, I came to this topic for the same reason, I need a way to activate the metabox io with a key, it is integrated into my plugin and using define( 'META_BOX_KEY' doesn't seem like a good thing to do

    in reply to: Problems with columns when displaying taxonomies #40459
    Infolu OfficialInfolu Official
    Participant

    Hi Peter, below is my complete code.

    just reinforcing I have no problems saving the data in the database.

    My only problem is that it doesn't display in the post column when I use taxonomy_advanced

        if ( ! class_exists( 'MB_Custom_Table_API' ) ) {
            return;
        }
    
        global $wpdb;
        MB_Custom_Table_API::create( "{$wpdb->prefix}postmeta_changelog", [
            'summary_content' => 'LONGTEXT NOT NULL',
            'description_content' => 'LONGTEXT NOT NULL',
            'information_content' => 'LONGTEXT NOT NULL',
            'taxonomy_label' => 'LONGTEXT NOT NULL',
            'taxonomy_type' => 'LONGTEXT NOT NULL',
            'taxonomy_status' => 'LONGTEXT NOT NULL',
            'close_date_time' => 'LONGTEXT NOT NULL',
    	] );
    in reply to: Problems with columns when displaying taxonomies #40444
    Infolu OfficialInfolu Official
    Participant

    Hi Peter, in the image the value you see is not circled because I did a test
    the value that appears is because I used the 'type' => 'taxonomy', if I use the taxonomy_advanced it does not display in the column, below my code

    function ims_home_register_meta_boxes_post_type_changelog( $meta_boxes ) {
    	global $wpdb;
    	$meta_boxes[] = array(
    		'id' 			=> 'default',
    		'title' 		=> __( 'Information', 'ims-home-i18n' ),
    		'storage_type' 	=> 'custom_table',
            'table'        	=> $wpdb->prefix.'postmeta_changelog',
    		'post_types' 	=> array( 'changelog' ),
    		'context' 		=> 'normal',
    		'priority' 		=> 'high',
    		'fields' 		=> array(
    			array(
    				'id' 	=> 'summary_heading',
    				'type' 	=> 'heading',
    				'name' 	=> __( 'Resume', 'ims-home-i18n' ),
    			),
    			array(
    				'id' 	=> 'summary_content',
    				'type' 	=> 'textarea',
    				'rows' 	=> 2,
    			),
    			array(
    				'id' 	=> 'heading_description',
    				'type' 	=> 'heading',
    				'name' 	=> __( 'Description', 'ims-home-i18n' ),
    			),
    			array(
    				'id' 	=> 'description_content',
    				'type' 	=> 'textarea',
    				'rows' 	=> 4,
    			),
    			array(
    				'id' 	=> 'information_heading',
    				'type' 	=> 'heading',
    				'name' 	=> __( 'Technical information', 'ims-home-i18n' ),
    				'desc' 	=> __( 'Technical Information comprises data and items as well as important instructions and guidelines for agents.', 'ims-home-i18n' ),
    			),
    			array(
    				'id' 			=> 'information_content',
    				'type' 			=> 'textarea',
    				'rows' 			=> 6,
    				'clone' 		=> true,
    				'add_button' 	=> __( 'Add more information', 'ims-home-i18n' ),
    			),
    			array(
    				'id' 	=> 'divider',
    				'type' 	=> 'divider',
    			),
    			array(
    				'id' 			=> 'taxonomy_label',
    				'type' 			=> 'taxonomy',
    				'name'			=> __( 'Label', 'ims-home-i18n' ),
    				'desc' 			=> __( 'Select the label and version of the log', 'ims-home-i18n' ),
    				'taxonomy' 		=> 'changelog_label',
    				'field_type' 	=> 'select_tree',
    				//'remove_default' => true,
    			),
    			array(
    				'id' 			=> 'taxonomy_type',
    				'type' 			=> 'taxonomy_advanced',
    				'name' 			=> __( 'Type', 'ims-home-i18n' ),
    				'desc' 			=> __( 'Select the type of the log', 'ims-home-i18n' ),
    				'taxonomy' 		=> 'changelog_type',
    				'field_type' 	=> 'select',
    				'remove_default' => true,
    			),
    			array(
    				'id' 			=> 'taxonomy_status',
    				'type' 			=> 'taxonomy_advanced',
    				'name' 			=> __( 'Status', 'ims-home-i18n' ),
    				'desc' 			=> __( 'Select the status of the log', 'ims-home-i18n' ),
    				'taxonomy' 		=> 'changelog_status',
    				'field_type' 	=> 'select',
    				'remove_default' => true,
    			),
    			array(
    				'id' 			=> 'close_date_time',
    				'type' 			=> 'datetime',
    				'name' 			=> __( 'Log close time', 'ims-home-i18n' ),
    				'desc' 			=> __( 'Log closing date and time.', 'ims-home-i18n' ),
    				'inline' 		=> false,
    				'timestamp' 	=> false,
    			),
        	),
      	);
      	return $meta_boxes;
    }
    add_filter( 'rwmb_meta_boxes', 'ims_home_register_meta_boxes_post_type_changelog' );
    in reply to: Autocomplete fields #28971
    Infolu OfficialInfolu Official
    Participant

    In other words, I have hidden fields in this post type, which information must be inserted when saving the mb frontend form.

    in reply to: Autocomplete fields #28969
    Infolu OfficialInfolu Official
    Participant

    Hi Long, what I need is that when I save a form the field I specify is automatically filled in, for example

    On my site page there is a function that captures the ip of the visitor I want that when I click on save form from mb frontend , this information is saved in a metatag of my post

    Today in my back-end when I go to my post-type and register a new post when saving I have fields that automatically save information.

Viewing 15 posts - 1 through 15 (of 57 total)