Hi Barry.

1 - as you can see, the AC devs addressed the mobile Stripe collapsed credit card entry box problem that you identified.  I sympathize with your latest sentiment.  I'm not 100% sure how something like this gets disseminated to existing AC Stripe users; guess I never thought about it until now.   

2 - I don't use firefox much.  Today, it auto-updated when I turned it on.  I'm now on latest version 57.0.  I confirm that on first visit to your homepage, your cart buttons on each product show the wrong icon and do not work.  I confirm that navigating anywhere on your site then returning to homepage, the cart buttons then work as expected.  I cannot say for sure whether this was occurring 2 days ago when i was on vs 56.  Sorry, I wrote my previous reply in a hurry and did not notice.

I can't offer much more help.  If I were you, I'd start with the housecleaning, then ask your host if they think SSL issues are related to odd FF performance, then ask AC devs.  Good luck.

I looked at your site in Firefox 56.0.2, didn't notice any obvious problems. 

I can't solve your new problem, but i can give you some suggestions for working in that direction.

1 - Housecleaning.  Your entire site is located within one folder on the live server.  FTP that folder down to a backup folder on your PC.  It may take a long time, like hours, because the folder will contain numerous small files, which slows the data rate.  Keep this backup folder intact and safe and unedited. 

Then figure out which "copy or version" of your site on the live server is actually the one driving your website.  Delete the other copies or versions from the live server.  You need to get to a point where the only files and folders on the live server are the ones that are running your site.  Get your host to help you.  If I understand you correctly, there may presently be multiple versions.  That won't help with SSL issues. 

If you break something, restore things from the backup folder on your PC until the site runs.  Keep notes as you clean up.

2 - Read the AC documentation on Developer Tools and cloning the default template.  I doubt that your host-created website clone is the same concept as an AC template clone used for customizations.  If you use AC Developer Tools to create an AC Template clone, you will see the clone in it's own folder within the root/extensions folder, and that folder will have a name that you chose (templatename), and it will contain a cluster of site folders within a /storefront/view/templatename/ hierarchy.  If you can't find this in your site files, then you don't have a template clone.  This is not relevant to your SSL problem, rather just an FYI.  If you study enough to understand my comment, you will begin to understand how AC works. 

3 - Structure.  You need to learn how the site runs from the server.  AC is an application.  There are a small handful of files on your server that tell the AC application how to start up and run.  After that, it just runs.  Study your htaccess file, see what is in it.  In particular, you need to understand the RewriteEngine family of commands that include RewriteCond, RewriteBase, RewriteRule, etc.  There will be several of these rules in htaccess, and the settings specified by these rules basically contribute to either smooth sailing or endless headaches. 

4 - Here is a cut-n-paste from my notes for initial live site setup:
c.   Rename the htaccess.txt file to .htaccess.i.   
ii.   The dot in front of “.htaccess” indicates that this file is ‘invisible’. Therefore you may have to configure your FTP application or hosting file manager to show invisible files in order to edit.  This .htaccess file on an Apache based web server allows you to configure settings for how you’d like your website, or certain files within your website, to behave.
d.   Edit the .htaccess file: if your store is not on the root, you have to configure the RewriteBase/ element to point at the subfolder that contains your store: change it to RewriteBase/subfoldername/  .  The ending slash is important. 
e.   AC Admin control panel - System>Settings>System:   
i.   Scroll to bottom, enable System Check for Admin and Storefront.  Then check the messages that will come up on Admin as you use it.  Resolve the messages.  Delete each after you resolve it. 
ii.   Turn on Retina.
iii.   Turn on SEO URL's
iv.   Note: these all require the mod-rewrite Apache module to be active and .htaccess.txt to be renamed to .htaccess and the RewriteBase/ to be properly configured.

If you read up on the terminology in the snippet 4 above, you should begin to understand what htaccess is doing, which is a step towards getting it set properly. 

My htaccess file includes the following rules that steer all traffic to https :
RewriteCond %{SERVER_PORT} 80
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule ^(.*)$ https://www.yoursitenamegoeshere.com/$1 [R=301,L]

If you aren't set up properly in this fashion, that will be the first place that SSL problems start. 

If you get htaccess "right", then your host is going to be the one to help you resolve remianing ssl probs.

Good luck.  I was almost as much a noob as you when i started.  It took me months to sort this stuff out.  There are no shortcuts or quick fixes, other than cash.  If you want a super quick and dead-right fix, contact the AC devs and ask to them to do a contract job to clean this up.  I would imagine they could fix everything for less than the cost of a weekend's entertainment. 

Hi, I just checked, you have not successfully edited the style.css file that is running your page because I don't see the new rule when i refresh the page and then inspect it. 

If you are using a template clone to customize your site, you need to find style.css located in the root/extensions/templatename/storefront/view/templatename/stylesheet/ folder.  Edit that file to add the complete snippet above, (take care to include all parentheses), then save the file back to the same location on your live server, then clear browser cache.  It will work. 

If you are customizing the default AC template, the file you need to edit will be in root/storefront/view/default/ folder.  Use the same procedure. 

Once you succeed in editing and saving the proper css file, the Stripe box will be limited to a minimum 280px width, which will solve your problem.

FYI - if you are customizing a template clone, you are "doing everything right". 

If you are customizing the default template, then it is probable that your work will be lost during future software updates.  This is okay, don't panic.  Just make a note to never update AbanteCart.  If AbanteCart never develops a security problem with the version you are using, then an update will never be essential. 

You can learn about these concepts in the AC doc stack.  Once you become familiar with Developer Tools and Cloning a template, you can actually migrate your current site customizations to a new clone rather easily, and then be fully ready for future updates without losing your work.  Etc etc.  Have fun coming up the curve!  It won't happen in 1 weekend, so don't stress. 

No one?  Crickets? 

Here's another perspective:

Kids and 20's don't use facebook or twitter.  They use Instagram.  Only old people use facebook or twitter, and the only reason these two companies stayed relevant was new users who "discovered" or "finally joined", then wasted the required year of their life on the app, then dropped out.  Well, the supply of new users is drying up.  Facebook and twitter stats are dwindling.

No one ever used linked-in to sell anything except a job.

Instagram and Pinterest are 'it' for the foreseeable future.   

AbanteCart doesn't include the two pre-eminent social media platforms in the default social media setup.  Ouch. 

AbanteCart uses a powerful easyzoom image viewer that allows PC users to view closeup product images via hover.  Yay!

Pinterest uses a powerful script to add "Pin It" or "Save" buttons to website images.  Cool!

The scripts don't work together.  Ouch. 

The way Pinterest works: Web User A can visit your site and click the Pinterest Save button that you installed on your images, which adds your image to their own fluid Pinterest bulletin board.  People do this as a sort of online status currency of "look what I found!", or as a reminder of "something I want", or as part of a Xmax List gigt board where they assemble 100 gift ideas and then choose from them. 

Other pinterest users can and will see Web User A's "Pin" of your image while cruising around in pinterest looking for items in that general category.  Many of them will re-pin it if your item is catchy.  The pin always links back to your site. 

Or Web User B, who is famous, can pin an image from your site, and everyone who follows User B will visit your site because User B said it's cool.  Web User B can be famous because they are a movie star, or famous as being a finder of cool stuff on the web, etc. 

These two features described above are the "free" and original features that made Pinterest the most important social media platform for ecommerce today.  Because people actually do that stuff, and it works, and Pinterest is now huge. 

You can also buy exposure on Pinterest, and there are a few other planks in it's marketing platform, but you get the idea. 

In Abantecart, if you implement the Pinterest "Save" script in footer.tpl, it works! 
It is so easy!  Just copy a single line of code as the last line of footer.tpl. 
Then all your mobile customers will see the Pinterest button when they tap your images. 
And all your desktop customers will see your pinterest button when they hover over your images on your Category or Product List pages. 
BUT, when they get to a Product page with the easyzoom window, they will see that your site is broken because easyzoom doesn't work with the Pinterest script.

This is not a huge surprise.  Easyzoom is a script.  The Pinterest button is a script. There are bound to be conflicts when 2 scripts are trying to run on the same element. 

The purpose of my post is to point out that Abantecart does not work with the most important social media platform of the day. 

That's a big sentence.  It's powerful.  Searchable.

Maybe someone with coding skills could evaluate the Pinterest script for potential inclusion into or coexistence with the easyzoom script. 

Maybe an AC developer could evaluate AbanteCart compatibility with Pinterest, and then publish a formal position paper on the subject so that the Pinterest capabilities and techniques are know up front.  If the solution is to disable easyzoom, then publish that fact so that AC users know how to proceed.  Instead of sitting around here listening to crickets. 

If the scripts can be combined or made compatible, then the AC platform would gain the distinction of being an e-commerce app that is able to operate with Pinterest [insert superman emoji here],

as opposed to its current status of "Yah, our software doesn't work with Pinterest. [doo doo face emoji here].

Thanks!

Does anyone know how to successfully integrate the Pinterest Save widget with the easyzoom script on the Product page image viewer?

Pinterest has a widget builder that will produce a script for various types of Pinterest buttons on your site. 

The simplest Pinterest button is the Image-Hover Save button.  You paste a single line of code at the bottom of the footer.tpl file:
<script async defer data-pin-hover="true" data-pin-tall="true" data-pin-round="true" src="//assets.pinterest.com/js/pinit.js"></script>

This script will produce a Pinterest Save It button in the upper left corner of any image that a visitor hovers over.  On mobile, the Save button shows up when customer taps or long-taps an image.

It works quite well on Category and Product List pages, but not on the Product page. 

The problem occurs with the easyzoom function for product images on desktop. 
On hover, the Pinterest Save button will show for an instant, and then disappear as the easyzoom action starts to work. 
The Pinterest button will sometimes then reappear in random places near the image in the viewer, but you can't click it. 
This isn't a problem on mobile devices because easyzoom is disabled on mobile.

Is there a way to integrate the Pinterest Image-Hover Save button with the easyzoom feature so that the Save button remains in the upper left corner of the image viewer, and can be clicked? 

I tried adding the script to the bottom of the Category page only, to see if it could be used only on that page, but it doesn't work.

I tried similar things with the Any-Image style of Pinterest button, but again no success. 

There has to be a good way to use Pinterest Save buttons on AC, but I can't figure it out. 

Thanks!

Glad it helped. 

Good job spotting the other rule that needed to be changed. 
On the unmodified AC stylesheet as of today, that's line 3788. 

I had made the same change in my own stylesheet, forgot to mention it.  Glad you caught it. 

Hi, all of the changes I described above should be made to the style.css file.  Do not make any changes to the bootstrap.css file. 

I should have made my language more clear:  "around line 2600" is the "bootstrap overwrites" section of style.css.

After you save all these changes to style.css, clear your browser cache and see if it works.