Andrew

There’s no issue. I was just suggesting including a check before saving to prevent the honeypot field having the same name as a regular form field. We had a regular field called ‘your-tel’, but the honeypot was also called ‘your-tel’. So when someone entered into the regular ‘your-tel’ field, it triggered the spam block.

CF7 does an immediate AJAX validation check on the form code to prevent errors when you save. You should have something like this too to prevent field names conflicting.

https://ibb.co/hRvZQXT

https://ibb.co/P97db5K

@rsouzaam thanks for the reply. It is an inherited site and yes, I found that code it the theme! I’ve removed it and the option now displays and I’ve turned of the email summaries.

Thanks!

Yes, that works! Thanks

@chrslcy thanks for spotting this. An update has just been released to fix this bug. Essentially, all the widget settings were being reset when the Editor saved the to-do list.

Hi @chrslcy,

We’ve just released an update to fix the bug where all users were able to view/edit the dashboard widget. This is now limited to Administrators, however, Admins can now also enable/disable editing access for Editors.

Admins can also show/hide the to-do on the frontend for Admins and/or Editors.

We have more ideas in the pipeline and we will take on your suggestion of sending out regular emails to users.

Thanks for your feedback and for using our plugin.

Hi @volker0101,

What line is the actual warning on? Could you provide the full error log please?

What version of WordPress are you on?

Are you using the latest version of the plugin (1.2.0)?

How often does this happen? Does it appear after something you’ve done or does it just appear randomly? I just need some more info so I can try to replicate the issue, as I’ve not come across this issue before.

Works perfectly, thank you!

Thank you for the great review and kind words ??

@care2michelle

You can add your own styling without using a plugin, using PHP and CSS. The plugin has it’s own hook for adding custom scripts to the head of the page:

password_protected_login_head

You can add the code to your child theme’s functions.php. For example, this will change the logo:

add_action("password_protected_login_head", "custom_login_css");
function custom_login_css() { ?>
  <style>
  body.login #login h1 a {
    background-image: url('https://domain.com/wp-content/uploads/2023/01/logo.png');
    width:100%;
    background-size: contain;
    }
  </style>
<?php }

Adding the following hook as well will apply the CSS to the default WP login page as well:

add_action("login_head", "custom_login_css");

@toimisto The plugin has it’s own hook for adding scripts to the head:

password_protected_login_head

add_action(‘login_head’, ‘my_custom_login’);
add_action(‘password_protected_login_head’, ‘my_custom_login’);

This will apply your CSS to both the password protected page and the WP login page.

Hi @someguynamedlou, thanks for the message. We’ll certainly look into adding some styling features into the next update.

I’m glad you like the plugin and find it useful! I would appreciate if you could leave a review letting others know your experience.

Thanks for the great 5 star review @douglaskarr! I’m pleased your whole team finds it useful!

I just wrote a function and popped it in the functions.php on each site (if you’re using a separate child theme for each):

add_action('wp_head', 'arwd_hreflang_head');
function arwd_hreflang_head(){
global $post;
if(is_page()) {
$url = $_SERVER['REQUEST_URI'];
?>
<link rel="alternate" href="<?= 'https://domain.co.uk'.$url ?>" hreflang="en-gb" />
<link rel="alternate" href="<?= 'https://domain.com'.$url ?>" hreflang="en" />
<?php }
}

This adds it to the header on every page on the site. My two sites are exact copies of one another so there is always a matching page on the sister site.

I haven’t heard anything back, so I’m going to mark this as resolved.

Hi @fid2, sounds like it could be a code conflict. I suggest deactivating all your plugins (except this one), then test and reactivate one at a time to see if it one of them is causing the issue.

Although unlikely, try switching to the default theme and test. If you also have a caching plugin, try purging the cache.