How to install Magento and skip the database validation? I don't need sales order, shipping, etc. Just wanna make a Magento as a CMS module.
Or, any best CMS that running lightly?
i've tried Magento Lite but there's an error.
not sure what you mean by "skip the database validation". But if you want to use Magento as a cms and have the sales and other modules stripped I recommend this.
It's a Magento version that has stripped the catalog, sales, customers and many others.
I've tested it and it runs smoothly.
[EDIT]
If you are asking about any CMS in general or looking for one that runs lightly, then I think this is completely off topic and to broad for any answer to cover it.
Each CMS has it's advantages and disadvantages.
I think you shouldn't base your search for a CMS on its "lightness". This should be a secondary reason. First you have to find the ones that fit your needs and then compare them.
Start looking here for example.
Related
I have extensive modifications to carry out on a prestashop 1.6 site.
I have created a local copy, and am tracking filesystem changes in git.
However a lot of changes in prestashop are stored in the database, specifically in my case:
Installing and configuring a new module
Uninstalling a module
Adding shop categories and changing the hierarchy
Changing module positions
and generally modifying what modules appear in what hooks.
During the dev process, the live site has received numerous new orders, customers, subscribers etc, so the databases are out of sync.
I have solved similar problems in other frameworks by dumping and importing specific tables in the db, or using the frameworks built in migrations functionality, but i cannot find any advise specifically for prestashop.
How is this handled?
Considering that the dev site has probably undergone more diverse changes than the live one, i wonder if it would be easier to copy the new orders etc over to the dev site then overwrite the whole thing?
I don't think that it is possible to achieve this in PrestaShop. You must have immense knowledge of PrestaShop DB (i.e. have knowledge of each and every table and columns in it) to merge the databases.
It is never recommended to do that either.
I suggest you do the syncing manually as it is a very risky task and you might lose all the data in your live store, which will be even more painful.
For modules the information is stored in all tables which start with modules.
Module config values are stored in configuration and configuration_lang. Make sure you also copy custom module tables of course.
Shop categories information is in all tables which start with category.
Module hooks information is in all tables which start with hook.
However as Raghubendra Singh said in his answer this is very risky task, if you really really want to do it, I suggest you create another local copy of currently live site and first try the process between two local copies and make sure everything works correctly.
I can tell you my experience on updating the Prestashop and using it everyday.
For the everyday work (fix bug or add feature) I do the changes in DB directly in phpmyadmin. I test everything in a mirror isntallation, copy the changes to the prod site and apply the mysql changes.
We only lauched 2-3 new major versions of the site (once every 2 years, more or less) and wait for a stable version of Prestashop, even 1.7 now has a few major bugs (Translations was one of them, not sure it's 100% fixed in 1.7.1).
The last one, that went quite well, we altered the theme to our needs, applied a bunch of new features for our customers, etc... When was time to launch I just analysed the difference in the relevant tables, and copied the data from the old db to the new one, with the added fields and changed defaults, etc... using ssh access as they were both on the same server.
Btw, the old tables we need were related to address, carrier, cart, category, customer, delivery, feature, group, image (but not image_type), manufacturer, orders, product, range, specific_price, stock_available, supplier, tax, tax_rule, wishlist, zone, country, state, employee, profile, and others used by our modules. Others like modules, configuration, hooks, etc, didn't matter because it was a complete new theme.
I always thought on doing something that could synchronize the db of the dev version and live one. But still haven't done due to the fact that we don't do that many major changes, and the minor ones, we try to keep the changes in a file until we apply it (not the most professional, I know). And sometimes, on these major version changes there could be new ways of Prestashop doing things. THe last i remember was the access slug in the 1.6.something, that was not in the 1.5, and after everything done, I could login to back office, but other workers couldn't, because it had changed how access was controlled, and since I was superadmin, I was not affected by it. Another thing in the of not doing it right now, it that Prestashop is starting to use Symfony, and I think will try to use it even more in the future, impacting how things are going to be done in the future. So a solution now could not work in the future.
We could also use the upgrade features in modules. Never tried it, but it could be used to apply upgrades to the DB and others automatically. Looks promising, but don't know if it works with a push or if only on module upgrade. One of these days i'm going to test this.
This is not a response with a solution, but I'm interested in one, and in working on one if there isn't any. It would be interesting to do a push, and not having to change things in db "by hand".
I had a question regarding Magento: -
Currently I have a client whose online site and catalog was being built on magento, however they are wanting to divide up their site to use a different platform for the catalog management and consumer purchasing experience, while keeping the rest of their corporate site intact on magento.
Since they were using enterprise before, the idea is to move to Community to use for their corporate site, however I'm wondering if this is feasible to do from a migration standpoint. Is there any way to port across their CMS pages (catalog isn't important) from their old enterprise version to a fresh community version, and have it remain intact?
Enterprise has lots of additional features in place. Also its URL table are modified. So you need to check if these features are used in design.If so you need to remove all those plus you might have to move some data or populate some tables.
Its possible to move back from enterprise to community.But is not a cake walk.
I'm working on a magento Enterprise edition store and I want to migrate it to Community Edition.
I'm new to magento, please help me with some steps that I can follow to migrate EE to CE.
Could you please provide some ideas?
In my mind there are two different approaches.
You can start fresh with a new community install and bring over your code and design modifications and then your data.
Or you can try to downgrade your installation by "upgrading" to the latest version of community.
The way to go would depend on what modifications or customizations are in place
Not all data can be moved as some of the tables and fields are not in community edition.
Steps suggested:
1. Install fresh magento community version.
2. Copy theme folder from ent site and paste in communiyt site.this will probably break at places and you will have to fill.
3. Magento has data import export system so use that to import products.
4. Similarly apply import export for customer(You might have to go with some 3rd party code for this).
5. Apply configuration via admin.
I am not sure whether you want to move order data too.This part is going to be complex.
See https://magento.stackexchange.com/questions/6706/how-to-migrate-from-enterprise-edition-to-community-edition
Yanted has written a fabulous guide to this - some of the EE features in >= 1.13 actually make upgrades a little more painful than the below writeup would lead you to believe. As Marius points out in the comments that all passwords will have to be reset as encryption methods are handled differently between EE/CE.
See the blog for more details.
http://blog.yanted.com/2014/02/21/downgrading-magento-enterprise-to-community/
Original post:
Migrating is actually very easy - point your CE codebase at your production database. There's little more to it than that (see below for some folder removal information).
If you're using a well-built EE-compatible theme it should be backward compatible.
Here are some little-known EE features you'll need to watch out for when downgrading to Community:
No access to Customer Attributes from Admin Panel
Customer segments will go away
Catalog events, private sales, Invitations etc. will go away
CMS hierarchies are not supported in CE
Banners are not supported in CE
RMA - people always seem to forget about RMA (information will be resident in db)
Admin Logging information will be inaccessible (still resident in db)
If you have a large portion of your CMS built in EE I recommend you take a very thorough and methodical approach and make sure that your new CE theme (or backwardly-compatible EE theme) support the data that is still resident.
I also suggest not dropping any tables from the db prefixed with enterprise - as well as not removing any enterprise folders from your 3rd party themes. These are not considered as part of the EE install and you should take them along with you when you leave. You will need to remove the files and folders from the following locations:
app/code/core/Enterprise
app/design/frontend/enterprise
app/design/adminhtml/default/default/layout/enterprise
app/design/adminhtml/default/default/template/enterprise
skin/adminhtml/default/enterprise
skin/frontend/enterprise
app/etc/modules/Enterprise_*.xml
js/enterprise
LICENSE_EE.txt
LICENSE_EE.html
And of course, you need to consider the real biggie: Full Page Cache. I highly recommend that you find a decent 3rd party Full Page cache.
Best of luck!
I will start a little project with a shopping cart. I will need to make several modifications in the shopping cart.
So my question is "Which is the best PHP open source Shopping Cart" to work with and easy to modify.
Give me some clues.
Best Regards,
Prestashop
Having worked with virtually all major open source e-commerce platforms, this is by far my favorite. It's not as powerful as Magento, but it's very easy to learn how it works, create/modify modules and design templates. There's also a very active community and it's developed by a company that releases it as OpenSource, so it's being constantly improved. The new flagship version 1.4 is almost out (it's at RC5 right now).
Other alternatives are:
Magento: It's built using the Zend Framework and it's heavily MVC. If you're familiar with the Zend Framework, this might be a good solution for you. It's a lot more difficult and has a much steeper learning curve than PrestaShop.
TomatoCart: This is a fork of osCommerce 3.0 beta. The creators have tried hard to improve the platform, but osCommerce has a lot of rotten design and it's a mess to extend. I've tried creating a couple of modules and had many problems. There isn't much documentation to help you and the community is not very active.
VirtueMart: If you are familiar with Joomla, this might be an option. If you're not, you should stay away because you might have a few problems setting everything up correctly and integrate this component with your template.
osCommerce: Just stay away from this...
Magento is an easy leader at the moment. It's got lot's of up-to-date features and an easy to modify architecture. The downside that I've seen mentioned in other forums is that it's more suitable for technically minded people so might not be good for a beginner.
Zen Cart
I've built a few (3 or 4ish) sites using zen cart. It's free, and it does waaaaaay more than anything I've ever needed it to do.
I've also used Squirrel cart. It's not free ($170), but it is easy to implement and has great support.
I have used both Magento and OpenCart and I can say that Magento wins hands down in terms of :
available extensions and modules
search engine optimization
wide store management possibilities including products’ comparison
wish lists and smart customer accounts.
Effective multiple store management is Magento considerable advantage.
Concerning Open Cart, it has some benefits in terms of easy installation, as it's quite lightweight in comparison to Magento.
If you are planning little business without rapid development in the near future, OpenCart will be quite enough for you.
Magento is really demanding in terms of hosting, investment, efforts, so it better suits large size stores.
Like said above OpenCart is lightweight and simple to use.. recommended more for small stores and beginners..
Magento is way ahead and has larger extensions than opencart. magento is more technical to use.
I am looking for a good eCommerce CMS.
I need to be able to sell services and products, it must be open source that it can be customised wherever needed.
I am very familiar with PHP and Mysql, and somewhat familiar with python and ruby, so a PHP solution would be preferred.
Some of the best PHP carts:
Magento - Full featured. Excellent code quality. Hard to learn. Requires lots of server resources.
PrestaShop - PrestaShop is currently used by 250,000 shops worldwide and is available in 60 different languages.
OpenCart - OpenCart comes with an inbuilt Affiliate system, where affiliates can promote specific products and get paid for this.
InterSpire - Not Free.
FoxyCart - Not Free. Hosted checkout that uses your templates. Works well with a CMS like Modx or Expression Engine.
LemonStand - Not Free.
I have two recommendations for you.
Dont use OSCommerce.
Dont use XTCommerce which is based on OSCommerce
To be more specific NEVER EVER use oscommerce for ANY project you want to extend at all. If you run the project 100% out-of-box and need some payment extension that nobody features consider it for two seconds but then better DONT. OSCommerce features code from 2001. OSCommerce has only one coding pattern which is FIXHACKCOPYQUICKPASTEHERENOW. Its the negation of everything you think to know from software development and project mangement. If you use OSCommerce and try to extend it your project will need twice as long and you will start hating webdevelopment. And yes i know it sounds like, but i am not kidding. Been there, done that.
If anybody tells you to use oscommerce - e.g. for all the existing extentions that are out there - stand up and leave the room.
Extra Tipps:
Magento IS SLOW.
http://www.prestashop.com/ - In the OSS world Prestashop has some popularity.
http://www.interspire.com/shoppingcart/ has some reputation but is not OSS.
I know you want to stick with Linux based but nopCommerce is amazing:
http://www.nopcommerce.com/
http://demo.nopcommerce.com/
For free you can't beat this.
Try Magento
Have you checked
http://www.oscommerce.com/
It was discussed here also:
https://stackoverflow.com/questions/143656/whats-the-best-free-and-opensource-php-ecommerce-solution-and-why
Regards
oscommerce- basically many features that you want, they have it. Only thing is it is in plugin format, you need to go to their forum to find the plugin to install.
I would recommend below:
interspire shopping cart- one of the most user friendly cart. Not free, but quality is there. I personally love this a lot.
Magento- is the open source software. Very good quality and functionality. BUT BUT BUT, eat up lot of server memory. If you want to go for this, start from semi dedicated server is your choice.