fob

Good news update: Data is back in Google Analytics. Clearing the cache in WP Dashboard Analytics helps now to refresh the missing plugin data even in WP.

Google introduced the Google Analytics 360 Suite these days. May be the ‘yesterday option’ is not fully supported anymore? Perhaps only in the new payed accounts?

In my case it was normally set to Europe/Berlin (DE). Yesterday and the day before I recognized that the traffic per hour was shown until 5 o`clock (pm), nothing more.
The corresponding Google Accounts were showing the same. Strange…

Today – well, may be it’s too late for me tonight, but today it doesn’t look very promising what I found in Google Analytics (Standard) accounts. For example the traffic per hour seems not to be available anymore. It now seems to be aggregated like it is done for all the other days (in periodical views). Will have a deeper look tomorrow…

• This reply was modified 7 years, 9 months ago by fob.
• This reply was modified 7 years, 9 months ago by fob.

Oh. That makes sense.

Thank you very much for the quick reply and all your work on this great plugin. I can confirm it works as you explained it.

– This topic is closed. –

You are welcome!

Hi,

Nofollow Case by Case starts working right after activation.
There is no need to configure anything.

You might want to have a look into the source code of your comments to see if nofollow has gone after activating the plugin. You can also try a modified link (replace nofollow like this: one_comment_authorlink/dontfollow) to check if the link still works with this modification. If it works, your output is filtered by the plugin. This means the plugin works.

Best regards
Oliver

You are welcome!

I`m very sorry, Ken. It was my fault. Thanks for sharing the bug.

I quickly had a look into the plugin code and found out that it currently checks if you have a version <= 3.5 or newer. So for versions between 3.5.0 and 3.6 the plugin currently delivers a wrong result as these versions are not aware of the new escape function delivered with the new core system. This must have been the reason for the error massage you have seen. I will have to correct that for other people who have not updated their core yet.

Thanks and best regards
Oliver

Hi,

wp_slash was introduced with WordPress 3.6. Did you try to deactivate the other (outdated) plugin already and see what happens? There might be issues with its pre save filter.

I do not know your other plugins but it`s fine to disable the NFCBC jQuery scripts if you neither need a target_blank (new window) option nor have to clean up accidentially modified links from other plugins. The core functions of Nofollow Case by Case are PHP functions.

Hi Monika,

I`m sorry to be late with this. I did not modify any comments yet in WP 3.6 and had “a lot of fun” with BETA changes instead so that I did not recognize the modifications of the pre save filter earlier.

Thanks to Halina I received a great video by email today, explaining her issues with the comment editor.

The fix is on the way. Please feel free to upgrade.

Great idea!

Fixed by the way many bugs which came up with nonused jetpack functions (WYSIWIG not showing, path errors, …) in subdirectory installations.

Nice. Attachments seem to have been fixed, too. May be I just have a cache problem for elder stats left. Today and yesterday already look like normal. Great! ??

Problem seems to be nearly solved. Is it?
I currently see the loading title thing only for attachment pages.

now showing “#895 (loading title)”

Yep, but wrong domains seem to be properly filtered now. Looks much better than before… ??

(@niska: May be I`m wrong but I do not think that importing posts has anything to do with it.)