Hi Jack,
It seems to work perfectly. Thanks!
Hi Jack,
It seems to work perfectly. Thanks!
Thanks for the support! My topic “Trouble aligning button in sticky cart on left side” has been successfully resolved.
Hi Jack,
The caching system isn’t the issue here. We see the results on our end, the same as you.
We need it to be the other way around, so like this on desktop https://imgur.com/6sJ98Fz (topwidget, everything closed) and this on mobile https://imgur.com/3xfraAL (sidebar widget, everything open)
Hi Jack,
The z-index issue is entirely our fault, and I appreciate your support in fixing this nonetheless.
Still, of more importance is the closed filters issue, where we seem to be able to open all filters for desktop (topwidget) and separately have them closed on mobile (sidebar widget), but not the other way around (https://imgur.com/OdGziC2). Is there a way of fixing this?
Apologies, the temp login link had expired.
New one in Private.
I’ve applied the change, and cleared cache. Mobile still displays same behaviour. Maybe you could check on your end?
Please see video in private section on the floating filterr icon issue.
With regard to the toggle open/closed widget:
https://imgur.com/OdGziC2
It seems we can have a separate action for the mobile version (sidebar widget being closed upon loading), but not the topbar widget we use on desktop. How can we resolve this so that the topbar widget is closed, and a seperate action for mobile widget (sidebar) to be open upon page load?
It’s been a day, we’ve again cleared all cache (also CDN) but the change isn’t visible.
Can you tell us what changes you’ve made?
I’ve cleared site-, object- and CDN caching, but the indent is still visible on our end as well.
The space between the add-to-cart button and the attributes above has been reduced successfully.
We’ll check it again tomorrow
Thanks for the support! My topic “Manipulate space (padding) between products on shop / category pages” has been successfully resolved.
Worked perfectly. Thanks!
Thanks for the support! My topic “How do I get rid of the top filters (sort by price, popularity, etc, and number of results per page)” has been successfully resolved.
Thanks for the support! My topic “Text layout gets fumbled in all text imput fields (visual is fine, result is not)” has been successfully resolved.
Thanks for the support! My topic “sticky chat button overlapping sticky cart product” has been successfully resolved.
Hi Jack,
We’ve tried to manipulate the positioning ourselves a bit, but this is where we’re at: https://imgur.com/RCeI5lK and https://imgur.com/zZAj7rB
The red arrow indicates what still needs to be done, but overall, we would like to understand which classes are at our disposal to better manipulate the positioning ourselves.
Much appreciated!
Cheers
Thanks for the support! My topic “Unable to locate sales badge or lable for discounted items” has been successfully resolved.
Hi Jack,
Thanks for your prompt response. I had to check for a minute, and it seems that the mentioned CSS code was added to minimise the space between the product variations and the stock info. Removing it, solved our problem. Thanks!
Expecting some push back on our end, can you help us with the right classes to address when we want to minimise that space without fumbling up the paragraph tags?
On that topic, can you tell us why Xstore’s ‘formcart’ is built the way it’s built? Other than selecting a horizontal layout (with its own layout challenges), there doesn’t seem to be an option to design that part of the product page. In its current format, there’s a LOT of white space that we don’t see in many Shopify pages. Having that stretched layout waters down the buying experience.
That’s funny, because paragraphs seem to have vanished throughout the entire website, subsequently compacting all of our texts: https://imgur.com/i7Xzj2s
-EDIT- I noticed that creating a new FTP user also created a new port (in private). Apologies
-EDIT 2- We’ve checked all blog pages, text pages, products… Nowhere is the paragraph layout visible in the front-end. It seems updating the files didn’t go as planned, or perhaps there’s a conflict with the earlier code-fix in functions.php?
Hio Jack,
Apologies, I thought I just needed to clear the CDN. Kinsta allows for these basic tasks in the WordPress backend panel. I will need to take a closer look inside Kinsta’s control panel.
As for FTP, please see credentials in private
-EDIT-
CDN has been disabled
Apologies. Product template has been closed.
I wasn’t able to find the setting in the product template, the product itself, Woocommerce product tags, or anything within xstore…
Hi Jack,
We’ve cleared all cache, disabled CDN, but it seems the problem persists.
1) Created a text in code, using tags: https://imgur.com/1VyLM5e
2) Switched to visual editor: https://imgur.com/l0Z81br
3) Switched back to code editor, to check editor behavior: https://imgur.com/OjUguRy
4) Checked output on website, paaragraphs are gone: https://imgur.com/jGDMNl8
We get that we can use HTML tags. Unfortunately, once we do, we check the text block by switching back to Visual, and then back to Code, only to find that the manually entered HTML tags are removed! To clarify: all visual layouts are also removed (paragraphs)….
Do you recognize similar issues when trying to edit a text, or is it only on our website?
Thanks for the support! My topic “Bug in multiple header editor: unable to retain page assigments” has been successfully resolved.
Thanks for the support! My topic “URGENT: Google index conflict w/xstore filter” has been successfully resolved.
Thanks for the support! My topic “Custom Add to Cart button does’t add product to cart” has been successfully resolved.
Hi Jack,
Thank you for all the thorough feedback. Your support is amazing, as always.
I’ll take this up with the Elementor team.
Thanks again!
Hi Jack,
I think you may have misunderstood:
If you would like to have a similar widget on other templates
The screenshot I shared is of a cross-sell section on the same single product page. The product image is retrieved just fine, but the add-to-cart button doesn’t pick up the corresponding product. You mean to say there’s no way to solve this, other than to request a feature? I would think that, because of the existing hook for the product image,, an ?add-to-cart slug with the relevant product-ID wouldn’t be much of an extra stretch…
Let me know if this clarifies things a bit more. If not, I’ll proceed with the feature request.
Hi Jack,
Thanks for your guidance. The problem appeared to be two-fold:
The element was disabled in the Elements Manager, so we fixed that. Second, the widget only appears in the left side widget panel on a single product page, not on any other page, so while using the pop-up template builder, we couldn’t find the widget.
It’s implemented, and it works, so we’re halfway there.
The second part of the problem is that we’re unable to ‘copy’ the same functionality to an add-to-cart button in the cross-sell section, and I was hoping that the code snippet you suggested might fix that as well?
Hi Jack,
Unfortunately, we’re unable to locate the Sticky Cart widget: https://imgur.com/HNioQZI (looking for “sticky cart” doesn’t yield any result)
Also: the example you gave still redirects to the home page as the slug before the ?add-to-cart is the home page’s address.
The solution we’re trying to create is a sticky-footer with a cart button that pops up to offer the customer to add the product of the current page to the shopping cart. The sticky footer pops up after scrolling 15% down. The sticky footer should also disappear again after scrolling all the way to the top, because of the standard add to cart button coming back into view. After clicking the sticky footer cart button, the customer should stay on the same product page, not get sent to the home page…
Thanks for the support! My topic “Gallery element shows unnecessary white space” has been successfully resolved.
Thank you!
Since this is a custom script to fix what I believe is a structural issue, will there be a permanent fix in the template? If so, is it possible to receive an alert when this is done, so we can delete the work-around script again?