netzgestaltung

well – i have my account here and will stay here. i use ff in a case where my client has it before but occasions like this will prevent me from evaluating any pro purchase in future. have you ever looked into his issue instead of only hinting to another plattform? bye.

and now nobody knows the answer. thank you for nothing. i research the same topic, coming from DDG.
i can not imagin that the WP-Team prevents you from posting a helpfull link.

• This reply was modified 2 weeks, 6 days ago by netzgestaltung.

Hi,

meanwhile i noticed that my changes led to bypass the captcha on the login page (with wrong letters, empty field wont bypass) so i removed the action parameter condition entirely:

    if (!session_id()) {
      if ( $GLOBALS['pagenow'] === 'wp-login.php' ) {
        session_start();
      } else {
        @session_start(['read_and_close' => true]);
      }
    }

So that solution maybe needs more testing on other occurances then on the login page. Is it used elsewhere or somehow for loggedin users?

• This reply was modified 5 months, 2 weeks ago by netzgestaltung.

Hi,

i debugged that topic furthermore as the proposed solution stopped the registration page captcha from working.

so thats what i currently came up with:

    if (!session_id()) {
      if ( $GLOBALS['pagenow'] === 'wp-login.php' && ! empty( $_REQUEST['action'] ) && $_REQUEST['action'] === 'register' ) {
        session_start();
      } else {
        @session_start(['read_and_close' => true]);
      }
    }

• This reply was modified 5 months, 2 weeks ago by netzgestaltung.

Looks like you reinvented or still not fixed the issue – when i look at ~/wp-content/plugins/captcha-code-authentication/wpCaptcha.php on line 41 it still not fixed.

these snippets are regarded to a previous version, you should make your own thread to receive better help

• This reply was modified 9 months ago by netzgestaltung.

Hi there,
while running wp 6.5.2 with Captcha Code 3.1 i also get such messages in the backend.

I searched in all my plugin files for “session_start()” and found it at ~/wp-content/plugins/captcha-code-authentication/wpCaptcha.php on line 41 inside the class WP_Captcha_Code.

I researched to that particular message and found that german page:
https://www.viresist.org/wordpress-tutorials/kritische-warnung-eine-aktive-php-sitzung-wurde-erkannt-in-wordpress-erhalten/

in general it says: try to add the option “‘read_and_close’ => true” to it and see if it works.

from

if ( !session_id() ) {
  @session_start();
}

to

if ( !session_id() ) {
  @session_start(['read_and_close' => true]);
}

I changed it the hard way in your plugin-file and the message goes away.

EDIT: But then the Captcha gets bypassed on Login.

So maybe an also mentioned session_write_close(); sowehere else is needed.

kind regards
tom

• This reply was modified 10 months, 3 weeks ago by netzgestaltung.
• This reply was modified 10 months, 3 weeks ago by netzgestaltung.

Yes it also is applicable for checkboxes which i quick-fixed with:

remove_action( 'wpcf7_swv_create_schema', 'wpcf7_swv_add_checkbox_enum_rules', 20, 2 );

• This reply was modified 11 months, 1 week ago by netzgestaltung.

Email was sent, also had no fatal errors with 6.0.3 on PHP 7.4.33 with Smart Grid Plugin installed also.

Sorry i was a bit absent the last days.
I will check out 6.0.3 on my dev instance.

Hi,

i get this:

 Fatal error: Uncaught Error: Call to undefined function c2p_get_form_key()
in /wp-content/plugins/post-my-contact-form-7/public/class-cf7-2-post-public.php on line 177

let me now when you fixed it, i will then check back.

• This reply was modified 1 year, 4 months ago by netzgestaltung.

Hi,
i will check it today on a dev site of mine and report back.
cheers

looks like single posts using a template file of the plugin instead of its usual theme when not in maintainence mode. i suggest that the call of that template has changed.

https://github.com/Codeinwp/wp-maintenance-mode/blob/master/views/wpmm-page-template.php

no. you have to disable this piece(and reenable it after work done), remove the string in .htaccess or add a custom rule instead of the disabled one (copy/paste from .htaccess with the removed string)

Hi there,
just a short reminder that the pull requests are still open ??
kind regards
tom