Jump to content

Dirty Butter

Moderator
  • Posts

    6,634
  • Joined

  • Last visited

  • Days Won

    139

Posts posted by Dirty Butter

  1. No problem! I tried to create one myself and couldn't get it to work.

    But I worked it out from another way:

    Add this to main where the svg lines are in Foundation:

    				<a href="#" class="back-to-top"><span><img src="{$STORE_URL}/images/icons/folder.png"> {$LANG.common.top}</span></a>

    Just as a test I used the folder.png image. But you should be able to find an Up arrow png image somewhere onnline that you could add to the images/icons/. I'll look for one, too.

    This one is free to download and comes in lots of sizes:

    https://www.iconfinder.com/icons/296828/arrow_up_icon#size=20

    The other issue for you is that you wouldn't have the back-to-top class.

    Add this to your skin css/cubecart.css file:

    a.back-to-top, a.back-to-top:hover, a.back-to-top:active, a.back-to-top:visited  {
        color: #000 !important;
    }

    Hopefully that's all the edits you need!

    Just remember, these edits will not survive an update of your Galaxy skin file and would need to be added back in. It's always best to make comments before and after any such edits you make, so you can see what to merge with a newer version.

  2. If the code never existed in Galaxy, rather than accidentally being deleted - you will probably need to add something to css or images somewhere. Does Galaxy use svg or fontawesome for icons? I suspect it's not svg.

    I'm not sure if you can add the svg file from Foundation 6.1.8 to get this back-to-top to work, or if you will need to change svg references to some comparable fontawesome references.

    I'm trying to find which CC version started using svg. Looks like the change was made in 6.1.0.

  3. This is the section in main.php of stock Foundation:

                  

                   <div class="large-3 columns show-for-large-up" id="sidebar_left">
                      {include file='templates/box.featured.php'}
                      {include file='templates/box.popular.php'}
                      {include file='templates/box.sale_items.php'}
                   </div>
                   <a href="#" class="back-to-top"><span class="show-for-small-only"><svg class="icon"><use xlink:href="#icon-angle-up"></use></svg></span><span class="show-for-medium-up"><svg class="icon"><use xlink:href="#icon-angle-up"></use></svg> {$LANG.common.top}</span></a>
                </div>
                <footer>

     

  4. 52 minutes ago, keat said:

    are you sure              '$pricing_group.product_id ='              is the correct string to use ??

    No - it's not. I've tried several different strings, but couldn't figure out what would work.

    Bsmither does something like add {debug} to the bottom of the file he needs to see what is available. You get a popup. Keep the popup, but delete the {debug} from the file.

    I tried looking at the popup, but I just don't understand it all well enough to be able to spot what is needed.

  5. This looks like it worked:

    This did NOT work, but I think it would if the expression was correct.

    content.account.php

    <h2>{$LANG.account.your_account}</h2>
    {if $pricing_group.product_id = '1' }
    <h3>Please change your login email address and password</h3>
    {/if}

    where customer is added to Group with id=1 (I found the correct id number from phpMyAdmin.

  6. You had upgrade issues getting to 6.1.7, so chances are the problem was leftover from your previlous situation.

    Take a look at the sql queries in setup/db/upgrade/ and make sure all those database changes are in your database. If you run a query from the upgrade folder that has already been run you may end up with some duplicated indexes. They will show up in your Maintenance>Database tab and can be fixed via phpMyAdmin.

  7. @difonzo Is the front end of your store functional?

    Do you have access to your database and directories with cPanel or something similar?

    If so, please look in includes/global.inc.php and see what the admin_XXX.php file and the admin_XXX folder are named. Do NOT share the actual XXX part on the forum.

    Try to login to your store url/admin_XXX.php

    Have you created the error_log?

  8. Also, just a suggestion, since you are using Options:

    Instead of using Add to Basket on the Homepage and Category pages, it stops the customer from seeing the Choose an Option warning if you edit the button as a Details/More Info type button. Just change the url of the re-worded button to the product listing instead of the basket.

    This is what I use in content.homepage.php:

    <a href="{$product.url}" title="{$product.name}" class="button small postfix">{$LANG.common.info}</a>

     

  9. 56 minutes ago, havenswift-hosting said:

     It would be great if the developers release could be available via the admin auto upgrade so the actual upgrade functionality can also be tested.

    Without this part it doesn't seem like the developer release would have caught the admin upgrade issues from a few versions ago.

×
×
  • Create New...