Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Which one of OsCommerce, ZenCar and CubeCart is the easiest to customize with a custom design template? I know ZenCart is an offshoot of osCommerce so I'd guess they would be similar.
ZenCart and OSC are similar, but I would recommend Zencart over a standard OSC for template customization. I haven't used CubeCart.
If your modifications are only html/css customizations for one shop you should be fine with Zencart, although there are quite a lot of files to make a full template, with the modification of a few files on an already made template you will go a long way.
With the default template, I would suggest starting with:
Under the common folder: html_header.php, tpl_header.php, tpl_tabular_display.php, tpl_columnar_display.php, tpl_main_page.php and tpl_footer.php.
Sideboxes folder: the sideboxes you plan to use if you require html changes to them, perhaps you won't, with CSS you should be able to modify their appearance quite a lot.
Under the Templates folder: you will probably need to modify the html in the checkout pages, the product_info_display page and the half a dozen listing pages.
You don't mention Prestashop. It is a much more modern software than Zencart or OSC (code wise), completely written with OOP and, more importantly, it uses Smarty for its easy to follow template system.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 5 months ago.
Improve this question
We use massive bunch of components in our products with Vue 2 (migrating on 3rd version) and Nuxt SSR. Could we improve our project performance with removing scoped block of styles (how much)?
Scoped CSS can have some performance impact: https://vue-loader.vuejs.org/guide/scoped-css.html#deep-selectors
So you could improve it if you can achieve the styling without the CSS scoping (even tho, depending of the solution replacing it, that may be more heavy overall).
How much is hard to answer here because it depends of your app and if you have some performance benchmarks already.
Migrating to Vue3 will bring quite some performance tho. But as everything, it all depends on the current bottlenecks. If you have a Google UTM tag importing à whole 3rd party chat library, removing the scoped styles will only have a minor impact.
So yeah, to broad of a question with too much variables to give a concrete answer.
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
To Zerobrane users, since this is not a question on lua :
I use Zerobrane for editing lua programs that are to be used with LuaLatex. Very nice !
I make all tests there before using the developments in LuaLatex. So, at the beginning, the programs are run there. I need to tidy up this part, on ZeroBrane, by making files hierarchical, with a master file and slave files around.
Once again, it is a question about ZeroBrane, not about how I use the file within LuaLatex (I know enough about doFile, luaexec and co)
Does this exist ?
I saw PaulK passing by, if he could drop a line, it would be appreciated ...
An "include mechanism" as you call it is usually a language feature, not some feature of an IDE.
Lua provides various functions for running code from other files.
dofile, load, loadfile, require, ...
The most convenient and common is require which will find a file by its name in a given set of directories and execute its contents.
Read this:
https://www.lua.org/manual/5.3/manual.html#6.3
https://www.lua.org/pil/8.1.html
https://www.tutorialspoint.com/lua/lua_modules.htm
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
Any idea how to run multi language Shopify site? JavaScript hacks are not the solution, cause it breaks SEO. I can't imagine how to do it by templates and pages.
I would say: Don't duplicate your store. We did it once and it was a nightmare. (you need to have duplicate products, duplicate collections, duplicate pages, duplicate settings...) It all depends on your company size and how many people you can allocate to each store. We used the translator app and it's working pretty good though checkout is not translatable.
UPDATE: (february 2015)
There's 2 new localization apps in Shopify:
a.- Langify (good solution but it really dirts a lot your liquid code)
b.- Localize.js (great solution and incredible clean and fast dashboard, which uses its own strings database so you don't use Shopify metafields)
Sticking back to your question, answers are:
Use david option (open one store for each language).
Use any of the i18 available Shopify apps.
No way by using liquid as you'll need to create a session to set the language, and this can only be done with JavaScript.
You can see an example of a Shopify store with multiple languages (spanish+catalan+english) here: Pienso para perros - Dr. Pet
Call up Shopify. Ask for a deal on a needed second shop. You can re-use your templates of course. Now just edit your inventory to have your second language translations. Import.
You can provide language switcher links in your shop. Of course, if inventory counting is important, allocate half to each shop.
To run your show, bookmark both admins, and now you're in business.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm really attracted to the webservice.js module. I'd like to use it as a real webserver, using only an HTML page with JS calling the webservice to retrieve the datas.
The problem I'm seeing is about the search engines, as I do wish my website to be search engine optimized.
So I thought I could be fallbacking to plain HTML when JS is not enabled (just going to the url, webservice.js sends back some datas in plain HTML). For this, the links will be displayed in the HTML markup on the frontpage.
The problem is about how much SEF have the URLs to be?
I mean, the webservice will allow me to have URLs of this kind : http://domain.com/content?get=title-uri-encoded.
Is it search-engine friendly? I know having http://domain.com/content/title-uri-encoded would be better, but is the kind I'm thinking of still friendly?
PS : I'm not sure whether this post belongs to SO or Programmers.se...
You probably want to look into progressive enhancement techniques or Google's proposed AJAX solution.
You may end up with a URL structure like this:
AJAX enabled public version
http://domain.com/content#!get=title-uri-encoded
Search Engine version (plain html)
http://domain.com/content?_escaped_fragment_=get=title-uri-encoded
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am going to be taking over from a developer here at work soon. Hence, I'll be supporting all the applications that he has written over the last few years.
My question is, when supporting an application that you probably don't know much about, what kind of documentation is most helpful to get a handle on how to fix problems, extend functionality, modify functionality, etc? I'm thinking it would need to give you an overview of what the software does, what interfaces it has to other software, what databases it uses, usernames, passwords, and so on.
Is there such a thing as a software support document? Referrals to any templates would be most helpful.
BTW, unfortunately, there are no requirements documents, specs, etc! So, really my question is, if my colleague had a day to write a single document for each application so that I could (more easily) support it, what would that document be and/or what would it look like?
I would ask for primarily some sort of flow chart/schema of the way the app functions.
I would want to be able to know how each file interacts with other files (and the database). So this way, you'd know where to start to fix a bug or add a new feature, etc.
So to do a quick, text mockup of it:
Index.php -> Login.php -> Dashboard.php
Index.php:
Has login box. Submits login into to login.php
Login.php:
Verifies data with database entries, shows error on fail or sends to Dashboard.php
Dashboard.php:
Once logged in this acts as a main menu
Something along these lines? For basic documentation I'd think this is the way to go.
Hope this helps. Good luck!