@mdekker When I first set up Amazon payments and PayPal I had problems. The PayPal one was related to a bug which you fixed (missing code) and then PayPal worked fine. It may have broken when I upgraded to 1.01 or it may have happened with the PayPal upgrade. I didn’t check it until after the PayPal upgrade.
The Amazon issue was on their end and is now fixed.
The other url problem I have is that the blog category page pulls up the post_default image instead of the post_list_item image.
This thread has been very interesting to follow. But again most of the discussion is for the nerds that is members of this forum, not for all of the ones that is merchants only, not tech freaks.
Search is really something a person can geek out on. It’s always interested me because good search makes a system/store/website a joy to use while slow or non-functional search leads to immense frustration, at least for me.
What shoud they choose, They ofc want a very good system. Not all of them will go to Shopify or Bigcommerce or whatever, its very expensive.
I’m definitely not going with a packaged system. They can be a good fit for some people but it’s not for me.
So for them it reall does not matter, Algolia is there quite easy to setup but can cost a lot. But that is really the same for Elastic. If you want to use the Cloudservice they provide, it quite quickly get very high priced.
Algolia has a free option that should be fine for stores with 1000 to 2000 items as long a they aren’t too busy with visitors. I don’t know if they limit features or performance but they do force a logo to be displayed on your site which is not ideal.
Elasticsearch also doesn’t have to be expensive. For a similarly sized store it shouldn’t be a problem to run Elasticsearch on a smallish VPS together with the web and db servers. If you site gets busier or your catalog grows then something else will need to be done but a separate small VPS should be enough for even a relatively large (~100,000 products) store.
I don’t know about other hosts but I know that Cloudways offers Elasticsearch on their plans. Just check a box to turn it on, no configuration necessary.
Why is it so? Computer power and bandwidth is cheap nowadays. I would like to see a very good TB module that can connect to a good priced Elastic provider. Not one that charge hundreds and hundreds per month. It is fully possible, someone just have to start
Most of the hosted ES cloud providers are focused on larger installations and are priced to match. They also tend to be on AWS which is expensive compared to many cloud hosts.
I think that with 30bz being open source it would be nice if the standard “advanced fast search” module used an open source search engine, but unfortunately I don’t have the skill to code the search module myself.
Placing the support email address more prominently? Email does everything a ticketing system needs (answer goes to the customer only, customer gets notified, history is preserved) and on top, a new customer doesn’t have to create an account. One can even place mailto: links which pre-fill that email, e.g. with a ticket number and/or the currently visited page.
It’s a one-page checkout like in having only a single page. Cart at the top, then addresses, carriers, payment options. Only caveat I can see is that one has indeed to save the address before one can choose a payment option. That’s somewhat unavoidable because one can’t make a contract (binding prices and processing times) without knowing about the shipping address first. PS 1.7’s “one” page checkout suffers the same; the later steps can’t be opened before the first two are filled and saved.
@mdekker is there a way to force a footer link to open in a new tab? I know it should be target = “_blank” but how should the link look. It goes to an external site and I dont want the customer to leave the shop
Preview used to be a feature, but we removed that last-minute. The permission to preview an item was linked to the customer email. (If customer email = admin email, show). But as you can guess, what if someone just creates and account with an email that happens to be an employee? Yah, that’s a prob! So we have now begun testing on reading the back office cookie and check the employee’s status instead and use that for previewing.
Author widget is nice. We want to use Gravatar for it. No idea actually why it didn’t land in the first version. I think we forgot.
Yeah, language field should definitely be disabled for one language and have some defaults.
Yes, linking to products/categories should go both ways.
Shortcodes are awesome, but I don’t think the core is ready for it, yet. We’ll likely combine it with a widget system in the future.
I always wanted to make a simple module that shows your limits for a country. So I have researched this topic a few times already. Besides that I also sometimes act as a consultant, so have to know all this.