Is there an updated Design Guide for 2.0, or should be be using the old one?
Is this guide available for trial users?
DELETE
After I realized that I cannot use the newest version of cs-cart, because due to language problems and a missing tutorial I do not understand how I can change a template in 2.0 (what the hell is a hook?) to the template I already made for the previous version. I don’t have the time to struggle through the whole forum finding some advices here and there. My English is not bad, but not good enough to understand how that works.
I made a new template and let CS-Cart update - and after that my new template had been changed. How does the update know what to change? It was a new template, not a copy of another one! And so on. I hate the way template are organized in the new version of CS-Cart! I’m so disappointed. I already spent so time in CS-Cart.
[quote name='djstevie84']
www.
[/QUOTE]
Normal and hover font size could be same size, you can change it in css
for:
[QUOTE] Cart is empty · View cart[/QUOTE]
Using FF
i am pretty upset. i am not very happy with v2 thus far. i have clients who are waiting for me to to basic changes and i can not.
languages massive issue that should have been corrected before release.
i can’t even figure out how to change the top banner on one of the native styles. i am going to lose on this project, i can tell already.
[quote name=‘mpjbay’]i am pretty upset. i am not very happy with v2 thus far. i have clients who are waiting for me to to basic changes and i can not.
languages massive issue that should have been corrected before release.
i can’t even figure out how to change the top banner on one of the native styles. i am going to lose on this project, i can tell already.[/QUOTE]
Try using the free “Local Confiiguration” addon provided by EZ Merchant Solution provided from here.
Documentation (and a list of all template hooks) can be found in this pdf
We also provide consulting services if you are in need. If you want to manage multiple skin revisions and manage the upgrade of inactive skins, read this thread for more information: [url]http://forum.cs-cart.com/showthread.php?t=12447[/url]
In other words: It is not possible to use this version of CS-Cart as it is AND make your own templates easily like it is advertised?
Using version 1.3.x and former versions it is possible!
[quote name=‘Miss Marple’]In other words: It is not possible to use this version of CS-Cart as it is AND make your own templates easily like it is advertised?
Using version 1.3.x and former versions it is possible![/QUOTE]
Yes you can, that’s not what I was saying. What I was trying to explain is that if the template is “named” the same as the standard skin then you will have to manually resolve conflicts at each upgrade. If you use the Local Configuration addon then it will separate your changes in a manner that prevents conflicts during an upgrade.
[quote name=‘tbirnseth’]Yes you can, that’s not what I was saying. What I was trying to explain is that if the template is “named” the same as the standard skin then you will have to manually resolve conflicts at each upgrade. If you use the Local Configuration addon then it will separate your changes in a manner that prevents conflicts during an upgrade.[/quote]
The template which was overwritten was called “Naturez”, the folder was called “Naturez” and I copied everything to the vars-folder as well. Manifest.ini begins like this: description = “NATUREZ skin”. That’s like I made my templates before.
If I as a web designer and programmer need a third party plugin and manuals from third party to make my own templates I have to say: CS-Cart 2.0 does not deliver what they promise in their promotion. If I got you right it was necessary that users programmed something to get CS-Cart 2.0 to work as intended.
I bought CS-Cart once to get a cart which can always be updated. What I see is that this was a mistake. I’m so disapppointed.
Have you reported the issue to CS-Cart in the Bug Tracker? This is a serious issue which needs to be addressed.
Bob
Hi Bob,
because I don’t know what’s a feature and what’s a bug, I did not consider to report sth. If there was a manual from the developers I probably could make out the difference. And I must admit - I’m not fancy helping to bugfix any more.
But I already made the best out of it - I will have to stick to the old version. This is the lesser of two evils, because in the new version there is still no possibility to generate invoice numbers, or more than one invoice per order (because the invoice is the order itself in reality, not an invoice, frankly speaking). Invoices should have their own table in the database, but they left out this part. I hope I will find a way on my own to get my shop installation conform to European laws.
I meant the fact that it overwrote your custom skin - that would clearly be a bug. If we don’t report the bugs, the developers will not fix them.
I fully agree about the invoice number. Order management in Magento is way ahead of CS-Cart because:
- you can have multiple separate shipments for an order, each with its own shipping information:
- you get a separate sequential invoice number for each shipment unrelated to the order number;
- you have the basics of a backorder system since you can have unshipped line items.
I really hope CS-Cart improves in this area because they have many other features which are much better (or non-existent) in the competition.
Bob
[quote name=‘jobosales’]1) you can have multiple separate shipments for an order, each with its own shipping information:
2) you get a separate sequential invoice number for each shipment unrelated to the order number;
3) you have the basics of a backorder system since you can have unshipped line items.
I really hope CS-Cart improves in this area because they have many other features which are much better (or non-existent) in the competition.
Bob[/QUOTE]I’ve got to agree with you on this Bob. This is a huge hole that needs a solution. At the least, I’d like to be able to clone an order, then modify both as req’d. I could then put the status of the edited cloned order on backorder, allowing me to ship partial orders. But that’s a long way from an ideal backorder system.
The crux of the problem is that the “fulfillment” of an order is managed in the cart at the “order” level versus the “item” level. Additionally, there is no mechanism of authorization of CC at time of sale and then charge at time of shipment (or charge portion for multiple shipments).
Carts are generally geared toward the sale side of the equation. The merchant’s needs related to fulfillment are generally ingored. This is not unique to cs-cart.
So the solution today is to use an order/inventory management system that can actually manage the items within an order and the associated payment methods that match the business operations model. The order management solution needs to be tightly integrated with the front-end storefront so that infomation between the two is always consistent.
EZ Merchant Solutions (http://www.ez-ms.com) provides just this solution. However, it is geared toward real businesses, not for the merchant that sells cake recipes in their spare time.
Managing the fulfillment side of a real online business is quite a different issue that managing how your items are presented to your cutomers for sale. The complexity of “the cart” would increase to such an extent that it would probaby become unmanageable for those simply wanting a storefront solution.
Personally I belive that the storefront should be used exclusively for presenting products and securing the sale. Following the sale, management of fulfillment should be done within an application that specializes in those operations.
[quote]
I meant the fact that it overwrote your custom skin - that would clearly be a bug. If we don’t report the bugs, the developers will not fix them.
[/quote]
It overwrote the skin because it is (was) the “active skin”.
The upgrade doesn’t care what it’s named, it upgrades the “active” admin and customer skins with any change that have occurred within skins_repository/base. Other “skin specific” changes will not be applied to your newly named skin.
The upgrade assumes that anything in the “base” directory is common to all skins unless there is a file of the same pathname in one of the skin-specific directories. I.e. if base/customer/blocks/foo.tpl is changed in 2.0.9 and a file exists in default_blue/customer/blocks/foo.tpl (but is not in the upgrade) then if any skin other than default_blue is the ‘active skin’, then foo.tpl will be upgraded in the ‘active skin’.
Again, the skin revision manager I developed (see #6 above) allows you to specify which skin will be upgraded and which skin you want active for the customer view. You can also develop in a different skin without affecting the currently active skin.
I hope this is clear.