remedy17

I can swear that I was doing exactly what Childify Me plugin just did, but I know I should be humble enough to say it must be something I have missed. Both @debshadovitz (Deb), and @d4z_c0nf (Rocco) are awesome humans. I really appreciate you guys. Yes, it worked when I used the great plugin Childify Me by Rocco. You will not know how much time I have wasted on this. I love Customizr theme. It looks like there is another reason to love it even more: its community.

• This reply was modified 6 years, 5 months ago by remedy17.

Heateor, please disregard this. I created a new ticket for this as I thought that was more appropriate. I could not delete this.

Heateor,
I am very appreciative of this free plugin, but couple of issue are kind of defeating the purpose you set of the plugin. I am sorry to say these things to you.
1. After login (I use FB), the user basically loses his/her place since it takes them to the top. I tried several things including adding #commentform div in comment area thinking that it might be looking for that anker tag. I deactivated all my plugins, but no luck.
2. Post social login, it still does not show the comment box and it still says login to comment(this is approximation, not exact wording). Only the hard refresh can bring it. User will not know to do that and it is too much to ask. I tried everyone’s suggestion of putting ExpiresByType text/html “access plus 0 seconds” in my .htaccess file. No luck. Even if this were to work, it would sacrifice the site’s performance. These two issues leaves my in a dilemma of whether I should abandon the plugin I love.

Hi akyusa01,

I did allow me to create a ticket. It looks like you fixed your ticket creation page. Thanks. Ticket created.

Heateor,
Thanks for reminding me to check and clear cache, but that did not fix the problem. I bulk inactivated Akismet Anti-Spam, Comment Mail, Comment Rating Field, Custom Post Type UI plugins. I was able to inactivate and activate back Super Socializer then. I then was able to save the secret keys. Oddly it would not allow me to to activate back the above plugins. But I noticed a message from Super Socializer that I need to go do what is in Step 9 of your documentation page. I went to FB and did that and hit OK on the message that was displaying in WP Admin.

I was able to activate my plugins again. Here is what I am thinking: Super Socializer is not allowing some normal WP activities when it is displaying any notice in admin. Even my first issue may have been related to that. There maybe an element of conflict with one of the above plugins, but I am thinking only when Supper socializer is showing some admin notice. I might be wrong, but I wonder if that can ring a bell in your head.

Question: I noticed that your step 11 was telling us to enter App Domains our url with and without the www – we left that blank previously. It rejected my url with or one without www saying it does not match site url or something like that. Would that affect the authentication?

Heateor, I might add that the plugin would not inactivate either. I guess I would need to try it via cPanel file manager and rename this baby.

Heateor,
In the same vain, but my problem is even more serious. After the last upgrade, the plugin asked me to enter secret keys of Google and FB. Twitter was good already. My problem is not being able to find the keys, it is being unable to save the keys. It does not give you any message why it is not saving. It seems to be saving, but just refreshes back to blank. I have tried to do them one at a time. No luck. I also tried to capture the error in php log, nothing shows up there.

I just applied your latest update today hoping you may have addressed the issue. Basically I can’t use FB and G+ in my site now. What is your advice?

Having the similar problem here, but mine occurs in different PHP file.
[22-Feb-2018 21:39:49 UTC] PHP Notice: Undefined index: SCRIPT_NAME in /…/…/public_html/wp-content/plugins/wp-security-audit-log/classes/Sensors/PluginsThemes.php on line 105

I captured this at login attempt as admin, that is what caused this error. I was having perhaps a different problem with my site, the notorious “Sorry, you are not allowed to access this page” issue, when I tried to login as admin, but could be related. I can login from another computer though.

Heateor,
Your answer is great and your plugin is amazing. I disabled the traditional registration in WP Admin > Setting > General as you suggested.

I had this plugin on my site for about 2 years and I am surprised I did not know this until today, November 20, 2017. My question is this to Mike: You said the last version you released was 1.5.8.13, but I found out the version I have is 1.5.8.14 (before I nuked it.)

The malicious guy may have compromised me already with 1.5.8.14? I guess what I am asking is: have you had a chance to check what changed for 1.5.8.14?

Thank you for the great plugin while it lasted.

This is exactly the problem I am having today. Enabled Memcached in cPanel, when I go to WordPress admin SG Optimizer setting and go to the bottom hit enable memcache, error appears: “Could not disable memcache!”, First, I am not even trying to disable memcache, but the error text reads as if I am. Secondly, why is this appearing? It would be nice if it tells me that my site can’t use this cache type or something that makes sense.

This review is an example of how to review plugins in WP repository. Why doesn’t everyone do it like this rather than just state empty short platitudes such as “Great plugin”, “Works great”, “Works as advertised”, “It did not work for me”, “Just what I have been looking for”, “Gives me error”, etc…

Those are definitely not reviews. They are just votes. While I am okay with votes, I believe if my goal is to help out many future potential users, I need to explain why I like/dislike the plugin.

Your point by point review was just what I wanted to decide whether or not to install this plugin. You have saved me time it takes to install and try it out. I would have come to the same conclusion having tried it.

Kudos!

Forgot to add the output — here it is:

“The following plugins/themes are not compatible with PHP 7.0. myCRED
FILE: /home/…./public_html/wp-content/plugins/mycred/assets/libs/parsecsv.lib.php
—————————————————–
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
—————————————————–
111 | WARNING | Use of deprecated PHP4 style class constructor is not supported since PHP 7.
——————————————————

Sorry for that typo error. The meant to type Profile Builder Hobbyist plugin. I like this plugin and your obviously.

Thanks for the assurance in your response that it might be non-critical issue. I will Keep you updated if I learn new information on my end as well.

Correction Michael. It seems to create these error when I activate Amazon Auto Links plugin – which is a great plugin like yours. As I mention above I don’t think I had to do anything except activating this plugin. Would you have any idea why? I will also contact the author of that plugin based on your answer. I hope I can keep both plugins, two of my most favorite plugins.