• Resolved kyriakos_w

    (@wiseprt)


    Hello,

    I have an issue with vtprd-apply-rules.php. Unfortunatelly the website is not pointing to any domain as is still under developing and i can’t send you the error, so i am paste it below:


    Notice: Undefined property: VTPRD_Rule::$discount_total_qty in /home/USER/public_html/wp-content/plugins/pricing-deals-for-woocommerce/core/vtprd-apply-rules.php on line 1959

    Notice: Undefined property: VTPRD_Rule::$discount_total_amt in /home/USER/public_html/wp-content/plugins/pricing-deals-for-woocommerce/core/vtprd-apply-rules.php on line 1960

    Notice: A session had already been started – ignoring session_start() in /home/USER/public_html/wp-content/plugins/pricing-deals-for-woocommerce/core/vtprd-apply-rules.php on line 87

    This is happening on all products in category page.

    Waiting for your feedback.

    Best Regards

    https://wordpress.org/plugins/pricing-deals-for-woocommerce/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author vark

    (@vark)

    Hi,

    You are seeing php notices and warnings.

    My plugin expressly prevents notices and warnings from displaying.

    Your Host is overriding my plugin’s express command to **not display** these notices and warnings.

    This issue can be resolved by updating the wp_config.php file with the following:

    error_reporting(0);
    @ini_set(‘display_errors’, 0);

    Best,
    Vark

    Thread Starter kyriakos_w

    (@wiseprt)

    i added it in wp_config.php but the problem didnt resolved

    Plugin Author vark

    (@vark)

    Suggest contacting your host, and explaining that they are overriding my plugin’s express command to **not display** these notices and warnings.

    Also Notice: A session had already been started - ignoring session_start() in ...wp-content/plugins/pricing-deals-for-woocommerce/core/vtprd-apply-rules.php on line 87 on the frontend.

    Plugin Author vark

    (@vark)

    (1) make sure that Debug Mode is turned off in the wp_config.php file

    (2) if that doesn’t fix it, add the following in the wp_config.php file

    error_reporting(0);
    @ini_set(‘display_errors’, 0);

    (3) if no joy, Suggest contacting your host, and explaining that they are overriding my plugin’s express command to **not display** these notices and warnings.

    Thank you, but I have tried all those things (mentioned in previous user’s question), but they still show up.
    Why not just get rid of the errors?

    Plugin Author vark

    (@vark)

    Next big enhancement will clear this issue…. Some weeks away though.

    Ok, nevermind, the apostrophes were wrong on display_errors, this is correct:

    error_reporting(0);
    @ini_set('display_errors', 0);
    Plugin Author vark

    (@vark)

    Thanks for the correction

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

The topic ‘Notice undefined property error’ is closed to new replies.