Hi,
I am having the following problems:
1. The "prove your humanity" answer box on my WP forum registration form is uneditable, preventing users from entering any values.
2. To edit my website of WordPress I must sign in on my website due to (1.) I cannot do anything on WordPress even though I am logged in on my account and can access the dashboard..
Could you help me fix point 1 and tell me if point 2 is normal?
My website: https://scripotime.com/
Thank you for your help 🙂
1.
try this code
#wpforo #wpforo-wrap #jetpack_protect_answer {
padding: 0 0 0 5px!important;
}
add it to custom css
Dashboard > wpForo > Settings > Colors & Styles > Custom CSS
@tutrix Thank you for your answer unfortunately to access my wp foro settings on WordPress I have to go through the wp foro login which contains the issue I mentioned...
Where is the /community/ slug in all forums and topics?
@dimalifragis I am new to wo foro it’s seems that I disabled the community slug.. any advice on how to fix the problem I mentioned ? Thank you!
@gregpev I'm not sure what you have touched. Maybe in Boards? Is there the Slug Empty?
@dimalifragis whatever it is I cannot modify the settings of the WP foro pluggin because it directly displays the wp foro login which cannot be completed due to error I mentioned 🙁
@gregpev Well, use ftp or your Cpanel to disable or delete (for now) that plugin of humanity check (!). Is it Jetpack?
Or ask your hoster to help you out.
Another solution.
Open the website console, insert the code provided by Tutrix here, and you'll be able to answer the "Prove your humanity" challenge.
Please watch this short video attached below.
Ok I managed to get rid of the math question to prove my humanity. But now the problem is that any change I try to make of my wordpress account from the wordpress dashboard forces me to login via my website login page and that my credentials do not seem to work which creates a never ending loop. Any idea on how to solve this problem? many thanks for your help !!!
@gregpev Still this doesn't seem like a wpForo issue.