x97wehner

I use the generator pretty regularly and haven't had any issue. Running bleeding edge release currently.

Mine ended up being a combo of the issue that was resolved with the recent bleeding edge update, as well as the server, and then caching. Had to test it on a new PC with a new browser and new internet connection to verify it was all working after the update. It is, just had to get it all cleared.

I see the same behavior in the Warehouse theme

I don't. The error only shows on the shipstation side.

With PHP 7.3 and TB 1.1, Shipstation is not able to work correctly when transmitting tracking numbers. Seems to work fine with PHP 7.2. Shipstation is a webservice connection. Seems to be the only issue I've had with 7.3. Any how to resolve?

The page builder is nice. As a limited skillset dev, I look at it and think "That's a great foundational piece to offer nice base flexibility. I'll just modify the rest with some minimal code." As a full-time software consultant I think "It's not out of the box and ready to go enough for standard non-technical business owners to use." Not sure which group you're going after here as a primary focus; website developers or small/mid size business owners?

I believe he's projecting the page <yourdomain>/reviews into the custom Html block. And it doesn't require the recent reviews module.

Can we get the stripe module updated to map the country over to the stripe payment form in their checkout? I believe I have it setup correctly and it doesn't do that.

I just found the tpl files under root/pdf.

Actually no. The order_return_state is not the correct email that goes out when a return is approved. That's the issue. I can't find the email in in the available templates to translate. I think it should be called return slip or something similar.

Thanks, but was referring to @datakick's question as to which way is best for a TB dev to resolve it.

bump

I don't have a good answer for how it should be. But I know that I've had multiple customers not be able to submit the contact-us form over the past couple days because of this error, so it certainly needs a timely resolution. Thanks.

No other warehouse users having the same issue or anyone that might know how to fix?

I have not.

Note: I rolled back to stable 1.1 and the issue is gone. Tested in a vanilla OOB and my live site. Seems to be something in one of the subsequent patches in the bleeding edge versioning that is causing the issue.

in debug mode I get this error: "Property CustomerMessage->user_agent length (129) must be between 0 and 128 in file classes/ObjectModel.php at line 1058" - Not sure how to fix. Please help

Getting a 500 error when customer tries to submit the contact-us page. Console shows these two errors: Unable to get property 'SavePersonalAndPaymentData' of undefined or null reference Autoformfill_ContentScript.js (1,20660) HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request. POST - <domain>/contact-us Can someone advise how to possibly resolve this? Not had this come up prior.

@datakick Think I found a bug. When new customer creates an order, they do not select the opt in or newsletter boxes. After order is processed, in back office, both opt-in and newsletter boxes are checked. Tested while creating account and using guest checkout.

I can't find the order return email in the available email list to do a translation. Can someone provide guidance on where it's located so I can do this? Thanks

@datakick In the cart summary tile, if you can add an option to hide the "Total (Tax excl.)" line, it would be appreciated. Not really needed in the US and just adds clutter. If you can at least give it a dedicated class, I can hide it with CSS. Thanks.

I noticed the mobile/small screen display had some issues with longer text. Here is a little bit of CSS you may want to use if you're experiencing the same issues. (Please don't judge my coding ability, it works. ;-)) @media screen and (max-width: 445px) { .chex-option .chex-check { flex-direction: unset; } .chex-shipping-option .chex-check { float: right; width: inherit; } .chex-shipping-option.chex-option { display: flow-root; } .chex-shipping-option .chex-option-logo { margin-bottom: 3px; } .chex-option-delay { float: left; } .chex-option-price { float: right; } #basic .chex-section-collapsed-content , #shipping .chex-section-collapsed-content{ padding: 15px 20px; } #layer_cart .button-container .btn { width: -webkit-fill-available; text-align: center;} } @media screen and (max-width: 350px) { .chex-cart-item-quantity-price { display: block; } }

Looks to be working. Thanks! Look forward to the other updates around carrier arrangement and field arrangement.

You're on the right track. In all honesty, as far as design goes, Panda and Warehouse have the vast majority of needs covered. Some of their stuff is getting out of date as far as demos go, but as you said, but if it can be easily adjusted with CSS or some basic HTML, it's not too big of an issue. When it comes to design needs, I typically look to large online leaders in the same industry to determine an approach. As long as I can easily recreate a site that looks and functions similar to global product design leaders like Patagonia, Apple, Herman Miller, Nike, or a few others, then my needs are met. If you see their sites, you'll quickly notice some holes in availability from the above mentioned themes that you could easily close and make your theme very valuable.

thank you for the quick followup @datakick Regarding the address format, the new account forms all render according to printable format, I'm fairly certain. If printable format is adjusted, then the order of fields is adjusted on the form as seen below. This is what I was referencing for same functionality. Honestly, that is a minor issue. More UX that probably wouldnt' keep them from buying. The fact that tax is being displayed added to the product in the cart is much larger as it's not standard in the U.S. and it's keeping me from using this module despite purchasing already. Wish I had checked in more detail ahead.