Also, any product I add with a variation doesn't show up in category page.
You can search for it and find it etc
If I add 10 variations initially, and then come back later and add an 11th, the previous 10 will be deleted.
Can you please provide the step by step instructions on what you did. I don't quite understand the how to reproduce this.
Also, any product I add with a variation doesn't show up in category page.
You can search for it and find it etc
Yes, this is how it should be. We shown only simple and configurable products by default.
Initially one works with variations from configurable product page.
You want to show all variations on the products list by default?
If I add 10 variations initially, and then come back later and add an 11th, the previous 10 will be deleted.
Currently variations can't be added separately via the admin panel interface; they can only be generated. Generation removes all the variations that you created for this product earlier. This behavior is covered in 2 documentation articles:
• Adding product variations
• Differences between product variations and option combinations
Thank you for bringing this up; I've posted a feature request concerning this.
Yes, this is how it should be. We shown only simple and configurable products by default.
Initially one works with variations from configurable product page.
You want to show all variations on the products list by default?
So how do you expect the customers to find products with a variation then?.
FYI - I was talking about the top level product, not all its variations. Yesterday we could not even get these to show in category. However, today, have gone through the process from scratch and appear to have it sussed.
It was decided that changelog should be kept in the documentation.
By whom? Bad idea for reasons stated above. You can very easily keep it in both places since it's a txt file. Please return the changelog to the distribution. If you want to shorten it to make it just that release, that would be fine.
Why did you stop having the changelog.txt be in the releases? Much easier to see what changelog.txt relates to the client's installed version.
You can very easily keep it in both places since it's a txt file. Please return the changelog to the distribution. If you want to shorten it to make it just that release, that would be fine.
We did it to streamline the release process by cutting down on extra actions that took time but didn't add any value to the product increment or ensure its quality.
With the changelog those extra actions were:
• Getting the changelog to a couple of branches in the repository, while making sure that the commit hash is the same across these branches.
• Making a couple of pull requests and having another specialist merge those pull requests.
• Waiting for the release to be built once again.
• Re-checking the release and making sure that the archive has been uploaded everywhere it needs to be.
If there were any significant last-day or last-week changes, these actions delayed the release and took time from our specialists, just for keeping the changelog up to date. That's why we decided to keep the changelog in the documentation only.
So how do you expect the customers to find products with a variation then?.
There are 2 ways:
1. In advanced search select "Product Variation" https://www.evernote.com/l/AQHwSiic-4RGqILnAb0I-bWAquiFEp1b8FM
You can btw save this search.
2. On the configurable product page (parent product), there is a tab "Product Variations"
We did it to streamline the release process by cutting down on extra actions that took time but didn't add any value to the product increment or ensure its quality.
From a customer and development partner, those are lousy reasons. Most of your reasons don't apply to a single file modification in the repository.
Just my two cents. You can ignore it as usual.
From a customer and development partner, those are lousy reasons. Most of your reasons don't apply to a single file modification in the repository.
Just my two cents. You can ignore it as usual.
What do yo mean under "Most of your reasons don't apply to a single file modification in the repository."?
You can read what Continuous Integration mean. Team should be able to release new version at any given time without additional work like "preparing changelog" etc.
Why was CKEditor removed? Our team is used to that editor. We rolled our own custom CK before this happened so its all good here, but still very curious why that editor would be removed.
And thanks for fixing "A logo from the wrong storefront could appear on the invoice when multiple storefronts were used" super annoying bug. I couldnt believe how hard it was to force the baked in logo func to grab correct layout/runtime -- actually gave up on it to make a custom func.
For anyone in previous versions of CS, this will grab the correct logos while in "All Stores" mode https://github.com/dhaupin/cs-cart-fn_get_logo_simple
Put this in invoice.tpl's somewhere after $order_info check (there is no hook here):
{if function_exists('fn_get_logo_simple')}
{$logos.mail.image = fn_get_logo_simple($order_info.company_id, 'mail')}
{/if}
Profit.
What do yo mean under "Most of your reasons don't apply to a single file modification in the repository."?
You can read what Continuous Integration mean. Team should be able to release new version at any given time without additional work like "preparing changelog" etc.
Sorry, updating changelog.txt should be a standard part of your release process. If you make a change to the product, updatng a single line in the changelog.txt file should:
1) be automated with your GIT comments and the whole file should be regenerated based on the individual file versions and their comments in git.
2) Even if manual, should be a quick part of the process and shouldn't inhibit the release.
3) It ensures that the changelog.txt is part of the md5 of the release archive and that they are in sync.
Without it being synchronous with the release, there's not way to have confidence that they will match. There's no part of the described process that ensures that changelog.txt on a separate web site matches or is available at the time of the release.
It seems to be a change that does nothing for customers/developers and might save 5 minutes out of the release process (if any).
Again, having the whole history of releases in changelog.txt isn't necessary. That should be in the documentation. But the current release changes should be documented within the release.
Since no one else is chiming in here, I'm assuming I'm alone in my beliefs.
Remember that this all started because someone saw a change that they were NOT aware was coming. I went to look in changelog.txt and saw the pointer to the documentation web site. I then copy/pasted the link and went to the site and searched for 'expir' and it didn't show me a changelog entry, The search result showed me an area of the addon developer's page which I'd stated was not a good place for a customer to find changes since most merchants are not addon developers.
You should be making it easier for customers/developer to identify changes, not more difficult.
Why was CKEditor removed? Our team is used to that editor. We rolled our own custom CK before this happened so its all good here, but still very curious why that editor would be removed.
You can use full version of CKEditor from our team
https://www.ecom-labs.com/ready-to-use-add-ons/cs-cart-full-ckeditor-add-on.html
So, where can I find change log?
The changelog in the root of your store should contain the following:
Legend:[+] - new feature/improvement[*] - functionality changes[!] - bugfixChanges in version 4.6.1 and future versions are described in the documentation: http://docs.cs-cart.com/latest/history/index.html
There are 2 ways:
1. In advanced search select "Product Variation" https://www.evernote.com/l/AQHwSiic-4RGqILnAb0I-bWAquiFEp1b8FM
You can btw save this search.
2. On the configurable product page (parent product), there is a tab "Product Variations"
Are you saying that a Product with Product Variations will not show in the storefront under its Category.??
Is that something that will be fixed?
I want to start using this addon, but since it seems to have a few issues, reluctant to try it out.
You can use full version of CKEditor from our team
https://www.ecom-labs.com/ready-to-use-add-ons/cs-cart-full-ckeditor-add-on.html
Ah cool. You're missing some essential plugins though like codemirror, autosave (patched), textselection, etc. Also CK 4.7.1 is available now (your addon uses 4.5.9).
Here is v4.6.1 with a bunch of plugins including the patched autosave (i think its in their repo now), if anyone is interested: https://github.com/dhaupin/cs-cart-lib_ckeditor_full
Ah cool. You're missing some essential plugins though like codemirror, autosave (patched), textselection, etc. Also CK 4.7.1 is available now (your addon uses 4.5.9).
Here is v4.6.1 with a bunch of plugins including the patched autosave (i think its in their repo now), if anyone is interested: https://github.com/dhaupin/cs-cart-lib_ckeditor_full
Thank you for the message. We plan to update CKEditor version soon. I will also discuss 3rd party plugins with management