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.
Related
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 4 years ago.
Improve this question
I'm working on a webshop. And would like to add the feature to be able to post product images to the shops Instagram account when a new product is added.
The thing is that the Instagram API does not seems to allow to post images. Either does the official Instagram Website. And a Google Search gives me multiple SO QA which says the same.
But at the same time, there seems to be a ton of websites, applications, and services and other non-emulators who let you post to Instagram (to mention a few: http://techwiser.com/effectivly-use-instagram-on-pc-upload-pics-bluestacks/ and http://dskgrm.com/ is another one, there also seems to be some WordPress plugins who does it ex. https://github.com/roladn/wordpress-to-instagram but I'm not too good with eirhet PHP or WordPress to be able to tell how they have done it.).
And before anyone reports it as a duplicate. I do not consider this a duplicate since all other QA simply states that it is not possible via the API, but obviously, it is possible somehow, and I'm wondering how.
So I simply wondering how people are successfully implementing this feature when either the API or the official website allows it?
No official way to post media to Instagram doesn't mean that there is no way to do this.
If you are a developer you could simply reverse engineering the Instagram API and build some software to use that, otherwise you could just use some tools already developed.
PHP
mgp25/Instagram-API
Python
b3nab/instapy-cli
And if this don't fit your needs you can go to github and search some other softwares already developed.
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 4 years ago.
Improve this question
Consider a website with multiple sections, each with a different set of data/features. Now to promote the website through blogging which of the following method is better and how is it better than the other:
A single blog is created which has multiple categories and each category corresponds to one section of the website. In this way each and every section of the website is covered and you can manage all the stuff in just one blog.
Separate blogs are created for each section of the website. The content of each blog is unique and you can promote each section of the website more precisely.
It depends. If the sections on your website cater to each other e.g surround a common theme I would only create separate blogs if you have enough content to fill them up in a quality way.
Gaining readers, backlinks and reputation as a site will be much easier if you can focus on one blog.
If the content on your webpage is very diverse I would go for separate blogs. That way its easier for your readers and searchengines to grasp your theme.
If your website has multiple industries and each one is serving many services, then separate blogs for each industry and categorize them with your industry related services.
If your website is focusing only on one industry then simply make a single blog and categorize them with different services. It will also help the users to read stuff related to your different services from a single platform.
separate blogs used only for first positions using url more work and time required if multiple blogs
but single all in one blog have always success and high view and earnings and seo for single blog is also easy and permanent
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.
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!
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 10 years ago.
Improve this question
I need to help a human rights organisation to setup a donation page at their website. They have tried PayPal and GlobalGiving and they found some glitches with these services like ceiling, transaction fees, etc. They want to setup their own mechanism. So what are the possible options and how much programming is needed? Is there any free-open source e-commerce or charity modules available?
Sounds like you are looking for something very customizable here, what I would recommend you is to do some custom coding or leverage solution like wufoo. You can build as simple as a form that whole bunch of fields and sends all these result to paypal or other payment gateways. Leveraging pre-built solution like wufoo is often recommended for non-technical people and/or simple, quick tasks like this.
(Alternatively) Most well-known applications like drupal, Joomal, wordpress (you name the rest) have fairly good support/module on this area, however, most of them require some degree of customizations and often become an overkill solution (mainly because of the learning curve).
You might look into Google Checkout. It's not free, but they do have an option tailored to non-profits (link).
The main benefit of going with them is that you won't need to set up a direct relationship with a CC merchant gateway, which can be a good sized hassle, especially for a smaller nonprofit. To me, the other benefit is that it keeps you far away from Raiser's Edge / Blackbaud, purveyors of some of the most awful donation pages I've ever had the misfortune to see or use.