GunnyRet

@mbrsolution, Thanks for the suggestions. I deleted the .htaccess file via cPanel. Saved the permalinks and generated a new .htaccess file. On reactivating the plugin, it immediately takes me to 127.0.0.1.

@wpsolutions, I can go into the tables, and follow your advice. However, I am not the only user affected. One of my customers/clients for our non-profit says when she tries to login, she is getting the same result. This is affecting all my sites.

Another thing I noticed, is that when I tried to access the login page from a public wifi, I am blocked in the same manner. I CAN login when I get home, but only IF AIOWPS is disabled.

I am finding “several” instances of .htaccess. May I ask what folder the .htaccess file SHOULD reside? I’m wondering if it is possibly “misfiled”; causing the errors.

I appreciate both of your suggestions.

I LOVE AIOWPS, but if I can’t fix this, I’ll have to find another solution. I HAVE to be able to allow my clients the capability to login to create applications to apply for our programs that support employers wishing to hire Veterans.

One of the things I really use this plugin for is that it allows me to manually approve new registrations.

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

Ok. I found an .htaccess file that was recent. It didn’t have any reference to AIOWPS in the code. I was hopeful that it was going to resolve the issue. As soon as I reactivated AIOWPS, it sent me to 127.0.0.1 again.

I’m not sure where in ALL the various settings this has been messed up. I see there are several settings that may be used to direct users to 127.0.0.1 under certain instances.

I manage 5 different sites, and this seems to have affected all of them when AIOWPS is enabled. Maybe I should just switch to another security plugin.

I may have figured out the issue. aiowps wasn’t listed in the .htaccess file. However, I found a line that somehow inadvertently combined another url I manage:

RewriteCond %{HTTP_USER_AGENT} ^(.+)$
RewriteCond %{SERVER_NAME} ^gunnyretneovets\.com$ [OR]
RewriteCond %{SERVER_NAME} ^www\.gunnyret\.com$

Naturally, this isnt the entire .htaccess file. I just wanted to give you a snippet of where the error was buried. I’ll have to try to new .htacess from another location, and see if I still have errors.

Will keep you posted.

Thanks.

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

Sorry for my slow reply. I’ve been trying to resolve several website’s issues while a family member is hospitalized. Didn’t want you to think I didn’t appreciate your input.

Question before I proceed with the above tips.

Can I not customize the content like this?

“{userContent}

Thank you for your membership application!
It has been received. It will receive a simple review for completeness and accuracy prior to being forwarded to the First Vice Commander for further processing.”

My understanding was that when I use the above, the user will see whatever information they submitted, AND they will receive the additional information depicted above, in their email.

OR – Should I only have {userContent} in the text area?

Thanks,
GunnyRet

• This reply was modified 7 years, 1 month ago by GunnyRet.

Good morning! I had a similar error and I realized that I enabled debugging in a plugin the yesterday. As soon as I disabled the debugging mode, the errors disappeared in both admin and public view.
“Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method IS_IU_Import_Users::process_csv() should not be called statically in…”
I didn’t reveal my entire error string because my problem is now resolved.

@grumblenz, thanks for your suggestion. I contacted GoDaddy and they were able to go in and deactivate my plugins. Next, they helped me change my admin password so that I could remove CLEF and and I had a “redundant” security plugin installed and they suggested it may have inadvertently caused a conflict. I removed that as well. I apologize I didn’t have an opportunity to update my status on this issue until now due to some family medical issues, business meetings and wind-generated power outages in my area.

Again, thank you very much for taking the time to offer an alternative resolution.

Have a great evening.

I hope my reply helps someone else!

[ Signature moderated ]

Thank you. I think I’ve identified the root cause. I will see if someone there can help fix it.

I appreciate the nudge in the right direction.

Right, I was there and it shows the current one as installed, but I don’t see any way to uninstall it.

I was just trying to draw upon an analogy of how I expected the uninstall to look and feel in Themes.

Ok. thought it was going to be a simple fix. I’m using WordPress and hosting on Go Daddy’s cPanel Linux. I have the aforementioned them installed. I thought this Theme would appear in a list so I could uninstall, much like any other plugin.

I don’t really see “Uninstall” as an option. Am I overlooking something really obvious?

Thanks again. Will let you know shortly how it goes.

Thanks for the quick reply, sterndata. I’m very new to WordPress (no kidding). If I reinstall it, does that trash my site’s current setup, or just help the backend files reload?

I will go run a backup first, of course.