Jump to content

rule

Members
  • Content count

    60
  • Joined

  • Last visited

  • Days Won

    1

rule last won the day on August 26 2018

rule had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Any idea how to get rid of the following error? Although there's no functionality hit, it keeps on flooding our error log making it difficult to monitor for other errors. [20-Sep-2019 16:03:21 UTC] PHP Warning: Illegal string offset 'iso_code_2' in /home/user/public_html/includes/modules/shipping/zones.php on line 121 121 $dest_country = $order->delivery['country']['iso_code_2'];
  2. rule

    HoneyPot Captcha

    Is it possible to extend the module by including a filter to catch domain names used by spammers for emails, i.e. similar to the bad words filter but for account creation rather than contact form? The same domain names seem to be used over and over again.
  3. rule

    HoneyPot Captcha

    @Jack_mcs Unfortunately, this latest change does not improve the situation. We are still seeing about 15 new fake accounts each day. More importantly, using CSF to blacklist IP addresses also appears to be futile.
  4. rule

    International SEO

    @Jack_mcs Could you possibly provide insight into this SEO stuff?
  5. rule

    International SEO

    Wait. This file is the Canonical Header Links module we discussed above when you said it was fine to keep it on. So should it be disabled or not and why?
  6. rule

    International SEO

    Could you please clarify the exact name of the HT module that should not be used? Doesn't look like we have it enabled but just want to make sure. That would be much appreciated.
  7. rule

    International SEO

    Are you referring to Canonical Header Links? Why not? As for Google, their main recommendation is the use of the following HTML tags. <link rel="alternate" hreflang="lang_code" href="url" /> <link rel="alternate" hreflang="x-default" href="default_url" /> The difficulty with our setup is that we use SEO URLs, which rewrites product and category names with /de preceding the German versions. How could we make an HT module insert such tags dynamically based on the selected language?
  8. Live shop so just quoting from the error log. This is the most commonly reported warning. [01-Mar-2019 17:30:17 UTC] PHP Warning: Illegal string offset 'iso_code_2' in /home/xxx/public_html/includes/modules/shipping/zones.php on line 121
  9. rule

    International SEO

    Good point. This is probably the most important issue here, since it may directly affect a website's indexing. @burt any ideas on how to make the two compatible?
  10. rule

    International SEO

    @JcMagpie That's exactly what we are after. Adding hreflang itself is easy but making it take different forms (en-us, de-de, fr-fr) is what we are not sure about. How would we make the attribute take different values depending on the language selected? @Hotclutch Our content is actually multi-lingual. Not just boiler plate.
  11. rule

    International SEO

    @Hotclutch What additional information is required? This is not an SEO question per se. We just need to modify core code to add the hreflang attribute. Does anyone know how to do this?
  12. rule

    International SEO

    We would like to ensure that foreign language versions of our website are served correctly for purposes of international SEO. Default code structure is below. <!DOCTYPE html> <html lang="de"> <head> <meta charset="utf-8"> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no"> <title>Größentabelle</title> <base href="https://domain.com/"> <link rel="canonical" href="https://domain.com/size-chart.php/de" /> </head> The reason we suspect this not to be entirely correct is because many analytics tools also require a hreflang attribute (e.g. hreflang="de-de"). Not sure how big of a deal it is for the search engines. Is there a way to modify osC output to be consistent with the above?
  13. rule

    ULTIMATE Seo Urls 5 - by FWR Media

    Noticing quite a few of the following in our error log. PHP Fatal error: Uncaught Error: Call to a member function store() on boolean in /home/xxx/public_html/includes/modules/ultimate_seo_urls5/main/usu5.php:78 Stack trace: #0 [internal function]: Usu_Main->__destruct() #1 {main} thrown in /home/xxx/public_html/includes/modules/ultimate_seo_urls5/main/usu5.php on line 78 Line 78 reads as follows. $this->getVar( 'cache' )->store( $this->getVar( 'registry' )->store() ); Is this a PHP 7.2 related error yet again?
  14. rule

    Keeping Error Logs Clean

    @MrPhil We are on the latest release with all the bug fixes in place. Looks like the warnings mentioned above are extra.
  15. rule

    Keeping Error Logs Clean

    @ecartz The zones shipping module is ancient and may very well be the cause of the second warning. Taking out ['iso_code_2'] leads to shipping cost not being displayed anymore for that module. How/where do we set $order-delivery to be an array?
×