wakabayashi

You have good speed on your site 🙂

I don't know if I have already reported. But there is an issue with criteria that don't apply to all products/categories. In my case I always apply them to categories. But when I edit such a criteria, the categories aren't selected. In addition it says something like: "apply to no product" in the overview.

Yeah I got this. That's why I want to implement the expiration feature. But I really don't get the point having part "expiration". Either it makes no difference at all (when customer doesn't order anymore and lose all it's coins). Or the user loses a part of his coins (in your way) and none coins (in my way). But I as a customer would be totally angry if your case comes in. If I place a new order at your store and still lose some of my coins I would think: Ar they kidding me? I am still buying stuff there, but still delete my coins :S In addition: how likely is this case? As far as I understand a loyalty points system almost always works like this: You order something and collect a few points. You use them on your next order and the thing is done. Doesn't 99% of the orders work like this? Probably the module doesn't show it. But I get your point. There is nothing wrong in adding this number somewhere 😉

Yes it's working now...

Tbh: that would be quite a huge rewrite/extension. And I really don't believe it's user friendly. If somebody is interested to code this solution, I am open for merging something. But I won't code this "feature" myself. When I am looking again deeper at the module I will think, if I can implement a solution for customer returns.

Well maybe it's a cache issue. When I visit the link from above, there isn't "checked" in the html source code.

Yes that should work. Does it?

Please search in your tpl files for "check_autobid" and then post the code of the tpl.

I can't find the correct place... Either it's still the wrong tpl or it isn't a checkbox at all. A link to an example could help.

I dont think that is the right tpl. It should be have something like: input type="checkbox" Edit: yes the second one looks better.

@AndyC and @datakick Is this an en error from conseqs or something of my module krona? Btw: I haven't forgot about the expiration. It's still on my todo list. I just have too much other works, to do right now...

The checkbox is probably inside a tpl file from the module. So we need to see this code...

Probably what you search for are the tpl files in the theme folder. Best way to find such things: you download your website to your desktop and use a HTML editor which can search trough all files. Then you search for something specific (class, id or so) and it the search tells you which file it is.

What does not work? Any error when debug mode is on? You posted two times the same override...

No you don't need to concern too much about these warnings. Since some weeks google got aggressive in making this warnings. Rich snippets are no direct ranking factor, but they can help indirect. An example: If you have rich snipped correctly implemented for ratings. You have the chance that google shows stars for your products. This can help, that more people click on it. BUT what if you have 0 reviews for a product? Then google will warn you and you can't even do something, since you just don't have ratings. In short: fix the one, who takes a few minutes. But invest the hours in improving your shop in general. (Descriptions, Images, Blog posts, Newsletters and so on...)

I looked a bit into it. It seems to be theme related... You would need to edit product.js in your theme. There the function getProductAttribute(). But I am really not sure if this is worth it...

Probably ZenCart doesn't even do the rich snippets 🙂 It's also a question of training... With every day you get better, to handle your store.

Have you deleted cache? I still see the wrong html code when I visit your blog post. Have you checked datakicks adivce with the theme folder?

Np. Please tell afterwards if it worked 🙂

This tells you what to do: https://github.com/thirtybees/beesblog/commit/471b64dbb8b6c50b2ce2bb0e1d547a2e6f777fca Let me explain a bit. You need to go into your module files: /modules/beesblog/views/templates/front/post.tpl There you remove the red line as you see it in github. You add the green line on the same position. Then you do the same for /modules/beesblog/views/templates/front/post_list_item.tpl

Isn't that the normal behaviour? I am the owner of chesspoint.ch. I changed some things with attributes, since I don't want to have any "default" attribute. But I can't remember, that I removed the id in the url 😮

If it refers to the blog. First important information is: which blog module do you use? It would also be helpful to have a link to the blog post or blog category where the error occurs.

@Traumflug Well it makes sense, if you want that. But as he is aksing for csv files this can lead to new entries in the db, which arent wanted. Of course depending on how the csv looks like.

You to to inspect the code in your browser. It's very easy: just right click and then something like "inspect". then a tab will open where you need to search for something like "console".

Well save() will add new product as well. update() will only update exisiting products. I highly doubt save() makes any sense in this case... To me this sounds all a bit complex and as I said you need to be careful. I don't understand why you have id_product at all in your csv? Where comes the csv from?