Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by raiwa

  1. @Kurre,

    This module is not intended to be used to show a different logo for mobile and desktop view. It is intended to show the optimized size of the same logo for each device size/resolution.

    If you wish to show different logos for mobile and desktop/tablet, you have to use the bootstrap helper classes. It's a different approach.

  2. 33 minutes ago, Kurre said:


    You could give the modification posted by Stefan a try:

    On 7/5/2018 at 4:22 PM, Stephan Gebbers said:
        echo '<a href="' . tep_href_link('index.php') . '"><picture>
    	      <source srcset="' . $store_logo_big . '" media="(min-width: 1200px)" />
    	      <source srcset="' . $store_logo_medium . '" media="(min-width: 800px)" />
    	      <img src="' . $store_logo_small . '" title="' . STORE_NAME . '" alt="' . STORE_NAME . '" class="img-responsive no-watermark"/></picture></a>';[code]

    Check also your resolutions, if viewed with a retina (high resolution device) it may take the big image even it is a small mobile screen.

  3. 4 hours ago, PiLLaO said:

    Since 2015 with ECMAScript 6, pure javascript it's more easy to use, near to jQuery but you don't need to load and extra file.

    If you use de "order editor" addon, you can view that not use jQuery and have ajax.

    The tendency is to program in pure javascript.

    GitHub removes from his frontend jQuery: https://github.blog/2018-09-06-removing-jquery-from-github-frontend/

    Hello Gustavo @PiLLaO,

    JQuery is core on admin and store side and used in many core files, PayPal App, core header tags, core hooks and other third party apps. So I really do not see any need for the suggested mod to pure javascript.

  4. @Dnj1964,

    Better go for the version which includes a small error fix:

      osCommerce, Open Source E-Commerce Solutions
      Copyright (c) 2019 osCommerce
      Released under the GNU General Public License
      $cl_box_groups[] = array(
        'heading' => BOX_HEADING_CATALOG,
            'apps' => array(
            'code' => null,
            'title' => null,
            'link' => null


  5. 3. PWA login module. I just checked again. Clean unmodified Phoenix installation. Added the PWA files and modified files. Installed the PWA login and header tag module and all works like expected. Maybe you didn't install the header tag module?


    5 minutes ago, discxpress said:

    @raiwa Thanks I will try again. 

    What is the latest version for Phoenix?


    On 11/26/2019 at 7:31 PM, raiwa said:

    Uploaded update for Phoenix:

    Purchase without account 4.0.1

    Changes Version. 4.0.1
    - updated core reference for Phoenix in admin/reviews.php
    - replaced deprecated <u></u> tags with alert-link class in shop language files. Thanks to @Demitry
    - added sql to delete guest account data also from customers_info, customers_basket and customers_basket_attributes tables when the guest account is deleted. Thanks to @vmn
    - disable navbar account menu and header account buttons during guest checkout. Thanks to @vmn
    - updated scripts for checkout success to restyled Phoenix version..

    4 versions included:
    Phoenix and lower: (old review write page "reviews_write_pwa.php")
    Phoenix and higher: (new reviews module "ext/modules/content/reviews/write_pwa.php")
    Phoenix and higher:  (restyled checkout success modules")
    Phoenix and higher:  (updated review stars in admin/reviews.php")


  6. 40 minutes ago, discxpress said:

    Ok. It didn't happen until I installed PWA


    2 hours ago, discxpress said:

    @raiwa i couldn't get PWA to work so I tried to remove it and now I'm getting a database error.

    1. What is correct, you got the error since you installed it or since you removed it?

    2. PWA doesn't add, remove or modify anything in the reviews table. It only uses modifications in admin/reviews.php and in admin/customers.php. There are queries on the reviews table in these files, but unchanged by the PWA modifications.

    In which page you get this error?

    I'm pretty sure you modified something else apart of the PWA installation.

    If you do not find the solution, recover your backup (you made a backup? sure?)

    3. The PWA login module can only not show if you missed to copy the template file or the language file, or you didn't installit/turn it on in admin, or you  copied a wrong version (very outdated PWA version)

    Please consider that PWA is working in hundreds of stores since years. No one has reported any similar problems.