Forum Replies Created

Viewing 15 replies - 1 through 15 (of 114 total)
  • Thread Starter allstarsft

    (@allstarsft)

    Thank you, @hashibali Got the New update! Home page back to normal… . Didn’t know when this happened as well . Got a shock..

    My Webhost just informed me PHP 7.4 is deprecated… Is it safe to update to PHP 8.3 the latest — for your plugin?

    Thanks!

    P.S: is this ip address range 83.99.*.* yours ? My site keep getting hits by Google bots and this range of IPs today and it caused my Redis connection to go down…

    • This reply was modified 1 month, 3 weeks ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    And for WP debug.log :

    [01-Oct-2024 09:29:53 UTC] PHP Fatal error:? Uncaught TypeError: Argument 2 passed to Elementor\Element_Base::add_link_attributes() must be of the type array, null given, called in /home/allstars/public_html/wp-content/plugins/bdthemes-prime-slider-lite/modules/general/widgets/general.php on line 2529 and defined in /home/allstars/public_html/wp-content/plugins/elementor/includes/base/element-base.php:407
    Stack trace:
    #0 /home/allstars/public_html/wp-content/plugins/bdthemes-prime-slider-lite/modules/general/widgets/general.php(2529): Elementor\Element_Base->add_link_attributes(‘slider-button’, NULL, true)
    #1 /home/allstars/public_html/wp-content/plugins/bdthemes-prime-slider-lite/modules/general/widgets/general.php(2639): PrimeSlider\Modules\General\Widgets\General->render_button(Array)
    #2 /home/allstars/public_html/wp-content/plugins/bdthemes-prime-slider-lite/modules/general/widgets/general.php(2687): PrimeSlider\Modules\General\Widgets\General->render_item_content(Array)
    #3 /home/allstars/public_html/wp-content/plugins/bdthemes-prime-slider-lite/mod in /home/allstars/public_html/wp-content/plugins/elementor/includes/base/element-base.php on line 407
    [01-Oct-2024 09:29:55 UTC] PHP Notice:? Function ID was called <strong>incorrectly</strong>. Product properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/plugins/woocommerce/templates/single-product.php’), wc_get_template_part, load_template, require(‘/themes/oceanwp/woocommerce/content-single-product.php’), do_action(‘woocommerce_single_product_summary’), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, OceanWP_WooCommerce_Config::single_product_content, wc_get_template, include(‘/themes/oceanwp/woocommerce/owp-single-product.php’), woocommerce_template_single_add_to_cart, do_action(‘woocommerce_simple_add_to_cart’), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, woocommerce_simple_add_to_cart, wc_get_template, include(‘/plugins/woocommerce/templates/single-product/add-to-cart/simple.php’), WC_Product-&gt;single_add_to_cart_text, apply_filters(‘woocommerce_product_single_add_to_cart_text’), WP_Hook-&gt;apply_filters, bbloomer_custom_add_to_cart_single_p in /home/allstars/public_html/wp-includes/functions.php on line 6085
    [01-Oct-2024 09:29:55 UTC] PHP Notice:? Undefined index: title in /home/allstars/public_html/wp-content/plugins/woocommerce/templates/single-product/tabs/tabs.php on line 38
    [01-Oct-2024 09:30:46 UTC] PHP Notice:? Undefined index: title in /home/allstars/public_html/wp-content/plugins/woocommerce/templates/single-product/tabs/tabs.php on line 38
    [01-Oct-2024 09:31:12 UTC] PHP Notice:? Function ID was called <strong>incorrectly</strong>. Product properties should not be accessed directly. Backtrace: require(‘wp-blog-header.php’), require_once(‘wp-includes/template-loader.php’), include(‘/plugins/woocommerce/templates/single-product.php’), wc_get_template_part, load_template, require(‘/themes/oceanwp/woocommerce/content-single-product.php’), do_action(‘woocommerce_single_product_summary’), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, OceanWP_WooCommerce_Config::single_product_content, wc_get_template, include(‘/themes/oceanwp/woocommerce/owp-single-product.php’), woocommerce_template_single_add_to_cart, do_action(‘woocommerce_simple_add_to_cart’), WP_Hook-&gt;do_action, WP_Hook-&gt;apply_filters, woocommerce_simple_add_to_cart, wc_get_template, include(‘/plugins/woocommerce/templates/single-product/add-to-cart/simple.php’), WC_Product-&gt;single_add_to_cart_text, apply_filters(‘woocommerce_product_single_add_to_cart_text’), WP_Hook-&gt;apply_filters, bbloomer_custom_add_to_cart_single_p in /home/allstars/public_html/wp-includes/functions.php on line 6085
    [01-Oct-2024 09:31:12 UTC] PHP Notice:? Undefined index: title in /home/allstars/public_html/wp-content/plugins/woocommerce/templates/single-product/tabs/tabs.php on line 38
    [01-Oct-2024 09:31:37 UTC] PHP Notice:? Undefined index: title in /home/allstars/public_html/wp-content/plugins/woocommerce/templates/single-product/tabs/tabs.php on line 38
    [01-Oct-2024 09:31:59 UTC] PHP Notice:? Undefined index: title in /home/allstars/public_html/wp-content/plugins/woocommerce/templates/single-product/tabs/tabs.php on line 38

    Thread Starter allstarsft

    (@allstarsft)

    And WordPress system emailed me with this link (Technical Error email with Recovery Login) :

    https://snipboard.io/HLMv4C.jpg

    WordPress login page has these errors : https://snipboard.io/uFEM0m.jpg — This url link is actually the Elementor Page link for the Home Page

    Notice: Undefined property: WP_Error::$roles in /home/allstars/public_html/wp-content/plugins/insert-headers-and-footers/includes/class-wpcode-snippet-execute.php(316) : eval()’d code on line 3

    Notice: Trying to access array offset on value of type null in /home/allstars/public_html/wp-content/plugins/insert-headers-and-footers/includes/class-wpcode-snippet-execute.php(316) : eval()’d code on line 3

    • This reply was modified 1 month, 3 weeks ago by allstarsft.

    @saffiretech Thank you very much. ??

    allstarsft

    (@allstarsft)

    Just to add with a screenshot as well — https://snipboard.io/PSh0Mx.jpg

    Have to revert back to old version first for now I guess…. but @saffiretech — please resolve this issue asap.

    Edited — Rolled back to 1.2.1 — https://snipboard.io/0Keh8t.jpg

    Now The archived pages are ok — https://snipboard.io/qc3RBp.jpg

    So next fix — 1.3.1 will have to resolve this issue… which is rather odd… Thanks!

    • This reply was modified 3 months ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    Thank you for pointing this out.. I did not realise disabling REST API will affect Jetpack.

    All is good now. Thanks!

    allstarsft

    (@allstarsft)

    Same problem here with the latest plugin version 1.3.0…. please assist soon to resolve.

    • This reply was modified 3 months ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    Ok, so my impression is correct that Cloudflare only caches the Production site. SO by right, I should deactivate your plugin…. But now I am abit afraid to do that… due to the earlier issues of duplication of the instances. Now at Staging site, your plugin’s Status indicator is Green.

    Thread Starter allstarsft

    (@allstarsft)

    Which in the first place it was wierd. They do not share the same DB. But this happened when I just did the staging/cloning.. After adding the urls coding into the respective wp-config.php, it seems fine now. (Otherwise things are haywired…. OceanWP verification system going haywire — keep asking me if this or that site is long term duplicate or ? … , and other wierd stuff happening that time)

    So Do I keep your plugin enabled on the staged/cloned site?

    Why do I keep asking this question was because, I had the impression that Cloudflare is only for the production site — allstars.com.sg — staging sites with subdomains are not included. So I thought to disable would be better.

    • This reply was modified 5 months, 2 weeks ago by allstarsft.
    • This reply was modified 5 months, 2 weeks ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    Right after cloning or staging the site, the staged / clone site will have its settings or plugins behaviour duplicated across – -somehow. And this caused problems to the Production site — like If I deactivate your plugin at staged/cloned site, the production site will have it deactivated as well .

    Initially I log in from Staged site (WP-admin), instead of going into the Admin backend of the Staged site, it went into the Production site backend instead.

    So am wondering what is the best practice for cloning or staging websites with Super Cache for Cloudflare in use at Production site? Apparently, after staging/cloning the site, I had to also include the url links in wp-config.php — and this work for some time. Now its stable.

    define('WP_HOME','https://owp-s1.allstars.com.sg');
    define('WP_SITEURL','https://owp-s1.allstars.com.sg');

    owp-s1 being the staged site. And I also had to do this to the Production site’s wp-config.php.

    Do I keep your plugin activated in the staged site?

    Thanks.

    • This reply was modified 5 months, 3 weeks ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    @isaumya

    I have temporary retained Wordfence first.

    An update to the issue — It seems that after I unchecked is_frontpage from the Do not cache, the issue doesn’t happen already. (have enabled back Fallback cache)

    Not sure why is that so? Do you have an idea?

    • This reply was modified 1 year ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    Hi @artiosmedia,

    Seems after the Product code latest upgrade version, this error appeared for every plugin that I installed. (During Installation, at the prompt for “Activate Plugin”). Could you please assist to check? Thanks!

    Notice: Undefined index: post_type in /home/allstars/public_html/wp-content/plugins/product-code-for-woocommerce/classes/class-pcfw-admin-settings.php on line 446

    • This reply was modified 1 year ago by allstarsft.
    Thread Starter allstarsft

    (@allstarsft)

    hmm, fyi, I have since done these in your plugin after last Saturday’s error again :

    Do not cache : I unchecked – Is_frontpage (which was not recommended anyway)

    Disabled Fallback cache. (i am not sure what this do?)

    Ever since after doing the above 2 settings, so far the same error did not happen again. Still monitoring.

    Yes, I am using Wordfence as well…. So you are saying just rely on Cloudflare’s WAF is sufficient?

    Thanks.

    Thread Starter allstarsft

    (@allstarsft)

    Dawn on me this morning, I had forgotten to donate! Hehe.

    Anyway, have left a 5 stars review.

    Thank you very much.

    Thread Starter allstarsft

    (@allstarsft)

    Tried to donate earlier but seems the donation via paypal is not supported (I am from Singapore).

    Do you have any other ways for me to donate?

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