Forum Replies Created

Viewing 15 replies - 1 through 15 (of 285 total)
  • Hi there,

    It seems like the issue is caused by the “PT sans” font which is used in the site theme. It has an invalid symbol for the Indian Rupee. More details: https://github.com/google/fonts/issues/2406

    Does the theme allow you to change font from the WP admin? If not, I’d recommend switching to another font via css.

    • This reply was modified 4 years, 3 months ago by makfruit.

    Thank you for the review! Glad you liked Ecwid.

    Yes, it is. Ecwid supports Stripe as well as many other payment options.

    Here you can find more details:
    https://support.ecwid.com/hc/en-us/articles/360000613249-Online-payment-gateways-in-Ecwid
    https://support.ecwid.com/hc/en-us/articles/360013319500-Stripe

    Hi John,

    We just released a plugin update — the parameter you found should not be sent anymore.

    Thank you for bringing this to our attention.

    Got it, thank you for confirmation! We’ll work on fixing it.

    Hi John,

    Thanks for the report, we’re looking into it.

    We will get back to you soon.

    Hi David,

    Thanks for reporting. If I get it right, the steps to replicate it are the following:
    – Install the Ecwid plugin and any other plugin
    – On the Plugins page select both and fire “Activate” from the Bulk actions menu
    – As a result, the Ecwid plugin will be activated, but the other one will not.

    So, the issue is concerning bulk activation. But it doesn’t affect one-by-one activation. So you actually can activate another plugin after Ecwid, but you need to get back to the Plugins page again for that. Is that correct?

    Thank you,

    Thanks for the update. Yes, you’re correct — the local product sync tool indeed copies product data including images to WordPress. I should have assumed that earlier, sorry.

    Does that cause any problem in your case?

    makfruit

    (@makfruit)

    Oh, I see, thanks for the clarification.

    Can you explain what was your initial goal with that renaming? What did you want to achieve so you needed to rename/detach media files?

    makfruit

    (@makfruit)

    Hi Michael,

    This is Matt from Ecwid.

    It should be easy to check whether some particular plugin causes that — just disable it for a minute and check if the issue is still there. So, you can temporarily disable the Ecwid plugin and try uploading/managing files in Media Library — if the issue is gone, Ecwid must have something to do with it. If so, please let us know and we’ll have a look.

    Thanks,

    Yes, it is. Ecwid supports downloadable products (e-goods). This article explains how to do that: https://support.ecwid.com/hc/en-us/articles/207100559-Digital-products

    Hi,

    Thanks for the report.

    The issue should already be resolved in the latest Ecwid storefront layout. Please try to enable it and let us know if that helps. Here is how to do that:
    1) Navigate to the “What’s new” section of your store settings (Ecwid dashboard -> Settings -> What’s New) and enable the “Next-gen Storefront” option there. It will enable the new layout of the store with a revamped design, features and SEO markup.
    2) Update the Ecwid plugin in WordPress to the latest version if you haven’t yet. You can do that on the “WordPress admin backend -> Plugins” page.
    3) Enable clean URLs in the Ecwid plugin settings — this is a must for SEO. Navigate to the Ecwid/Advanced settings in your WordPress admin backend and tick the “Clean SEO friendly URLs” checkbox there.

    When you’re done, please check it and let us know if you have any troubles.

    Thank you!

    Interesting, I hadn’t considered The SaaS javascript aspect of page rendering, and how that would affect the ability to hook, filter and theme. With that in mind, it remains important that DOM structure not significantly change so we can use CSS and/or JavaScript to affect customizations.

    Agree. Thousands of Ecwid stores are using CSS to customize look and feel. So, we try to keep the CSS classes and DOM structure unchanged. When changes are inevitable, we make them as feature toggles available for a seller to enable in their control panel. For example, the houstonphotowalks.com uses an outdated Ecwid storefront layout, we completely revamped the storefront 2 years ago. You (or a store owner) can consider enabling it in the store setting — that’ll make it look better. But it’s all right if you don’t want to — this particular feature is under feature toggle so you will be able to continue using the old storefront there.

    The website I previously provided, HoustonPhotowalks.com uses some customizations, however another website, https://calidoguitars.com/ makes heavy use of customizations. I will compile a list of the customizations for you and reply back.

    That would be awesome! Thank you!

    Thanks for the response and willingness to work with designers/developers of custom sites.

    You are welcome. That’s in our best interest. There is a lot to improve for us in this area. So, your honest feedback and discussions like this is of a great help.

    • This reply was modified 5 years, 7 months ago by makfruit.

    Hi,

    Matt from Ecwid here.

    Good discussion, @mvbaxter and @ext237. Everything makes perfect sense. In fact, we added your suggestions to our roadmap to implement this in some form in the plugin in the future.

    I’ll also add a couple comments and ask your for some additional feedback below.

    As you might know, Ecwid is a SaaS solution. All of the code and data is stored on our cloud servers, the content is rendered and delivered to user browsers in Javascript. The Ecwid’s WordPress plugin is only a tip of the iceberg, it is basically a piece of code that adds the Ecwid JS snippet to the site pages, the rest is handled by the cloud part. There are some additional functionality in the plugin, e.g. SEO and some compatibility codes. But those are nothing compared to the Ecwid core code stored with us.

    This approach alone gives us a lot of unique features: automatic backups of every store on any site platform — we can restore any Ecwid shop if something happens to the site or hosting; highload management — regardless of the hosting, we handle store traffic and quickly scale up if needed; bank level security of online payments; automatic updates a few times a day — all of the security patches, bug fixes and new features are released to all users centrally.

    But there are downsides, which you pointed out: when it comes to customization, Ecwid differs from WooCommerce and other WordPress plugins. Instead of providing open database access, hooks, filters and templates like other plugins, we are providing a REST API, a Client-side JS API, different kinds of webhooks and other ‘cloud-solution-style’ APIs. Part of the reason, of course, is that we need to make sure Ecwid can be customized on various platforms, not just on selfhosted ones like WordPress. Another part is complexity of mixing selfhosted/cloud approaches to API. For example, since the output is generated on our servers (not on a WordPress site), it’s tricky to design filters/hooks properly.

    The existing APIs do allow third party developers to extend Ecwid functionality or adapt it to websites better. But as you mentioned, that’s the matter of convenience. The WordPress developers community got used to the WordPress APIs. That’s not easy to switch patterns, especially if you customize several plugins and a theme at the same time and make them work together. No doubt, customizing frontend templates is much more convenient in WordPress “style”.

    But that’s still possible to create a useful API for our selfhosted part (WP plugin). And the feedback you provide is of a great help.

    Now, as this is apparently a big project, we’d like to understand where to start. So, can you provide a few examples of what exactly you wanted to customize in an Ecwid store recently? For example, changing the colors/fonts of the product description, or building a custom form on the cart page, or binding a custom logic to the “add to cart” event, or embedding product information into another WordPress page etc. The API design suggestion you made are great — we just need to make sure the API we’ll create will help you achieve what you want exactly. When we start working on it, we’d better start with some quick and useful part that would bring value as soon as possible.

    Thank you,

    We at Ecwid thank you for your kind words!

Viewing 15 replies - 1 through 15 (of 285 total)