Bruno Cantuaria

First, thanks for the answer.

I understand how tracking in email marketing service works, but I can’t agree with that. As you said, it’s not stored on your servers, but once user clicks on the URL it will go first to your server, and only then to the proper website.

There is simply no reason to do any kind of track in URLs that should be completely private. A simple rule to avoid any URL related to password would fix that.

At minimum, your plugin should let users know that when using the SMTP feature, administrative links with private information will pass through SendinBlue servers.

Not sure if you found the solution, but after a lot of struggle, I discovered the parameter render_callback that we can use while registering the block with register_block_type . It basically calls a function that you can use to render the block as you wish on the frontend. Example:

function gutenberg_register() {

    register_block_type( 'custom-gutenberg/custom', array(
		'editor_script' => 'custom-gutenberg-js',
		'render_callback' => 'custom_gutenberg_render_html',
    ) );

}

function custom_gutenberg_render_html( $attributes, $content ) {
	return html_entity_decode($content);
}

• This reply was modified 6 years, 2 months ago by Bruno Cantuaria.

Hi @wfalaa,

Thanks for the answer.

We’ve disabled the plugin since then. Today, I activated it again and the slowness didn’t came back, but we’ll keep an eye and will update here if necessary.

As about the Diagnostics, everything is green.

Best

Hi @westonruter thanks in advance for the response.

Yes, if I remove the is_amp conditional and switch to the non-Amp link, the stylesheet is loaded with the expected changes.

No, actually it’s just 6KB. The strange thing is that it’s not loading any stylesheet at all. If I remove the function that’s hooked with the wp_enqueue_scripts for the amp’s dequeue and enqueue, it still show the page with no stylesheet at all. So, not even the default stylesheets are used.

If I switch to the legacy mode, the default stylesheet is loaded as we expected.

I’ve installed the alpha version and something interesting occurs. With everything set, when I hit the amp URL it redirect backs to the default URL with ?amp_validation_errors=28 appended to it. But no validations erros are logged anywhere.

That was fast. The new version fixed it!

I’m having this issue as well. It seems that, when an action should trigger the Cache Clearing but the user is not an administrator, a wp_die() is triggered with the message “Must be admin”

For example, you can setup the cache to clear after a new post is created, then login with an editor or author and try to publish a new post. The post got published but the error appears. If you disable the option and repeat the process, the error does not occurs.

Amazing!

You’re the best!

Sure!

One picture says more than a thousand words ??

Hi,

Since version 2.4 all the premium options are now free and included in the main plugin.

Enjoy ??