christophrado

Thanks for reporting. I’ve just confirmed this myself. Without checking the Flamingo source code, I think it messes with a global variable, and in turn fails when other plugins access that variable. A quick Google search shows that quite a few plugins have this same issue when used along Flamingo.

I have changed CNC’s usage of that variable, which in turn makes Flamingo happy again.

If you’d like to confirm the fix, you can replace the function “manage_admin_views” in /includes/class-cnc-logger.php with this:

	public function manage_admin_views() {
		$post_type = '';
		if( isset( $_GET['post'] ) && ! empty( $_GET['post'] ) ) {
			$post_id = intval( $_GET['post'] );
			$post_type = get_post_type( $post_id );
		}
		if( isset( $_GET['post_type'] ) && ! empty( $_GET['post_type'] ) ) {
			$post_type = $_GET['post_type'];
		}
		if( 'cookie_consent' == $post_type ) {
			// Posts list: remove Quick Edit, remove Edit, add View
			add_filter( 'post_row_actions', array( $this, 'consent_post_row_actions' ), 10, 2 );
			// Bulk actions: Remove Edit
			add_filter( 'bulk_actions-edit-cookie_consent', array( $this, 'consent_bulk_actions' ) );
			// Restore from trash: set status to publish
			add_action( 'transition_post_status', array( $this, 'consent_untrash_status' ), 10, 3 );
			// View screen: Allow only 1-column layout
			add_action( 'in_admin_header', array( $this, 'consent_screen_layout' ) );
			// View screen: Inject js to set title to readonly
			add_action( 'edit_form_after_title', array( $this, 'consent_title_js' ), 100 );
			// View screen: Remove default meta boxes, add consent data
			add_action( 'add_meta_boxes', array( $this, 'consent_meta_boxes' ) );
		}
	}

If testing goes alright, I will include this change in the next release.

I’m seeing the same issue.

I managed to disable those options directly via the database options table. Now that I have all four options disabled via database, I can’t re-enable them via the settings screen as well. The save function just doesn’t seem to work or respect the checkboxes.

Yes, Unbloater is still in development and supported.

I just didn’t feel the need to push out an update just for the Tested tag. The plugin is quite simple, and most of the time no changes are necessary to keep it compatible with the latest WordPress version.

I’ll do this for the next release though, so the plugin doesn’t look stale.

Hi Dan,

I can’t reproduce those issues on the provided site. All the buttons are working fine for me. It kind of sounds like a cache issue, but I can’t verify for sure.

I currently see the “base” styling. You can select a different theme in the plugin’s settings, or roll your own via CSS.

Please note that this plugin is meant as a developer tool, and might not work in all setups without some customization. Please understand that I can’t provide full fledged support in case of specific theme conflicts.

Chris

No, this is not a case that Unbloater was built for. Unbloater can remove specific items from your site, but it’s not an automatic system to remove any unused resources.

There might be other plugins out there that can help you, but I’m not aware of a specific one that I can recommend for this use case.

Hi Steve,

thanks for your feedback. Unfortunately, I don’t think this particular feature is something that would fit the core feature promise of Unbloater, so I don’t think this is something that is going to be added to the plugin.

Maybe there’s some other plugin or code snippet out there that can assist you with that particular situation.

Best,
Chris

Thanks for the suggestions!

Some are kinda already on the idea list, some are less likely, e.g. user enumeration, as I don’t quite see this as “bloat”, but more of a functional thing. I do understand it’s often prevented/disabled, but it’s not quite right for Unbloater.

RSS feeds are already an option – removing the feed links or deactivating them completely.

You are absolutely free to use the code however you like. ??

Hey there,

Unbloater uses the www.ads-software.com translation system – translations are managed via translate.www.ads-software.com.

You can contribute to the plugin’s translations here: https://translate.www.ads-software.com/projects/wp-plugins/unbloater/

You can learn about the basics of contributing translations here: https://make.www.ads-software.com/polyglots/handbook/

Thank you, I appreciate the kind words ??

Thanks for the suggestion. Duotone is a theme-specific feature though, and can be easily managed and deactivated using theme.json. I am currently not planning on adding settings that are available through theme.json.

This is related to the oEmbed provider. I recommend using a plugin such as Disable Embeds if you don’t need or want oEmbed support.

This sounds as if some caching is preventing you from loading the most recent version of your site. On the link provided, I am currently seeing the same version (banner active) with Safari, Chrome and Firefox.

You seem to be using both a CDN and Perfmatters on your site. Make sure you purge all caches of those tools after making changes, so the versions your browsers load are up to date.

The settings are basically stored as an array of options. You can read them from a site by running this:

print_r( get_option( 'unbloater_settings' ) );

Writing options should work along the lines of this:

$settings = array(
'remove_update_available_notice' => 1,
'disable_auto_updates_core' => 0,
...
);
update_option( 'unbloater_settings', $settings );

As of now, all of the options are checkboxes, so it’s only a matter of setting 0 (inactive) or 1 (active) for each option.

Just make sure to include all of the options when saving the settings programmatically, otherwise they’ll be unset.

Changing just one option on a site can be achieved like this:

$settings = get_option( 'unbloater_settings' );
$settings['disable_auto_updates_core'] = 0;
update_option( 'unbloater_settings', $settings );

That’s basically reading the current settings, changing a value and finally saving the changes to the database.

I see the use-case, but it indeed seems a little overkill for Unbloater to have its own import/export section…

All settings are stored in one wp_options field (unbloater_settings) though, so it’s quite easy to read/write those just about with any tool (PHP, or even CLI I guess).

I personally use ManageWP and their Code Snippets feature to set stuff like this on multiple sites. Remotely configuring your sites might be a better approach than to log in to every site and import for each one.