Jump to content

Philo2005

Members
  • Content count

    67
  • Joined

  • Last visited

Posts posted by Philo2005


  1. 1 hour ago, Jack_mcs said:

    Did you make the database changes with the google_xml_sitemap_seo_install.php file? If so, it has a delete button. Did you not see that? I would think that button is more obvious than text in the install file. If the button is ignored then the text would be too, most likely.

    Yes you got me 😝 but all works fine 😎


  2. 1 hour ago, Jack_mcs said:

    @Philo20051 - Yes, that file should be deleted. You should have seen a button to delete it when you ran the file.

    2 - Unfortunately, it does not create multiple language map files. There's a way to do it manually but it requires editing files. If that was a one-time thing then it would be Ok for a temp solution. But this addon should be ran frequently so that is not a good solution. I've added this to things to do for the next version but it will not be completed anytime soon.

    @Jack_mcs

    Thanks for the fast respond!

    1 - okay i deleted the file manually, maybe this should be mentioned at the end of point 3) in the "readme.txt"  file of the add on.

    2 - okay thank you for adding it to you to do list, this seems important to me to be present on google in more than one language .

    Have a nice day 🙂


  3. @Jack_mcs

    Your add on works fine to me, thank you for developing it.

    I have some questions to the add on:

    1. After first time installation, can i remove google_xml_sitemap_seo_install.php from the root directory or is it still required?
    2. I have set up 2 languages in my shop, German (default) and English.
        a) Is this add on supporting multi lingual or just one language? 
        b) if only one language is supported, how do I tell google by the "xml files" my English description links eq parameters ?language=de or ?language=en?
            The description of articles, categories and manufactures in my shop are different in german and english!

    Thanks for responding

     


  4. 6 hours ago, raiwa said:

    includes/application_top.php lines 42-44:

    
    // set php_self in the local scope
      $req = parse_url($_SERVER['SCRIPT_NAME']);
      $PHP_SELF = substr($req['path'], ($request_type == 'NONSSL') ? strlen(DIR_WS_HTTP_CATALOG) : strlen(DIR_WS_HTTPS_CATALOG));

     

    So many other module in Phoenix uses $PHP_SELF and they all work fine, this show the acutal page Name e.q. "contact_us.php"!
    Thanks @raiwa


  5. @JcMagpie

    I sorted out the Problem and found it in your hook file JcMgoogleCaptcha.php.

    1. Basically I added first the
    $PHP_SELF
    to the globals for each function:
    listen_injectFormVerify, 
    listen_injectFormDisplay, 
    listen_injectSiteEnd.

    2. Your compare Statements are not correct! 

    (in_array(basename($_SERVER['PHP_SELF']), $this->good_pages)) 

    has been corrected to a proper comparison

    (in_array(basename($PHP_SELF), $this->good_pages))

    3. also I made code cleaning to view nice.

    Now i fixed the previous issue and all works fine,

    This new code solves the Problem how user enters the url:
    www.attias.ch/ishop/contact_us.php
    www.attias.ch/ishop/contact:_us.php/language/en
    www.attias.ch/ishop/contact_us.php?language=en
    All types of entering URLs now work!


    Feel free to see it on my live shop www.attias.ch
    and take over, if you like it.
    see attached file

    JcMgoogleCapatcha.php


  6. On OSCOM CE Phoenix v1.0.4.0 shops there is the option

    Use Search-Engine Safe URLs

    in admin section / Configuration / My Store.

    What is this option doing exactly? Is it recomanded to set to false or to true?

    The variable $PHP_SELF may not have the value what I expect (but Iam not shure),
    the Name of the page 'create_account.php' or 'create_account.php/langugage/en' or ' create_account.php/language/en/ceid=7e0482062e51eee6ea41fb0a9d94e1e4 ?


  7. While optimizing my Phoenix Shop with Google Search Console I found the Header Tag Product Schema JSON-LD
    which finally enables Products tab in Google Search Console.

    Once this script is enabled it shows in the header of the product_info.php code additional informations related to the product.

    Example:
    https://www.attias.ch/ishop/product_info.php?products_id=2152&language=en
    shows:
    {"@context":"https:\/\/schema.org","@type":"Product","name":"CH 1882 Ziffermuster weisses Pap. 53b (45) gestempelt Wyl SG","image":"https:\/\/www.attias.ch\/ishop\/images\/CH1882Ziffer53No1.jpg","url":"https:\/\/www.attias.ch\/ishop\/product_info.php?products_id=2152","description":"Switzerland 1882, Ziffermuster, weisses Papier, Kontrollzeichen Form A, 2 Rappen (SBK 53b, Michel 45), 2 Rp. hellolivbraun, sauber gestempelt WYL SG, 08.12.1882, farbfrisch und einwandfrei gez\u00e4hnt...","mpn":"CH1882-53No1","offers":{"@type":"Offer","priceCurrency":"CHF","price":"300.00","availability":"https:\/\/schema.org\/InStock","seller":{"@type":"Organization","name":"Philatelie Attias, CH-5620 Bremgarten AG"}},"manufacturer":{"@type":"Organization","name":"CH"}}

    Google Search Console sent me an E-Mail telling me the following warnings:

    Search Console has identified that your site is affected by 6 Products issues:

    Top Warnings

    Warnings are suggestions for improvement. Some warnings can affect your appearance on Search; some might be reclassified as errors in the future. The following warnings were found on your site:

    Missing field "url"

    Missing field "review"

    Missing field "aggregateRating"

    Missing field "brand"

    Missing field "sku" 

    This will appear for all my products.

    Somebody found a solution for These issues or has any Idea how to get rid of them? 

    There is also an additional header tag called
    Breadcrumb Schema JSON-LD,
    but no description for what it is?


  8. @JcMagpie

    Aha, I do not develop php programs yet… But i have installed a new test Environment and played a little bit with various settings in Phoenix. 

    I found out that turning off the Use Search-Engine Safe URLs (set to false) in admin section / configuration menu / My Store
    solves the Problem above.

    Now the link shows like this and it will be recognized by the hook in JcMgoogleCapatcha.php properly.
    https://www.attias.ch/ishop/contact_us.php?language=de&ceid=b762592bb02c1d2ca8938c328b92e63f

    Maybe also this has an impact to google search which i will control this in the next future.
    Thanks for your answer and for your hook!


  9. @JcMagpie

    Thank you for creating this hook:

    In my installation it works as long as the link is as followed:
    https://www.attias.ch/ishop/contact_us.php

    But when the link comes with the ceid: 
    https://www.attias.ch/ishop/contact_us.php/ceid/098b722e19620edff2b1bcecd03d55ed
    the recaptcha item will not be shown.


    I had to deactivate this hook by renaming the $good_page values in pages which dont exist.

    Maybe the hook JcMgoogleCapatcha.php does not find the page with the ceid in $good_page and needs to be substringed before.

    Any proposal? 

     

     


  10. 7 hours ago, ecartz said:

    To be honest, I don't really know.  I mean it's setting the reading direction to left to right (so I read the "What" first and the "doing" last in your question).  Basically it's saying that the language is not like Hebrew, which is right to left.  And it's saying that the language is Deutsch (German).  It's not specifying a dialect of Deutsch like en-US or en-GB do for English.  It's possible that it would make sense to put in a lang parameter on the English pages.  I'm not sure what it should be. 

    I would be better able to help you if someone told me what effect should be on the pages.  I could try to figure out how to implement that in code. 

    Since you don't have separate English pages for the US and UK, your proposed define is correct.  Whether it is better to set it or not, I don't know. 

    Thank you for your answer ecartz, I implemented the code  <html dir="ltr" lang="en">
    in the english.php and wait what it will create by google search console.

    Somebody other any idea?


  11. On 11/16/2019 at 12:52 PM, ecartz said:

     

    
    define('HTML_PARAMS', ' dir="ltr" lang="de"');

     

    @ecartz

    What exactly is this definition doing?

    I do have this in my german.php file,
    but in the english.php it looks like this:

    define('HTML_PARAMS', '');

    Do i need to change this to ?

    define('HTML_PARAMS', ' dir="ltr" lang="en"');

    I am asking this because i am optimizing my pages with the google search consol, which created tousands of Errors …
    and I am wondering how to define my pages in 2 languages as canonical, but not identical?

    <link rel="canonical" href="https://www.attias.ch/ishop/attias_index.php">


    There is no hint in my pages which languages is shown, except the german ones with:
     

    <html dir="ltr" lang="de"><head>

    code of Website to follow

    </body></html>

    How did manage you this?


  12. @ecartz

    Thank you very much, the first part is exactly what i needed. The second part i will go on later.
    Studying the "ht_pages_seo" which i already activated, I found out that the next step having the <meta  name= "description" content included is also defined there.

    So for conditions.php in english i defined: 

    define('META_SEO_TITLE', 'Our GTCs');
    define('META_SEO_DESCRIPTION', 'General Terms of Conditions (GTCs) of Philatelie Attias, CH-5620 Bremgarten AG');

    as for further languages i did this too.

    And this works fine for title and meta in html code!!! Great!

    So I hope now,  with these points in this topic  to reduce my 4500 error pages by google to 0! -:)


  13. Hi everybody

    I am studying html code produced by Phoenix Version 1.0.3.0 related to SEO Issues.

    I have set up 2 languages set up in Phoenix.
    -en english
    -de german (set as default language)

    The english language html code works fine (see attached picture head_en.jpg).
    All the <meta> tags are properly shown in the <head> section of the html code.

     

    The german lanugage html code is not correct (see attached picture head_de.jpg),
    all <meta> tags are shown in the <body> section of the html code,

    This is in my opinion wrong. The <meta> tags were not properly crowled.
    (template_top.php original version) 

    Somebody any ideas, what went wrong?

     

     

    head_en.jpg

    head_de.jpg


  14. 18 minutes ago, peterpil19 said:

    @Philo2005

    Sure,

    In includes/languages/german/modules/boxes/bm_information.php

    Add angebot under Contact Us, or wherever you wish it to appear in the links e.g.

    
      const MODULE_BOXES_INFORMATION_BOX_DATA = array(
        'privacy.php' => 'Privacy Notice',
        'conditions.php' => 'Conditions of Use',
        'shipping.php' => 'Shipping &amp; Returns',
        'contact_us.php' => 'Contact Us',
        'angebot.php' => 'Unser Angebot'

    Peter

     

     

     

    @peterpil19

    Thank you works fine 🙂


  15. 23 hours ago, ecartz said:

    So you want to go to https://www.attias.ch/angebot.html and have it look like https://www.attias.ch/ishop/conditions.php (with different text of course)?  If you're OK with changing the name to angebot.php, you could just make copies of the conditions page files. 

    • angebot.php from conditions.php
    • includes/languages/german/angebot.php from includes/languages/german/conditions.php

    In the new file, change

    
      require('includes/languages/' . $language . '/conditions.php');
      $breadcrumb->add(NAVBAR_TITLE, tep_href_link('conditions.php'));

    to

    
      require('includes/languages/' . $language . '/angebot.php');
      $breadcrumb->add(NAVBAR_TITLE, tep_href_link('angebot.php'));

    and in the language file, change

    
    define('NAVBAR_TITLE', 'Conditions of Use');
    define('HEADING_TITLE', 'Conditions of Use');
    define('TEXT_INFORMATION', 'Put here your Conditions of Use information.');

    to reflect what you want to show, e.g.

    
    define('NAVBAR_TITLE', 'Unser Angebot');
    define('HEADING_TITLE', 'Unser Angebot');
    define('TEXT_INFORMATION', <<<'EOTEXT'
    <h2>Briefmarken</h2>
    <p>Schweiz ab 1850 Einzelmarken/Sätze ab 40 % SBK</p>
    
    <p>Rayon, Strubel, Sitzende Helvetia, Stehende Helvetia, Ziffermarken, Tellknaben und Brustbild, Freimarken, Werbemarken, Pro Juventute, Pro Patria, Blocks, Zuschlagsausgaben, Automaten-Marken, Rollenmarken, Porto Marken, Zusammenhängende, Zwischenstege, Kehrdrucke, Dienstmarken, Stempel Neuheiten, Schweizer Neuheiten, Schweizer Spezialitäten, Jahreszusammenstellungen, Abarten, Postfrisch , Gestempelt, FDC's, Vollstempel, Ersttag Vollstempel, Frankaturware etc...
      Diverse Länder</p>
    
    <p>UNO Genf, Deutschland (in Bearbeitung).<br />
      Posten und Sammlungen</p>
    
    <p>Kleine Posten und Sammlungen ab 10.-, Kiloware Schweiz und Ausland (Briefmarken zum Ablösen), Länder- und Motivsammlungen je nach Angebot.</p>
    
    <p>Wühlkiste - jeder Brief 1.- Stutz - hier findet jeder einen kleinen Schatz.
      Ansichtskarten</p>
    
    <p>Weit über 15'000 Schweizer Ansichtskarten am Lager (Litho, Lichtdrucke, Foto-AK's).
      Zubehör</p>
    
    <p>Briefmarken-Kataloge (SBK, Zumstein, Michel), Sammler-Zubehör von Leuchtturm (einiges am Lager), Lindner auf Bestellung.  Hüllen für Ansichtskarten und Briefe, Archivierung etc., Briefmarken Alben, Systemalben für Briefmarken, Briefe, FDC, Ansichtskarten, Vordruckalben, Pinzetten, Lupen etc.<br />
      Fehllisten Bearbeitung</p>
    
    <p>Wir bearbeiten gerne Ihre Fehllisten für Briefmarken, falls die gewünschten Marken nicht am Lager vorrätig sind, suchen wir Sie gerne kostenlos in Ihrem Auftrag und offerieren Ihnen diese. Hier können Sie uns mitteilen, was Sie suchen, bzw. was Ihnen fehlt.</p>
    
    
    <p>Briefmarken-Neuheiten können bei uns im Abonnement bezogen werden!</p>
    EOTEXT
    );

    I prefer the nowdoc syntax for multiple line strings.

    There are also contributions like Page Editor , but it doesn't look like that's been updated for Phoenix.  If you have budget, you could pay someone to do that.  Either post in the Commercial Support Inquiries forum or PM @burt to see if he has something like that for Phoenix Supporters (annual fee required). 

    If it's important that the name end in .html, then you could configure Apache's mod_rewrite to do that. 

    Okay i did this for the buy page.

    How can I connect the page attias_ankauf.php to the information boxes?

×