Jump to content

Frank Auffret

Member
  • Posts

    83
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Frank Auffret

  1. One of my customers received an email from Opayo formerly Sagepay - see below

    Will there be a need to upgrade the Sagepay extension or is there a plan for an Opayo extension?

    Email snip
     

    Happy New year. Here at Opayo we are upbeat about the year ahead with some exciting product & feature releases all designed to enhance you and your customer's payment experiences, but we start the year with helping you get ready for PSD2, (Payment Services Directive), being implemented on the 14th March 2022 - Urgent action is required NOW.   

    Thanks to PSD2 there are a set of game changing security measures to make it safer to shop and bank online benefitting both the shopper and business. At the heart of it is Strong Customer Authentication (SCA). 

    The UK SCA deadline is 14th March 2022 however from January 'til March there will be a ramp up in card issuers challenging transactions for SCA, resulting in non-compliant transactions being soft/hard declined if the SCA data is not provided. 

    From 18th January 10% of transactions will be SCA challenged by issuers, this % will increase throughout March with 100% of transactions being SCA challenged by the deadline date (14th March 2022)
     

    If you have not completed the relevant updates for SCA, you must take action now to avoid disruption to your business. Our Team have pulled together a step-by-step guide which helps you or your developer make the correct updates to avoid any disruptions to transaction processing.

      


    Some key actions to consider
     

    • Upgrade to Protocol 4.00 or our latest API if you're using PI. We always recommend you use our latest documentation and this is even more important with the implementation of SCA.
       
    • Additional Credential On File (CoF) information is required for Token/Repeat payments. If you use Token or Repeats please ensure you are sending this additional CoF information for these transactions.
       
    • Standalone Token registration update. Successful 3D Secure V2 (3DSv2) authentication and CoF information is required to be registered for all Tokenised payments to be compliant with SCA requirements.
       
    • Update your Custom Template If you are using a custom template you will need to ensure the template includes the latest files for 3DSv2 compatibility.
       
    • Activate 3D Secure in MSP. Make sure you turn on 3DSecure in your My Sage Pay portal and activate checks.


    We're here to help

    For further information and resources see our SCA resource hub and developer hub, alternatively you can contact your account manager or our support team on 0191 313 0299 and email [email protected]

  2. 22 hours ago, bsmither said:

    Please show us the HTML surrounding where you are adding this image.

    In constructing the URL for the image, you have the choice of:

    {$ROOT_PATH} = /   (followed by skins/skin-2021/images/slides/top-banner-1.jpg)
    <img src="{$ROOT_PATH}skins/skin-2021/images/slides/top-banner-1.jpg">
    
    Alternate:
    <img src="{$ROOT_PATH}skins/{$SKIN_FOLDER}/images/slides/top-banner-1.jpg">
    
    Or,
    
    {$STORE_URL} = http://dev.SITE.co.uk  (followed by /skins/skin-2021/images/slides/top-banner-1.jpg)
    
    Do NOT use {$VAL_SELF}

     

    Thanks here's HTML

               <div class="row hide" id="small-search">
                   <div class="small-12 columns">
                      {include file='templates/box.search.php'}
                   </div>
                </div>            
                <!-- custom header-->
                <div class="row">
                 <!--Banner-->
                    <div class="medium-12 large-12 small-12 columns">
                      <img src="skins/skin-2021/images/slides/top-banner-1.jpg" title="Wesley Marine Windows" />
                    </div>                
                </div>        
            <!-- ends custom header-->
                <div class="row small-collapse">
                   <div class="small-12 columns">
                      {include file='templates/box.navigation.php'}

     

    Yes thanks it can also be fixed with

    {$ROOT_PATH} = /   (followed by skins/skin-2021/images/slides/top-banner-1.jpg)

    but that feels like a sticking plaster over a problem with the inventory table

  3. 1 minute ago, Noodleman said:

    there was a bug in an earlier foundation theme for this issue. if you're using a modified version of Foundation it probably didn't get the fix. 

    thinking of this, might be related:

    https://github.com/cubecart/v6/issues/2184

    Thank you for your quick response. The actual product images work fine it's just the top banner image in the template that fails on just some product pages. I used the Foundation skin from the latest version of Cubecart so should be bug free

  4. There's seems to be an odd database issue on one of my development stores (and when tested on live site). I created a new skin based on Foundation and placed a banner image in the header of /templates/main.php. 

    All works except for several (not all) product pages where the banner image fails as the relative path to the top banner image is changed e.g.
    Working product page: http://dev.SITE.co.uk/skins/skin-2021/images/slides/top-banner-1.jpg
    Corrupt product page: http://dev.SITE.co.uk/shower-doors/trays/walls/mixers/skins/skin-2021/images/slides/top-banner-1.jpg

    I cannot see anything in the inventory table that would cause the image path to be changed. Looking in the table in phpMyAdmin the record looks okay no corrupt characters in any cell. Even deleting the data in phpMyAdmin and then re-entering it causes the same error.

    If I delete the product record in CC Admin and re-add it in a new record with the same data the page works and the header image is displayed.

    This is quite an old site but has been regularly upgraded (manually) to the latest CC version.

    Any ideas?

  5. Not really a bug but something to be aware of if using 'Enable SSL'. A customer recently complained that his home page (only) was showing a 'Not Fully Secure' warning on the Security tab.  All other pages were secure.  I noticed he had added a smiley from CKeditor to the Home Page content. The address of the smiley image started 'http' ie 
    http://DOMAIN.co.uk/includes/ckeditor/plugins/smiley/images/regular_smile.png

    Manually changing to the 'https' protocol in the source view solved the issue.

    Hope this helps somebody.

  6. I've deleted the system files and re-upped them, cleared all the caches. I been trying to find out how the store closed is over ridden by the admin session but so far drawn a blank.

    I thought I had some legacy support credits but it look like they have been wiped. So am stuck as the site is in development and the admins cannot see the store without making it live.

  7. I just upgraded my sites to ver 6.1.8 mainly to fix the product titles with double quotes bug e.g. 6" length
    which was breaking the product image title code in the listing so no image was displayed.

    <img src="image.jpg" title=" product="" title"="" >

    The upgrade fixes the bug but causes another issue i.e. any product title previously added with double quotes breaks in the product admin page. 
    e.g. 12" widget  
    displays as 12 
    Doesn't affect the store front listing

    As I have hundreds of products across various sites like this I was wondering if anyone can think of a quick way to fix this issue otherwise I will have to manually re-enter every similar product.

    Apostrophe character escaped in product names, emails bug

     
     
  8. Just tried to install the 6.1.7 but the same installation problem remains - I thought this upgrade was supposed to cure it!

    Install just hangs at 80% complete
    "Upgrade in progress. Upgrading from version 6.0.12 to version 6.1.0"

    Has anyone found the answer to this issue yet?

     

  9. I did a manual upgrade and copied all the new files but the setup still sticks at 80% even if I click the continue button. Seems to get stuck upgrading from 6.0.12 to 6.1.0

    Edited to add just checked the history table seems I upgraded to 6.1.0 last October so can't understand why CC is trying to upgrade from 6.0.12 to 6.1.0 if it's already 6.1.0
     

    CubeCart Version Date
    6.1.0 Wednesday, 26 October 2016
    6.1.0 Wednesday, 26 October 2016
    6.0.12 Monday, 17 October 2016
    6.0.12 Wednesday, 26 October 2016

    I tried Force Upgrade which says upgraded to latest version now


    Upgrade in progress. Upgrading from version 6.0.12 to version 6.1.0

     

  10. 1 minute ago, Al Brookbanks said:

    The auto upgrade may skip renaming the admin.php and admin folder. 
    You can rename the admin folder and admin.php file (keeping .php on the end) manually then edit the includes/global.inc.php file to reflect the changes. 

    Do you still have the smarty error? If so please try deleting all files in the /cache folder. 

    I only got that error when I used the auto update.
    When I used force update I received no errors but am wondering if the upgrade only updated some files.
    Should I try a manual upgrade?

     

    1 minute ago, Al Brookbanks said:

    The auto upgrade may skip renaming the admin.php and admin folder. 
    You can rename the admin folder and admin.php file (keeping .php on the end) manually then edit the includes/global.inc.php file to reflect the changes. 

    Do you still have the smarty error? If so please try deleting all files in the /cache folder. 

    I only got that error when I used the auto update.
    When I used force update I received no errors but am wondering if the upgrade only updated some files.
    Should I try a manual upgrade?

     

  11. HI

    I'm currently developing a new Cubecart site, started last week by installing CC version 6.0.12 

    Tried to upgrade to latest version 6.1.0 using admin upgrade and got this
    [Exception] /var/www/XXXXX/XXXX/XXXXX/web/includes/lib/smarty/sysplugins/smarty_internal_undefined.php:47 - Smarty_Internal_Template->_decodeProperties() undefined method

    and the home page using foundation skin now has massive system images.

    EDITED TO ADD
    1/  fixed large images by clearing browser cache.
    2/ used force upgrade and the system says it's version 6.1.0 but the admin is still /admin.php
     

    Any ideas what to do next?

    screen-grab.jpg

×
×
  • Create New...