wpismypuppet

You are welcome! Settings will be different for each plugin for each site. That’s done by default… the harder part is making each site under multisite the same :). Luckily that’s not your case. Glad everything worked out!

Well I hate to be the bearer of bad news… but the plugin you claim to have downloaded is not a well written plugin. Two things it does (which is unnecessary)…

1. It creates it’s own table, which appears to be used for subscribers???
2. It creates it’s own redirect to a custom theme and set of files.

My guess is the deactivate and uninstall of the plugin did not remove all traces of the plugin. In fact I know this to be true, as there is no function called when the plugin is deactivated (a huge no-no in plugin development). Therefore, the table probably still exists, and other things that this plugin has created have not been removed, such as:

The redirect checks it’s table for a flag. If the flag is set to 1, then it calls a redirect.php page. It also sets an option (found in your wp_options table) called “rmmuc_nht_plugin_do_activation_redirect” and sets that to true. And there is a whole slew of other issues…

But since you are not technical and don’t know jargons, as you say (love that comment, BTW 🙂 ), then you’ll need someone to help you fully remove this plugin, and I don’t think it’s going to be easy to do through this forum.

With any luck, you might have a backup of the site before this plugin was installed? Otherwise you could FTP to your site, check the plugins folder, and make sure the entire “maintenance-mode-and-under-construction-page” folder is deleted. That might be your only option without having to hire someone.

You should not use @import to get the parent stylesheet to your child theme. You should properly enqueue the style in the functions.php file:

https://codex.wordpress.org/Child_Themes

<?php
function my_theme_enqueue_styles() {

    $parent_style = 'parent-style';

    wp_enqueue_style( $parent_style, get_template_directory_uri() . '/style.css' );
    wp_enqueue_style( 'child-style',
        get_stylesheet_directory_uri() . '/style.css',
        array( $parent_style )
    );
}
add_action( 'wp_enqueue_scripts', 'my_theme_enqueue_styles' );
?>

Using wp_enqueue_style is the cleanest way to enqueue all styles as it has ways of checking for the existence of the file to be enqueued, and gracefully and silently fails in the event that it cannot find the file in question.

Of course there is something you can write in the functions.php file. That’s what I meant by “look for the hook”. However, since the build in widget is practically in-editable, you’ll basically be re-writing the plugin. See here:

https://wordpress.org/support/topic/edit-meta-widget-in-theme-file?replies=12

Here’s another way to customize the default meta widget code. Perhaps if you do it this way, you won’t need the added Meta Widget Customizer plugin at all 🙂

https://guillaumepaumier.com/2012/01/26/customizing-the-wordpress-meta-widget/#Code

Because it’s a plugin that’s causing the issue, you would need to contact the plugin author and see if there is a hook to call for when the “names” of the links are being printed to the screen. Or, you can look through the code and look for the hook yourself. I doubt it was coded in such a way, so you’re probably looking at a JS solution, since you don’t want to hack the plugin in case of future updates.

You can FTP in and disable all plugins by renaming the plugins folder. Then you can see if it allows you to log in.

Comments should speak for themselves… 90% of this code is the standard WordPress walker class… only a few lines have been added. You’ll see those lines between the comments.

// Custom walker to allow drop down menus to be in columns
class Column_Walker extends Walker_Nav_Menu {
	function start_lvl( &$output, $depth = 0, $args = array() ) {
		$indent = str_repeat("\t", $depth);
		$output .= "\n$indent<ul class=\"sub-menu\">";
		// Add this piece to start to wrap all the <li> tags in a <div class="col">
		if( $depth == 0 ) {
			$output .= "\n$indent<div class=\"col\">";
		}
		// End
		$output .= "\n";
	}
	function end_lvl( &$output, $depth = 0, $args = array() ) {
		$indent = str_repeat("\t", $depth);
		// Add this piece to close the wrap of all the <li> tags in a <div class="col">.
		// It should be noted that an extra empty <div> is included to allow for clearing any floated column.
		// Feel free to remove '$indent<div class=\"clear\"></div>' if you have your own clear method
		if( $depth == 0 ) {
			$output .= "$indent</div>\n$indent<div class=\"clear\"></div>";
		}
		// End
		$output .= "$indent</ul>\n";
	}
	function start_el(&$output, $item, $depth, $args) {
		global $wp_query;
		$indent = ( $depth ) ? str_repeat( "\t", $depth ) : '';
		$class_names = $value = '';
		$classes = empty( $item->classes ) ? array() : (array) $item->classes;
		$class_names = join( ' ', apply_filters( 'nav_menu_css_class', array_filter( $classes ), $item ) );
		$class_names = ' class="' .  esc_attr( $class_names ) . '"';
		// This piece checks to see if you added a class of 'col-break' to any menu item in the admin area.
		// If you did, it breaks the column and starts a new one BEFORE the item is displayed
		if( stripos( $class_names, 'col-break' ) !== false )
			$output .= '</div><div class="col">';
		// End
		$output .= $indent . '<li id="menu-item-' .  $item->ID . '"' . $value . $class_names . '>';
		$attributes  = ! empty( $item->attr_title ) ? ' title="' . esc_attr( $item->attr_title ) . '"' : '';
		$attributes .= ! empty( $item->target ) ? ' target="' . esc_attr( $item->target ) . '"' : '';
		$attributes .= ! empty( $item->xfn ) ? ' rel="' . esc_attr( $item->xfn ) . '"' : '';
		$attributes .= ! empty( $item->url ) ? ' href="' . esc_attr( $item->url ) . '"' : '';
		$item_output = $args->before;
		$item_output .= '<a' . $attributes . '>';
		$item_output .= $args->link_before . apply_filters( 'the_title', $item->title, $item->ID ) . $args->link_after;
		$item_output .= '</a>';
		$item_output .= $args->after;
		$output .= apply_filters( 'walker_nav_menu_start_el', $item_output, $item, $depth, $args );
	}
}

If you want to ignore subcategories, then you need to set “hierarchical” to false (it’s true by default). Also beware of “hide_empty” as that is also set to true.

But in your code, it looks like you have “child_of” set to 40, which means you are already looking at a subcategory set. Is this a typo?

It would make more sense if you gave us an example of how the structure is set up in the back end, and how you want it to look with this code. If you are looking at getting the top level items that are children of 40, then it’s a different situation from getting top level items that are not children of anything.