Jump to content

Dirty Butter

Moderator
  • Posts

    6,634
  • Joined

  • Last visited

  • Days Won

    139

Posts posted by Dirty Butter

  1. There's a footer section in cubecart.css. You should be able to copy that section over to cubecart.default.css and make adjustments there. You can see how hover, etc., is dealt with for the product titles and add something similar for the footer text. Cubecart.default.css is not overwritten on upgrades. Other tweaks you make to foundation.css, etc. will be lost on upgrade and you'll have to put your edits back any time Foundation is revised.

    If you plan on extensive cosmetic changes, you might prefer to purchase a skin that provides easy ways to change colors, etc.

    SemperFiWebServices has a new one out with lots of flexibility that can be dealt with from within Admin, rather than via file changes.

    https://www.cubecart.com/extensions/skins/custom-foundation-5-skin

    And there are several other commercial skins that might provide the look you want. Havenswift Hosting has some you might like. If you go that route, be sure it is a Foundation based skin, not an old v5 skin. The v5 skins work with v6, but some functionality of v6 will not be there out of the box.

  2. I see that Bsmither helped you in the past with a problem, but didn't see anyone else discussing Plesk installs. Bsmither is not on regularly right now, so it may be a while before anyone knowledgeable can offer suggestions.

  3. Sorry, I should have reminded you to clear all CC cache in Maintenance, except images. Also clear your browser cache (Ctrl/F5).

    I just tried the edit, and it worked partially. It turned to blue the empty part of the nav bar to the right of the text, but not where the text is. So there's another code somewhere that needs changing, too.

    There's a top-bar-section a little further down in the foundation.css code. Maybe that's it.

  4. Welcome to the forums, @keepcalminsane !  Look in your skin/css/foundation.css file about line 1725. It's best to make a pristine copy (with it's own name) of all your skin files before you start fiddling with edits. Then you can always back out of any customizing you do that you aren't satisfied with.

    .top-bar {
      background: #333333;

    I found that code section by using the Firebug extension in FireFox. When you right click on a section you want to modify you will see "Inspect element with firebug". Choosing that brings up a window at the bottom of the page. On the right you will see the code locations, and you can edit it there to see if it does what you want.

    Chrome and other browsers have something similar.

    Right clicking on the product title indicates the coding for the title is inherited from H3 in foundation.css. So you'll have to search within foundation.css for where the sizing of H3 is coded.

  5. The upgrade bug has been fixed in 6.1.7, but that is not going to help you right now. And it's easily dealt with to upgrade to 6.1.7 if you had server access. I understand that you came on board to run the site, not to be involved with the code or hosting. But somebody did have access in some way back when the site was first created. If you can provide that way to access your file structure you can pay to have someone else manually upgrade this one time for you. That's why I asked if you could contact your host about getting that access.

  6. I've been very pleased with Havenswift Hosting for the last couple of years. Before that I was on HostGator, but I had a problem that was CC related and they simply made no effort to find the cause of the problem. Someone else here on the forum just recently was looking for a new host, because HostGator could not/would not help them.

    I do have an affiliate link to Havenswift, but I stopped displaying it when I became a moderator.

    https://www.havenswift-hosting.co.uk/clients/aff.php?aff=41

  7. It might be a good idea to private message Bsmither, so he'll see your post when he pops in. He's in the middle of moving his household and not on here much right now. If anyone can suggest a snippet or other coding solution, he would be able to.

  8. OK - that's the problem. But what version were you on already?

    As for the admin mess - you are certainly not the only one who has dealt with it.

    Take a look in includes/global.in.php and see what naming is there for admin.php and the admin folder. THAT is the good file/folder.

    Assuming it's admin_XXX.php that is good - try to login to your admin area using the XXX naming.

    Must be secure version if you have SSL enabled - https://storeurl/admin_XXX.php

    Whatever the obfuscated admin naming is - DO NOT share your naming here - just XXX it out if you share code or screenshots.

  9. Maybe you dipped your toe farther in the water than you thought you did. It DOES sound like it tried to do an automatic upgrade (thank goodness that is supposed to work from now on once you can get 6.1.7 installed correctly).

    Please take a look at your file structure via FTP or your host's FileManager. Look at the folders/files at your store root level. That's the level that has the includes folder in it.

    Do you have admin.php AND another file that looks like admin_XXX.php where the XXX's are random characters?

    Also, as well as needing to know what your current version is, as Bsandall asked, - are you on SSL?

  10. 21 minutes ago, SergeiG said:

    Actually, the name 'hide-for-small-up' sounds strange, according to logic it should be 'hide-for-medium-up' or 'show-for-small-up'.

    Well the idea I guessed was to keep it from showing at all if pagination was wanted. I'm sorry, but I have suggested everything I know how. Since we know there is a bug report concerning pagination, and I've added your issue to it - best to follow @bsandall's advice and use More for now.

×
×
  • Create New...