Tamás

Hey, I apologize for getting back to you so late.

Could you please provide some more information on the CF7 and WP versions and which PHP version you use? Then I can have a detailed look at the issue and hopefully come back with a solution.

Hey Muirén,

thanks for reaching out, that’s what the support forum is for ??

If I understand correctly there are two issues to address: The first one is the styling of the text of the list elements / links in the blogroll. The code above tries to address another (pseudo-)element after the text, with the ::after selector. If you omit the ::after it should work.

The other thing is the ::before pseudo-element showing up in weird spaces is because the selectors match every list element on the whole page. There is a way to narrow it down to the blogroll by prepending the classname of the widget .widget_links

So the additional CSS code would look like this:

.widget_links ul { list-style: none }
.widget_links ul li::before
{
  content: "\25EA";
  display: inline-block;
  width: 1em;
  margin-left: -1em;
}
.widget_links ul li {
  color: black;
  font-weight: 400;
  font-size: 14px;
  font-family: 'Montserrat';
}

Please let me known if this solves your issues or if other things pop up.

Best regards, Tamás

First of all, thank you for your patience. I tried and tested some stuff regarding this error and found that it only seems to happen, if there is output / headers sent / error happening in another plugin or theme. This also affects the function of the captcha, without a session no solution can be assigned to the user. Maybe you can check, if any plugin or theme is causing trouble before session_start() is called?

Nonetheless I added a check if headers are sent before session initialization so session_start() is not called if output happened before.

Wonderful, so I mark this issue as resolved.

Hey, thank you for reporting. I’m trying to figure it out, would it be possible to provide a little bit more detail, e.g. how you use the captcha (comment form, cf7, elementor)?

Thank you!

Hey @peter09z ,

sorry for the delay in answering, I was offline for a few days and only now got to work on it again. The error should be fixed, the class in question got renamed. I would appreciate your feedback, if this resolves your issue.

And thank you for the positive feedback!

Best regards, Tamás

@boatfl Thank you very much for taking you time and test it again! I Really appreciate it and am happy about the results ??

Regarding the typo, I tried to fix it a long time ago, but somehow missed the opportunity ??

Thank you again and wishing you also a wonderful day!

Hey Claus,

thanks for pointing out this issue! I found a bug in my oldschool autoloader and fixed it for the next release, which should be published as I am writing here ??

Best regards, Tamás

Hey @boatfl and thank you for answering. It is understandable you ditched the plugin after running this problem, so even more I thank you in advance for testing it again. I will leave the ticket open, so you can leave your feedback ??

Hi @taruk, thank you for your Feedback!
I was able to locate an error which has appeared in the last version and fix it. With the new version 1.2.3 the fatal error should be gone.

@boatfl Is your problem with the plugin on this one site still existing?

Hey and thank you for reaching out and I’m glad you’re overall happy with the plugin.
Unfortunately it is hard to tell from the distance why this is happening in this specific case and what (theme / plugin / setting) is interfering . Maybe you would send me some more details (via DM) about the used themes / plugins on that installation and I can setup a test environment to try to reproduce it.

Hey Daniel,

just wanted to give you a short update that the function to display the field for logged in users is implemented. You find the switch in the elementor widget settings (default is off).

Have a great weekend

Tamás

Hi Daniel,

I’m glad, we could clarify it ??

Yes, this would definitely be an important addition since the displayed strings and messages can’t be translated via TranslatePress which has some kind of WYSIWYG-editor for it and which now does not display this field. Being able to also display it for logged in users also makes testing more transparent and less irritating.

Thanks for the feedback. I will have a look at this, but it will take a little time.

Kind regards,
Tamás

Hi Daniel,

thanks for reaching out.
There is actually one case, where the field is not showing up in the form, that is when the user is logged in. Have you tried to visit the page with the form as a non-logged-in user (e.g. in another browser)?

Sorry, if this was unclear. I added a description of this behaviour to the FAQ section.

Also, I would love to hear your opinion if this should be added as an option to enable the field for logged in users as well.

Best Regards
Tamás

If you manually want to install the plugin, you have to save the ZIP-file and unzip it to you hard-drive. After that you copy the contents into the mentioned directory on the server with an FTP-program (like FileZilla).

Alternatively you can follow these steps to install the plugin through the admin interface:

Automatic Plugin Installation | WordPress Codex