• Resolved mnbilgi

    (@mnbilgi)


    This way I get two different errors:

    Notice: Trying to get property ‘user_id’ of non-object in /home/u9252356/public_html/wp-content/plugins/wp-w3all-phpbb-integration/class.wp.w3all-phpbb.php on line 2813

    Notice: Trying to get property ‘user_lastmark’ of non-object in /home/u9252356/public_html/wp-content/plugins/wp-w3all-phpbb-integration/class.wp.w3all-phpbb.php on line 2814

    Can you help me?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author axew3

    (@axewww)

    going immediately to check for this, 2.2.4 will be released in few hours and i’ll return back in reply here to report applied fix about this …
    Thank for the report just in time!

    Plugin Author axew3

    (@axewww)

    I have not understand how it could be possible the error come up, may can you also report which settings you activated into plugin, if into just released 2.2.4 it still has not not been fixed.
    The function about this has been (just little) re-coded to avoid any possible further execution, when not needed/required.
    If these vars aren’t setup at the point that are executed (and you report) there is in fact no reason to follow with code execution.

    2.2.4 has been released, so let know if still in trouble

    if still not fixed, how you experienced:
    integration run as linked users, or NOT linked users?
    which options active into main plugin page?

    Cheers!

       if(!empty($phpbb_u)){
        $user_id = $phpbb_u->user_id;
        $last_mark = $phpbb_u->user_lastmark; // when/if the user have mark all as read
       } else {
       	return;
       }
    Thread Starter mnbilgi

    (@mnbilgi)

    I’m trying right away. thank you for your interest.

    Plugin Author axew3

    (@axewww)

    2.2.6 should really fix everything and i assume is eligible to be a marked
    STABLE

    (… yeah! until next reported bug! (i guess this is the right STABLE time!))

    Please let know if something still wrong you may note

    Thread Starter mnbilgi

    (@mnbilgi)

    Hi Awex3,
    The problem has been fixed with the new version.

    Thanks, Regards :).

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘2 Different Error’ is closed to new replies.