Forum Replies Created

Viewing 15 replies - 1 through 15 (of 62 total)
  • Thread Starter Mr. Deb

    (@silumant)

    So you mean there will be no performance difference, if i use older redis 5 version VS using latest redis 7 version.

    Whatver version redis i use, i will get same performance/speed. Do u mean this ..

    Thread Starter Mr. Deb

    (@silumant)

    Dear @threadi ,

    I sent a support ticket to Softaculous (As i always use this tool to install WordPress)

    As per them, this issue is due to wordpress latest version 6.1+. There is nothing wrong in my server or Softaculous. It is a bug related to wordpress & some plugins.

    Then sent me this link: https://ww.wp.xz.cn/support/topic/php-error-action_scheduler_run_queue/

    I also checked that link (& inside there r other links too) and found the issue is really related to wordpress (& may be some plugins) and it is not solved yet.

    Plz check that link from your side in ur free time and kindly give me your opinion.

    P.S: Thanks to your assurance in previous msg, I am not giving much important to this minor error. Ignoring it and keep doing my work. I guess it will be solved in upcoming updates, may be take few months too😀.

    • This reply was modified 3 years, 1 month ago by Mr. Deb.
    Thread Starter Mr. Deb

    (@silumant)

    Dear @threadi

    I recently found out that my premium theme is compatible with PHP 8.0 & not with PHP 8.1 or 8.2. Initially I desired to use PHP 8.2 thinking it will give best performance/speed. But now I have to use PHP 8.0.

    So I guess this might be causing cron related errors. Am I right?

    Thread Starter Mr. Deb

    (@silumant)

    Thanks for reply @xue28

    I recently found out that my premium theme is compatible with PHP 8.0 & not with PHP 8.1 or 8.2. Initially I desired to use PHP 8.2 thinking it will give best performance/speed. But now I have to use PHP 8.0.

    So I guess this might be causing woocommerce related deprecated errors. Am I right?

    So if my assumption is correct, I have to use PHP 8.0. But before this I have one question.

    So my question is:

    Is performance (speed is my priority) of PHP 8.0 is almost similar to PHP 8.1 or 8.2. I know that updated PHP are better, but I think in overall performance; they are almost same. Am I right?

    P.S: After clearing about this PHP confusion, almost all my worry/overthinking will be cleared. I can use woocommerce without any worry🤩. And later upgrade my PHP when my theme became compatible with it.

    Thread Starter Mr. Deb

    (@silumant)

    Thanks for reply @dell123 .

    As a newbie in server related knowledge; initially I thought PHP change may make irreversible changes to website files/database.

    But now thanks to you & other experts; all my worry/overthinking are cleared now. Also as usual I always make a full site back up before changing PHP version.

    I have one question which I think you may answer as an expert.

    I recently found out that my premium theme is compatible with PHP 8.0 & not with PHP 8.1 or 8.2. Initially I desired to use PHP 8.2 thinking it will give best performance/speed. But now I have to use PHP 8.0.

    So my question is:

    Is performance (speed is my priority) of PHP 8.0 is almost similar to PHP 8.1 or 8.2. I know that updated PHP are better, but I think in overall performance; they are almost same. Am I right?

    P.S: After clearing about this PHP confusion, almost all my worry/overthinking will be cleared.

    Thread Starter Mr. Deb

    (@silumant)

    No, there was no PHP fatal error. Rather I got only PHP Warning &  PHP Deprecated. I guess this is due to using PHP 8.1 or 8.2.

    I also recently find out that my theme is currently compatible with PHP 8.0 & not fully with 8.1 or 8.2. So I I guess even if wordfence is compatible with PHP 8.2; due to my theme I may be getting this error.

    So below are my decisions:

    1. I will Use PHP 8.0. But one doubt. Is performance (speed is my priority) of PHP 8.0 is almost similar to PHP 8.1 or 8.2. I know updated PHP are better, but I think in overall performance; they are almost same. Am I right?
    2. Ignore any PHP warning/Deprecated related wordfence error (Not important to solve now, may check later, this will save lots of my time). And make support ticket if only I got any fatal error. Am I right?

    P.S: plz answer to my questions in serial manner so that I will have no confusions later. Thanks in advance.

    Thread Starter Mr. Deb

    (@silumant)

    Thanks for replay @xue28 .

    Initially I thought the main culprit is PHP 8.2; but I am getting it in PHP 8.1. Also you might be right about external theme/plugins causing this issue.

    So regarding your debugging suggestions, I will do this later as I have very less time now (Busy in a major project). And following your suggestion is consume some hours of my time. So I will do it in free time & update you here.

    In meantime, can you just assure me that I can safely ignore such deprecated warning errors without any worry or overthinking that it will cause some major problem in my website? If I can ignore now And keep doing my website works like configuring etc, This will save lots of my time. Also later I will follow your debugging instructions in my free time.

    Thread Starter Mr. Deb

    (@silumant)

    Thanks for replying @sterndata

    I was little confused with your reply of my this question & your answer:
    Am I right or wrong PHP version make irreversible changes ?
    Yes, you are right or wrong. 
    //This might be a mistaken reply. As there is no either right or wrong reply. Either you misunderstood my question or I misunderstand your replay. Haha.

    Whatever, this does not matter anymore. After your reply & talking with some other experts; I have reached to this conclusion:

    1. PHP changes does not make  irreversible changes to website files or database. So no need to worry/overthinking.
    2. I should stick with PHP 8.1 as many experts recommended to use it instead of 8.2. And I should follow experts instead of my over thinking mind. haha.

    Thread Starter Mr. Deb

    (@silumant)

    Regarding your question “check where “action_scheduler_run_queue” comes from”, I am thinking about asking directly to hosting/c-panel/softaculous. My suspicion is either c-panel or softaculous. Mostly on softaculous.

    Whatever, as per your suggestion + my own thinking; I have decided to not give much priority to such errors as they will not cause any harm to my website. I will ask about this to hosting/c-panel/softaculous in my free time.

    Thread Starter Mr. Deb

    (@silumant)

    Any response from dear wordfence team: @wfsupport and @wfjanet.

    I am telling something more about me for better understanding: My server is a powerful VPS + C-panel + centos 7 (Will upgrade to AlmaLinux later) + lsip. Regarding me, I have some good tech knowledge related to wordfence. As an entrepreneur, while securing website with wordfence, I just follow respective docs/articles/videos & if required ask for support. Also my c-panel is not subordinating any mandatory plugins. I always install WP via softaculous and there are always 2 plugins (Akismet & hello dolly; but deactivated) + default 3 wp theme. So I guess this might be some temporary bugs in my system or in others.

    As I was testing wordfence in one of my test site, I have uninstalled it. But due to requirement from woocommerce team regarding another support request related to similar woo error in their plugin, I have created woocommerce status system report: https://sharetext.me/uplyplsnde
    //I think this might help you. If you still want your wordfence related report (if it have any options), then I can send it too.

    What I think: Suspects are PHP 8.1 or 8.2; my server or latest version wordpress or wordfence or God know😂</img>

    Due to some frustrated past bad experience in breaking my website & then unable to solve them, I generally tend to worry/overthinking😂 that these errors means something wrong in my website or it will cause some severe irreversible problem in future.

    ✅</img>So This is My New Real Most Important Question: In future, if not getting such repeated errors, then can I just safely ignore such errors without any worry or overthinking like mentioned above? And keep doing my website works like configuring etc, This will save lots of my time.

    Regards,
    Deb😃</img>

    Thread Starter Mr. Deb

    (@silumant)

    Thanks for replying @roxannestoltz . My server is a powerful VPS + C-panel + centos 7 (Will upgrade to AlmaLinux later) + lsip. Regarding me, I have some good tech knowledge related to woocommerce. As an entrepreneur, while creating woocommerce website I just follow respective docs/articles/videos & if required ask for support. Also my c-panel is not subordinating any mandatory plugins. I always install WP via softaculous and there are always 2 plugins (Akismet & hello dolly; but deactivated) + default 3 wp theme. So I guess this might be some temporary bugs in my system or in others.

    Like you, I also tested again in fresh installation (using PHP 8.1 this time). I installed a theme (ohio premium theme from themeforest) & its required plugins. It required woocommerce & thus I configured it.

    And unfortunately, I got similar repeat errors. (For few times only, not more. May be come in future as not tested much. I just configured Woo recently)

    [09-Apr-2023 01:16:28 UTC] The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.
    [09-Apr-2023 01:16:28 UTC] The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.
    [09-Apr-2023 01:16:28 UTC] The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.
    [09-Apr-2023 01:16:28 UTC] The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.
    [09-Apr-2023 01:16:28 UTC] The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.
    [09-Apr-2023 01:16:28 UTC] The Automattic\WooCommerce\Admin\API\Options::get_options function is deprecated since version 3.1.

    Regarding what you asked for for debugging:
    System Report: https://sharetext.me/uplyplsnde
    Fatal Error log: There was none except a name test-log.log (& when I click view, nothing happen)

    What I think: Suspects are PHP 8.1 or 8.2; my server or latest version wordpress or woocommerce or God know😂

    Due to some frustrated past bad experience in breaking my website & then unable to solve them, I generally tend to worry/overthinking😂</img> that these errors means something wrong in my website or it will cause some severe irreversible problem in future.

    So This is My New Real Most Important Question: In future, if not getting repeated errors, then can I just safely ignore such errors without any worry or overthinking like mentioned above? And keep doing my website works like configuring etc, This will save lots of my time.

    Regards,
    Deb😃</img>

    • This reply was modified 3 years, 2 months ago by Mr. Deb.
    Thread Starter Mr. Deb

    (@silumant)

    Thanks for reply @threadi . My server is a powerful VPS + C-panel + centos 7 (Will upgrade to AlmaLinux later) + lsip. Regarding me, I have few such tech knowledge related to wordpress. As an entrepreneur, while creating website I just follow respective docs/articles/videos & if required ask for support.

    I know something about how cron jobs works. Generally after my website ready, I disable the wp cron jobs via using codes in wp-config & create custom cron jobs in my c-panel (Source: google & it works).

    Like you, I also tested again in fresh installation (usng PHP 8.1). But unexpectedly I too did not get the errors either😇😂. Also my c-panel is not subordinating any mandatory plugins. I always install WP via softaculous and there are always 2 plugins (Akismet & hello dolly; but deactivated) + default 3 wp theme. So I guess this might be some temporary bugs in my system or in others.

    Due to some frustrated past bad experience in breaking my website & then unable to solve them, I generally tend to worry/overthinking😂</img> that these errors means something wrong in my website or it will cause some severe irreversible problem in future.

    So This is My New Real Question: In future, if not getting repeated errors, then can I just safely ignore such errors without any worry or overthinking like mentioned above? And keep doing my website works like configuring etc, This will save lots of my time.

    Regards,
    Deb😃

    🔴IMP updates: In the fresh installation, I installed some plugins & then got this error. Thinking about ignoring.

    • This reply was modified 3 years, 2 months ago by Mr. Deb.
    • This reply was modified 3 years, 2 months ago by Mr. Deb.
    • This reply was modified 3 years, 2 months ago by Mr. Deb.
    Thread Starter Mr. Deb

    (@silumant)

    Your 2nd snippet worked very well.

    .single-product div#tab-description *:not(h1,h2,h3,h4,h5,h6) {
        font-size: 16px !important;
    }
    

    Thank you very much @amiralifarooq for your help💗✌. God bless you.

    Thread Starter Mr. Deb

    (@silumant)

    Hi @amiralifarooq

    I do not want to increase the size of product short description. I want to increase the size of the product summery (or long description), which you can find in the product tabs: https://prnt.sc/zbJkI4yDifrZ

    Thread Starter Mr. Deb

    (@silumant)

    I found this snippet & it seems working: https://www.businessbloomer.com/woocommerce-override-single-product-settings/

    So I guess my problem is solved.

Viewing 15 replies - 1 through 15 (of 62 total)