Skip to content

Branda config files need to be uploaded to each site individually #51

@neilpie

Description

@neilpie

We can centralise a set of Branda config options by adding something like the following:

add_filter( 'ub_get_option', __NAMESPACE__ . '\hard_code_branda_options', 10, 3 );

function hard_code_branda_options( $value, $option_name, $default ) {
    if ( 'ub_admin_bar' === $option_name ) {
        $value['logo']['logo'] = false;
        $value['logo']['logo_meta'] = array(
            "https://pie.co.de/wp-content/uploads/2025/12/Pie-P-Social-1-Brown.jpg",
            "400",
            "400",
            false
        );
    }
    return $value;
}

We will need to investigate all of the customisations that have been made via our standard Branda config, and then apply them through a filter such as the above. These new hard-coded settings will then override anything in Branda to prevent us having to make changes to each individual site every time.

Of note, if these subsequently need to be restored or changed on a site-by-site basis, they can be filtered upon at a later priority

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions