Jason Kemp

@codingowl If you add an email address at the bottom of the listing – like this.

Email: email@email

The contact form you are using should “see” the email address. I used the Contact Form 7* to do this. I wanted visitors to the site to be able to contact listings but not actually read the email address in the listing so I used an “WP Mailto Links” plugin to disguise the plain text version. This means that all emails sent using the contact form are tagged so the listing owner knows the source of the traffic. * It may work differently if using Ninja or Gravity forms – I didn’t test those.

In my view you don’t need to wait for anything – just add the email address, use Contact form 7 with this plugin and you are done.

I haven’t tried this but it may also work if you add email as a custom field and keep it hidden off the listing page.

@prmyapps Hi there MJ,

You are reporting a problem that was not caused by the actual plugin which is misleading for the plugin author who has found the issue in the theme.

You said

“Isn’t my post title still correct, regardless of whether the root cause is the theme or your plugin?”

It would have been better to have titled your review something like “Formatting problem I’m having with WP twenty sixteen”. Understand you didn’t know that at the time and may not be able to edit the rating or the title now but…

It is important to know if an issue is caused by a plugin or something else and I understand you don’t know about styling or CSS but you have penalised a plugin author who has gone above and beyond to help you and it is not the plugin at fault. These support ratings and queries are best when they enable plugin / theme authors to improve their code.

Knowing what the root cause is significant. It is not a “regardless” thing. Knowing the difference helps everyone make better plugins and stops people wasting time looking in the wrong places.

I had the same issue on one of my sites. Renamed the plugin to restore the site and will now check the version of PHP. However other sites all updated without crashing so good to know about the PHP change. I note there were some changes to make “Yoast SEO” compatibility better so for the time being i have deactivated that also.

Hi Tom,

This had me stumped for a while as I needed to do a couple of clear css cache after the “Reset Widget Styling” was ticked. For some reason that button needed to be on.

This is now resolved thanks. Also worked for the update to 2.2.2

Hi Tom,

Have a look at the menu using 2.2.1 on this test version of site
https://sciencemediacentre.co.nz/members/

And how it should look on (production version) https://sciencemediacentre.co.nz
which is using the version 2.1.5

I did the usual clear cache step but the result is definitely not what we want.

Max Menu is just on the home button.

To be fair there is now a list view option which suits me better.

“view your settings in list view by clicking the “list” icon.”

It looks like it may have been a path error or somthing to do with the wp-config.

Have reinstalled after editing wp-config and all working again so resolved.

@aaron I’ve had a chance to look at the error logs.

The only thing I’ve been able to find was “Call to undefined function” fatal error caused by Super Cache plugin on line 425

Backend fatal error: PHP Fatal error: Call to undefined function get_supercache_dir() in /var/www/vhosts/sitenamedeleted/httpdocs/wp-content/plugins/wp-super-cache/wp-cache.php on line 425\n

I have now removed Super Cache from that site tell I can find out what the issue is and reinstalled the latest version of iThemes Security Version 5.4.4and everything is working as it should.

It is possible that Version 5.4 caused the problem but for me this is resolved.

what @phil C said. I liked the old version but if we have to have this new UI please give us a choice.

Thanks @marcelo Pedra
and thanks @aaron

I will look into the error logs. Suffice to say that version 5.4.2 of this plugin just came out so I’m testing it on about 10 other sites before I come back to the one that broke.

Can we have the old interface back the new UI just looks like bloat to me. I had no trouble configuring it before. It wasn’t broken. Now it is unusable.

I can see a number of other users are getting similar errors. I can’t see any obvious error logs yet. The theme is based on Kubrick and is very light on resources usually.

I resolved the site error by deleting this plugin which is a bit drastic

I believe 5.4 has introduced a huge memory error. I’m also starting to think this plugin is getting bloated. No need for the new pretty screens especially if it sucks resource and tips over the entire admin section which is what happens.

When a user logs in they get a flash of the dashboard but then nothing – no access to posts or anything. This appears to have happened on multiple sites. For now I have deleted the plugin as unsafe to use.

I believe it is compounded if using SuperCache.

Hey everyone – See @tracey answer above –

“f you go to the bottom of the Analyticator settings page you can clear the plugin cache – that just worked for me on one site”

Clearing the plugin cache solves this problem. I did it on a couple of sites several weeks ago and it all works well now.

Hey @leanderbraunschweig you need to check the fix and mark this as resolved.

Since my earlier comment I switched to W3 cache for a couple of months. As soon as I stopped using Super cache the Analyticator graph updates worked fine but I don’t like the W3 cache plugin. Today I switched back to Super Cache and Analyticator showed the old data from back in August as before. As Tracey & rossagrant have noted clearing the analyticator cache right down the bottom of the settings page will refresh the graph widget.

I’m not sure if I will have to repeat the clear Analyticator cache process but at least there is a fix and it does confirm that there is a clash with the Super cache plugin.

In my view I think this topic is resolved.

Same issue here. Curiously not on all sites though. I use WP Super Cache and wondering if there is now a clash there. Shows data up to August 16th in 30 day view. If I change to 60 days it will show up to 2 weeks ago. pretty sure that August 16 was when the plugin was last updated. That broke something so that no data is getting through.