Sorry for addressing this topic again. Could me please somebody explain, why this topic is not marked with a high priority? The shop should be able to serve cusomers in different languages. At the moment the shop can only display Shipping/payment method's in one language. Do I understand something wrong or is there a workaround? Is everybody here working only with one language or why nobody have a problem with this missing function.
I prefer to prioritize items that customer oriented vs employee oriented:
1. Facebook, Open ID, Live ID membership integration 2. Performance optimization 3. One-page checkout support (was not included in 2.00) 4. Adding templates for products, categories & manufacturers. 5. Generic Attribute Mapping 6. Web Services
Congrats on the 2.0 release. Will start looking at NopCommerce again more seriously.
hey guys in the department of performance i think you should take a look at this and see if possible to implement in 2.1 this is from google code after testing my site with page speed from google
Overview Deferring loading of JavaScript functions that are not called at startup reduces the initial download size, allowing other resources to be downloaded in parallel, and speeding up execution and rendering time. Details Like stylesheets, scripts must be downloaded, parsed, and executed before the browser can begin to render a web page. Again, even if a script is contained in an external file that is cached, processing of all elements below the script is blocked until the browser loads the code from disk and executes it. However, for some browsers, the situation is worse than for stylesheets: while JavaScript is being processed, the browser blocks all other resources from being downloaded. For AJAX-type applications that use many bytes of JavaScript code, this can add considerable latency. For many script-intensive applications, the bulk of the JavaScript code handles user-initiated events, such as mouse-clicking and dragging, form entry and submission, hidden elements expansion, and so on. All of these user-triggered events occur after the page is loaded and the onload event is triggered. Therefore, much of the delay in the "critical path" (the time to load the main page at startup) could be avoided by deferring the loading of the JavaScript until it's actually needed. While this "lazy" method of loading doesn't reduce the total JS payload, it can significantly reduce the number of bytes needed to load the initial state of the page, and allows the remaining bytes to be loaded asynchronously in the background. To use this technique, you should first identify all of the JavaScript functions that are not actually used by the document before the onload event. For any file containing more than 25 uncalled functions, move all of those functions to a separate, external JS file. This may require some refactoring of your code to work around dependencies between files. (For files containing fewer than 25 uncalled functions, it's not worth the effort of refactoring.) Then, you insert a JavaScript event listener in the head of the containing document that forces the external file to be loaded after the onload event. You can do this by any of the usual scripting means, but we recommend a very simple scripted DOM element (to avoid cross-browser and same-domain policy issues). Here's an example (where "deferredfunctions.js" contains the functions to be lazily loaded):
<script type="text/javascript">
// Add a script element as a child of the body function downloadJSAtOnload() { var element = document.createElement("script"); element.src = "deferredfunctions.js"; document.body.appendChild(element); }
// Check for browser support of event handling capability if (window.addEventListener) window.addEventListener("load", downloadJSAtOnload, false); else if (window.attachEvent) window.attachEvent("onload", downloadJSAtOnload); else window.onload = downloadJSAtOnload;
Here are few shortcommings of previous versions of NopCommerce that had me coding. Therefore I feel they're good candidates to include in upcomming release:
-> performance optimization - although I must admit 2.0 is already much better in this regard than 2.0 beta
-> checkout process improvements; ability to supress certain screens (eg. billing address, confirmation button at the end etc.)
-> build in "checkout with paypal" (jump to paypal staright from shopping cart screen)
-> VAT on PDF invoices
-> more flexibility in the Shipping.ByWeight module; -->ability to wildcard countries (all EU countries; all North American counties; Australia and Oceania etc) -->ability to specify that shipping charge is per weight unit eg. $5 / kg so 0.3 kg is 1.5 usd; -->ability to specify shipping charge based on base fee + per weight unit
-> tag types; tags are very powerful so its logical to use them in may ways; eg. in the book world they can be used for authors, publishers, book series etc.; it should be possible to define "type of tag" and be able to display all tags or given type or all tags of given type related to product;
-> ability to display geotargeted messages to customers; eg. "hi Mr. I am Canadian, we ship you things for free"; (we already have gotargetting stuff in the code)
-> sort categories alphabetically button :-)
Some of this stuff is really simple, some more complex.
