druppel

I didn’t read it anywhere, maybe it’s just my changing perception and this solution always worked. That seems to be more plausible, since WordPress always depended on mail(), which is built into PHP, as far as I know.

The built in mail() functionality is an alternative that works for me, but that is my hosting provider who set everything up OK…

Contact form 7 (with file upload) is the plug-in I use for the messaging part, and it just works without any smtp plug in.

I just needed to white-list the sending email address from my web-host in Google Apps (Admin console>Google Apps>Settings for Gmail>Advanced Settings) under Spam.

Some thing seem to have changed in 3.9 regarding mail(), breaking all smtp plug-ins, but luckily it is now all built in, and the dependency has shifted from the smtp data you put in toward the configuration of your host. Well, for me anyway ??

I’ve been sending through the WP SMTP plug in successfully until 3.9, but I was told on this forum by another user that he had an upgraded 3.9 install with a fresh install of the plug-in and it worked.

The built in mail() functionality is an alternative that works for me, but that is my hosting provider who set everything up OK…

Contact form 7 (with file upload) is the plug-in I use for the messaging part, and it just works without any smtp plug in.

I just needed to white-list the sending email address from my web-host in Google Apps (Admin console>Google Apps>Settings for Gmail>Advanced Settings) under Spam.

Some thing seem to have changed in 3.9 regarding mail(), breaking all smtp plug-ins, but luckily it is now all built in, and the dependency has shifted from the smtp data you put in toward the configuration of your host. Well, for me anyway ??

Please add ipv6 support, I see Wordfence has encountered this question over a year ago….

Thank you very much for building the plug-in, I’ve used it a lot, but when things start to malfunction, regardless of who could be blamed, it gives me peace of mind to know everything is now built into my child theme. ??

Only when one has a Piwik-installation separate from a WordPress-installation one could follow the next steps:

On ones main installation:
– log in to Piwik.
– make a new website inside Piwik.
– copy the tracking code of the new website.

On ones WordPress-site:
– make a Child Theme
– copy footer.php from the template theme folder to the child theme folder
– paste the tracking code from the main Piwik-installation just above </body> in the child theme’s footer.php

WP-Piwik adds a reference at the webpages to piwik.js at the root of the server, which is not found (404).

OK, I just checked and it’s working now, here’s my config:
Piwik is fine.

I’ve added the tracking code from my main Piwik install for my WordPress site to my child theme’s footer.php, just above </body>.

WP-Piwik shows a wrong SiteId and it doesn’t update itself.

Time to uninstall and do as I did…

Dit anyone contact Piwik already? The’ve made the upgrade, WP-Piwik did as did WordPress. Three points of possible failure.

The tracking link seems to be added ok though, so this must be a Piwik problem, not a WP-Piwik problem.

I have reinstalled the plugin yesterday, I used the same sited and Api key as is stated on my main piwik install for my wordpress site. Did that yesterday and this morning the counter was still stuck at 0…

I take it the tracking code is not added to WP.

Now I’ve switched to the twenty fourteen theme, the plugin seems to work. Uploading files is not really working, but I’ve tried making it work using the file_upload parameter in php.ini, though php mail is slow at my host, so I’ll see tomorrow.

I’ve upgraded because I wanted the file upload functionality.

@swapan_mkt:
Oh… and restore a backup of your database, because many settings are saved there…

@swapan_mkt:
Yes, I remember having that problem once too…
I never will change the directory again, nor the login hours and I will not hide the login no more.

If you have a backup of your WP installation’s .htaccess and wp_config.php file, please put them back, rename the directory back to wp-content and delete the better-wp-security plug in from the plug in directory.

Try to log in now. If you can, redo the Better Better Securiy plug-in and try to keep to my recommendations in the first paragraph.

At least… I believe this is how I fixed it.
Hope it helps!

Why are you opening yet another topic with a negative feedback? It looks like you are a forum spammer working to make Better WP Security look bad, every post you make is incredible and full of stuff that seems to have the goal of keeping novice WordPress administrators from trying this plugin.

Well, I too am a novice WordPress administrator (1 year) and I can tell everyone that by installing the Better WP Security plug-in, with all it’s holistic features is very good if your aim is not to get your WordPress site hacked.

Maybe Gμ?rD??? aims at disinformation so to have more unsecured WordPress websites.