farinspace

@mhsupermom, I would be more than happy to try to help out …

I did a few tests with the current RELEASED plugin version v0.1.2 and the latest wordpress version v5.3 and have not found any issues. Please feel free to contact me directly at dbegunoff at gmail dot com and i can try to help further.

Side note …

We published this plugin what seems like ages ago, since … we have iterated over several versions “internally” (e.g. NOT RELEASED), you can have a look at what the plugin looks like now, here is an excellent example https://www.mist.com/resources/ (as of 2019-12-09) which is significantly different. You are welcomed to give this new version a try, better to use it on a new installation going forward.

https://ratiobuddy.com, is a great little tool I use often …

@tober1, thanks for the bug report.

Indeed a bug. I’ve fixed the issue in version 1.4.3

Please review and let me know if that works for you.

@thomasvalera, let me know if you have any more questions?

Closing this issue, however, please feel free to reopen if you need further assistance.

@onetechway,

Definitely a bug. I will get this fixed right away.

can you try the following for now: [nooz view="auto" use_pagination="yes"]

The custom CSS section can be difficult to manage a lot of CSS rules.

Another option is to create a custom.css (you can name it what ever you want), and use it directly on the site. This will allow you to manage all your rules from a single file and make it easier to edit.

Here is a quick example on setting that up (this requires that you have the ability to upload changes to you custom.css file when you make edits, and that you can modify your functions.php file):

1) In your theme folder create a custom.css file:
/wp-content/themes/mytheme/custom.css

2) In your /wp-content/themes/mytheme/functions.php file add:

add_action( 'wp_enqueue_scripts', 'my_custom_styles' );
function my_custom_styles() {
    $file = 'custom.css';
    $handle = 'my-custom';
    $src = get_stylesheet_directory_uri() . '/' . $file;
    $deps = array();
    $ver = @filemtime( get_stylesheet_directory() . '/' . $file );
    // https://developer.wordpress.org/reference/functions/wp_enqueue_style/
    wp_enqueue_style( $handle, $src, $deps, $ver );
}

@karthickr,

The following should work to remove css/js from non-nooz pages. You will have to adjust the array for pages where the [nooz] shortcode is being used.

add_action ( 'wp_enqueue_scripts', 'unload_nooz_plugin_scripts', 11 );
function unload_nooz_plugin_scripts() {
	global $post;
	$is_release_post_type = 'nooz_release' == get_post_type();
	$is_news_page = isset( $post->post_name ) && in_array( $post->post_name, array( 'news', 'news/press-releases' ) );
	if ( ! $is_release_post_type && ! $is_news_page ) {
		wp_dequeue_style( 'nooz-basic' ); // basic theme css (no js for basic theme)
		wp_dequeue_style( 'nooz-outline' ); // outline theme css
		wp_dequeue_script( 'nooz-outline' ); // outline theme js
	}
}

Again thanks for the insight, you have brought up a good point about not loading nooz css/js on pages where they are not needed. The detection of the [nooz] shortcode could be tricky .. but I will add this to the TODO list for inclusion as core functionality to Nooz.