Hello! Still trying to get to the point where the comment section needs no instruction. The issue is the visitors don't know how to use the inline commenting feature. They click on the blue box and nothing happens. They think it doesn't work. People are emailing me, telling me there is something wrong with it. It is a problem for sure. I put instructions in my sidebar and on the home page where I announced this new feature. Even when I reply saying where the login button is and placing three more login links to wordpress, they still don't get it. They come to me asking, Where? The login is too small and not important looking as well as far from the action. If you clicked on the blue comment box and nothing happened, what would you do? Move on. You would think it is broken for sure. You don't even know that you need to look for a login. So I made a google social login. Great directions by the way. Very, very good! Thank you for that. I completed it successfully but later found out the login is in the comment section area?? So small, but again, who would know to look for it or why they need to look for it. Something has got to happen to direct people so they know what to do. Period. I suggested a popup login when they click on the blue comment box. That would be best. Or a login page. Or move them to the login button at the comment section specificially on top of a designated login area with some directions. I don't know but as it is now, it is failing the user test. Did I miss something? Maybe I did, idk. Thanks!!
Dear @sea-odyssey,
Please export the wpDiscuz options and send them to us so we can check the issue. This will export all wpDiscuz settings.
Helpful article: https://gvectors.com/how-to-move-wpdiscuz-options-using-export-import-tool/
We’ll also need the form settings. To export them, navigate to Dashboard > Tools > Export, then export the Form post type.
@asti Ok, I have them. Where do I send them?
You can zip the files and attach them here, or send them to info[at]gvectors.com and let us know once it’s done.
@asti I sent it, thanks
@asti thank you, looking foward ;o)
@asti just within wpdiscuz. Not sure what you mean specifically. You gave me code for some css stuff.
@asti .comments-area{width:auto;}
.wpd-inline-form .wpd-inline-notification {
color: #454545;
width: 100%;
max-width: 100%;
display: flex;
align-content: center;
align-items: flex-start;
}
.wpd-inline-form input{
margin-top: 0;
}
.wpd-inline-form button.wpd-inline-submit {
border: 1px solid #454545 !important;
}
I am not sure what you are looking at. What is supposed to be there that isn't? Nothing changed before or after this code. Thanks tho
@asti I don't know. I don't know what that is exactly to look there. What is supposed to be there that I am missing?
By default, the inline commenting button is not visible for guests if commenting is disabled in the form settings.
On your website, it is somehow being displayed, which may only be caused by template customizations. We’re not sure how the button was made visible.
Please watch this video to see how it works on our website.
@asti Thank you that was the missing piece. After some testing, I unchecked these with success. First screenshot. So these are unchecked now. They were conflicting for sure. I also have a customizer that I messed with but it either took out all comments or put in the comments as a whole.
Looks good, below. No recaptcha on these inline boxes, but there is recaptcha for the comment section. Not sure if it should be on both.
Now, the only issue I have is, lol, I can only see/use the comment section and inline comments if I add /?nocache extension. If I do not, even after clearing cache etc, nothing works. The boxes are not clickable and the comment section is not accessible. I cleared the cache everywhere, wprocket, Flywheel, and regenerated Elementor etc. I do have Cloudflare, but so far, everything is in tune as far as caching through wpRocket. I paused Cloudflare, just to be sure.
Almost there... thank you!
@asti I have wpRocket, Cloudflare, but paused that so that isn't a factor. Any suggestions on how or where? Thank you dearly. Here are some things I noticed, never cache user agents, different URL options, query strings, and cookies. I am trying but really limited. Don't give up on me!
Could you please send the admin login details to info[at]gvectors.com email address? I'll ask the developers to check the issue for you.
@asti Thank you, I sent it.
Please see the error message below:
Error: The password you entered for the username gvVectors is incorrect. Lost your password?
1 attempt remaining.
@asti I sent a reset.
The developers are now able to log in and check the issue. I’ll update this topic once I have some news for you.
We kindly ask you to create a development/staging copy of your website on a subdomain and send the admin login details to info[at]gvectors.com so we can check the issue. It’s difficult to investigate the problem on a live website.
You can use the Duplicator plugin to create the staging site.
@asti I sent it, thank you!!
It also requires popup login information. Please include this in the email content as well.
@asti I sent the login details under the link in the email. I sent another email, explaining. Thanks!
Please contact your hosting support and ask them to disable the server-side cache.
Please see the attached screenshots.
Even with all plugins deactivated, wpDiscuz is still being displayed. This indicates a hard cache on the server side.
@asti Ok, I'll contact Flywheel now. There is a purge everything on Cloudflare I could do. Let me know. One sec.
@asti I have contacted Flywheel and they said I can put the site in development mode but the staging site is essentially uncached already. ...?
@asti try now, thank you!!
You didn’t miss anything — this is a UX issue. If users click the blue comment box and nothing happens, they’ll assume it’s broken. They won’t look for a small login button somewhere else. Instructions in the sidebar won’t help because people don’t read them at that moment.
You need immediate feedback on click: a popup saying “Please log in to comment” with a clear Google login button, or an inline message inside the comment area. The login must appear exactly where the action happens.