Forum Replies Created
-
Posts
-
Works perfectly. To reiterate for others who may get this problem, below is the code that cured the too-narrow box problem on the checkout page on my system. The css plugin they recommend makes it so easy; I highly recommend it. Much appreciated.
input.eStore_cart_item_qty{
max-width: 80px !important;
}
Update 9pm est USA
I put this code in (your helpful custom css plugin) from an old forum post which indeed works on the ‘store’ page quantity box (duplicate links above) but does ‘not’ change the quantity box size on the Cart page, which currently shows only one digit (although you can select the box and see the other digits in the box). What I mean by cart page is: the checkout page where the items selected from the online store page are listed and the customer pays.
input.eStore_cart_item_qty{
width: 60px !important;
}
Without a way to attach a screen shot to my post here, someone ‘must’ put a large quantity in from the store in order to see the problem on the cart (review your order) page. You’ll see it immediately.
Thank you!
Hello, could someone look at this again please? There is no change on the online cart page; the boxes are too small, cutting off anything over one digit.
Worse, on the online store page, the paypal button was shrunken tiny and unreadable (perhaps from this part here:)
.eStore-button-form input {
width: 50px !important;
}
At any rate, changing the px below does not help. I even tried 150px yesterday, and no improvement.
.eStore_cart_item_qty {
max-width: 80px !important;
}
I have just now removed the extra css coding to get the paypal buttons back correctly sized. Client and myself have both cleared cache (as always) and checked other browsers.
Note pls: One digit shows fine; 2 and 3 digits are cut off. Of course, but you must put 10-100 items in on the store page in order to see the problem on the cart checkout page.
Thank you very much for the prompt response. I’m reporting back that it’s forehead slapping time: I did have everything set correctly in estore plugin per the documentation, and the client did have PP regional tax set correctly per your video documentation which I had already sent him 2 days ago (but he already had set up years ago). All good so far, right?
The problem, in case it helps anyone else, is that – since I am not in his state – for testing the regional tax in his state, he was somewhat finagling a sale through PP from his own account to his own account. So PP knew something was hinky and checkout wasn’t working correctly (while estore shipping did apply beautifully and accurately first time and every time).
In conclusion: Today he made a purchase from another account (not his own) in his state and – voila! – it added the regional tax perfectly. I guess what I learned was to do ‘more and different’ testing next time before assuming I, or the plugin or merchant, is the causation.
I appreciate your help (and have updated my profile to receive email notices of responses so I can see them asap going forward).
Best regards from Catherine.
