I've been developing a Wordpress site for the last few months with the aim to make it a e-commerce website. I recently came across Magento and realised It is an extremely powerful e-commerce framework.
I was wondering whether anyone has any advice for Wordpress and Magento integration. Is it better to have Magento at the root as the CMS and use Wordpress for the blogging aspect, or is it just as feasible the other way around?
I was also wondering if it's worth me just creating a Magento theme based around my current Wordpress theme instead?
I think the latter is the best option here. I use Magento for an Ecommerce platform and Wordpress for the associated blog. Each has their strengths and weaknesses. Play to the strongest part of each and use Magento separately from Wordpress. Believe it or not, you'll save time even though you are using both platforms independently. Plus, Wordpress has been known to have minor to major security issues in the past. Plus, I wouldn't put the engine that's going to be providing me with a paycheck in a position that it was never intended to handle --> ecommerce.
Related
I have been reviewing about WordPress Flynt Theme a week ago.
I am going to develop a complex wordpress site by using Flynt. But I am not sure that Flynt will work without any doubt and has any conflict with famous Wordpress Plugins such as SEO plugins.
I'm one of the core contributors of Flynt. We are using Flynt for all our custom designed WordPress projects ourselves, may it be rather straight forward websites, or more complex ones.
As a general rule, we try to avoid using too many plugins in our projects to avoid compatibility and security issues. We're also making limited use of WYSIWYGs and shortcodes, but rely on custom fields with ACF Pro instead. Everything revolves around custom built components.
We're of course using popular plugins like Yoast SEO, Contact Form 7, and WP Super Cache. But Yoast will require ACF Content Analysis for Yoast SEO as a plugin for the backend to make things work. This will be similar for other plugins which are scanning the_content() to add functionality, as the component architecture is independent from the_content().
I'm sure Flynt will work like a charm for you if you love custom development, but you might run into issues if you're heavily relying on plugins to add frontend functionality.
does anyone know what building a WordPress commercial website actually means? Does it involve just learning PHP or other programming langs? Tried looking online, but couldn't find an answer.
WordPress is a blogging platform available under a license which allows reuse. Anyone can download the WordPress source code and use it to make a website. This may be a commercial website.
WordPress allows plugins. Many plugins are available under the same licence as WordPress itself, or similar licenses. Others can be purchased. Or you can write your own or pay someone to write them for you. These plugins can radically change the behaviour of a WordPress site. You can build all kinds of complex applications on top of WordPress.
Whether this is a good idea is another question. In my opinion, WordPress is a decent blogging platform, and the well known shop plugins are well tested and probably reasonably well behaved, but using it as a basis for bespoke complex applications is a bad idea. It certainly can be done, but the data structure tends to be weird. I speak as someone who has rebuilt from scratch a couple of applications originally based on WordPress, and both times wasted hours of my life trying to make sense of the database.
As per my opinion wordpress is not suitable for enterprise level applications, because due to lot of data it will get slow your site.
However if someone want to built commercial website on wordpress but on smaller scope, yes he/she can build on wordpress.
Building a commercial website on wordpress requires php basic knowledge and wordpress theme hiearchy and tags knowledge.
You do not need any high skill knowledge to build your commercial website.
Yes its involved learning of different fields like html, css, javascript or jquery, php, mysql.
But it depends on requirement.
If you have purchased a ready made theme and require only small changes then it will require frontend skills like html, css, jquery.
And if its need heavy customization then it will require backend skills like php or wordpress loop structure and theme structure.
My question relates to this post here (Fishpig's Wordpress):
Full Magento / Wordpress integration
I've installed this plugin and almost everything is working well. I've been trying to run wordpress plugins within the blog, but these were not showing up. No issues on the installation process.
Are there any further steps I have to take or is it generally not possible?
It's generally not possible is the short answer to that I'm afraid. In full integration mode your Wordpress themes and plugins will not function as they normally do as the whole thing is running through Magento.
All in One SEO will work, support for it has been added to the Magento module. Fishpig has produced a couple of additional Magento modules which can be installed and will support additional Wordpress plugins. Indeed, this is a way for them to monetise the work that's gone into it all, so I am hoping there will be more on the way. I've got the Next Gen plugin which works well, I can recommend that. There's also a Pinterest plugin and Advanced Custom Fields;
http://fishpig.co.uk/wordpress-integration-pinterest-rss-widget.html
http://fishpig.co.uk/wordpress-integration-advanced-custom-fields.html
http://fishpig.co.uk/wordpress-integration-nextgen-gallery.html
To have a fully functional Wordpress site you will have to set it to semi integration mode and do a matching Wordpress theme I'm afraid.
i have created a website for a non profit organization. People on the site want to post stuff . i want to figure out the best way to allow them to do this.
Can i host a wordpress site and somehow embed it into my website
Do i need to install some whole CMS solution?
Other solutions for supporting user driven posts.
to clarify, the functionality of wordpress is all i need (people posting content and pictures).
It's easy to integrate Wordpress into a static html site.
Integrating WordPress with Your Website « WordPress Codex. (You do need mysql, but almost every hosting company out there offers it.)
If you want to convert an existing html site to Wordpress, look at Theme Development « WordPress Codex. Developing Wordpress themes is no more complex than other CMS's, and here are lots of tutorials out there. You divide up your html into header.php, index.php, page.php, footer.php, etc., and css into style.css. If you do a standard Wordpress theme, then plugins will work fine.
Go ahead and do a full install of Wordpress; there's no option for a minimum install. WP is small, anyway.
If you need a finer degree of working with editors, subscribers and contributors than Wordpress offers out of the box, look at different plugins that offer role managing capability, giving administrators the power to give different levels of permissions to users to write, edit and publish. WordPress › Search for roles « WordPress Plugins
You can pull other content into Wordpress via RSS, too, and either have that content appear as an RSS feed, or have it integrated into published posts. FeedWordPress | simple and flexible Atom/RSS syndication for WordPress
You can get a free account at wordpress.com and try out a limited version of Wordpress, limited in that it is hosted by wordpress.com and you have a small number of plugins and css modifications you can make. But once you selfhost Wordpress, then you can do much more with it in terms of plugins and adapting the css to an existing site.
You could use a Wiki.
There are a few popular free Wiki packages out there these days. By far the most popular would be the framework behind Wikipedia - MediaWiki. Wikis' are a proven way to let users create the content, with systems in place to prevent vandalism/spam. MediaWiki also has a whole bunch of great plug-ins for anything you would need.
Another Wiki option is to use the Wordpress-Wiki plug-in for Wordpress. It lets you use Wordpress, but with some features of a Wiki. Not as feature rich as MediaWiki, but a good option if you really like Wordpress.
You do not need to install a whole cms solution, though wordpress can host an entire site, not just blogs.
You could hack it by using a hosted weordpress and displaying it in an iframe (this one might get some flames - but it works and it's easy)
You could also install wordpress on your server. By the sounds of it this is not your expertise, and while setting up wordpress is getting easier every release, for smaller sites I would much rather recommend pivotx
wordpress has a lot of overhead and requires a mysql database. The templated, while there are more available than in pivotx are harder to create. So I'm suggesting the other solution because it does the bulk of what wordpress does, and though it has far far far fewer plugins, it is a lot easier to theme, as it uses smarty.
This problem/scenario is pretty common. And the most common solution is to install a CMS. Our compagny installs Drupal to let end user manage their website easily. They can edit menus, and change content as easily as you write a document in word processor software.
But there is a lot of CMS out there...
Have you tried blogEngine.net?
I have two sites http://www.dotnetscraps.com and http://www.abhyast.com/ that are hosted using blogEngine.net. It is free and has multi user support, and the best part for me is that it supports both XML and SQL hosting. Anything that you post automatically ends up in the App_Data folder which is what you need to backup.
http://www.dotnetblogengine.net/
There are a plenty of themes to choose from, and if you wish you can customize your own theme without much effort.
I work at a more traditional ad agency and I am the sole web guy here. Recently a designer here redesigned our website based on the popular blog style seen about on the internets at the moment. Design is similar to this blog: http://effektiveblog.com/
I put forward that this would be a WordPress job, due to the designed features (tag cloud, dated/categorized posts, ability to be updated, rss, etc)
However, the non-web people at my workplace are saying they don't want to "do WordPress" and are planning on out-sourcing a custom CMS for this blog-look-a-like site!
As you can imagine, this is very frustrating and back-to-front.
However, as I haven't really delved fully into WordPress enough I don't fully know what arguments to put forward in regards to advantages/disadvantages in building it with WordPress vs a custom CMS.
Any thoughts on what to suggest to non-web superiors? or links even pointing to similar discussions?
I've been in the WordPress world for a few years and my observations have been that most of the "WordPress vs. other CMS" arguments boil down to a couple things:
Ultimately, you could use WordPress for nearly any CMS task, and you could use a general CMS to build blog content
WordPress was designed primarily as a blogging platform, so that's where it really shines. Yes, it can be used for other CMS tasks, but it does blogging best and that's where you'll find the most support and robust features.
More general CMS systems will offer features designed for a variety of content (not just blog posts or static pages), but they won't offer as many features (or as easy of an experience) for the blogging component as WordPress will.
Generally I tell folks that if the focus of the site is frequently updated content that is managed in a chronological fashion (like a blog), go with WordPress. If they're looking to integrate a bunch of disparate content and blogging isn't really important, they'll probably be better served by a more general CMS.
Wordpress is great for blogs and mid size simple websites. It's "static pages" approach is really useful, because you can create hirarchies that are fully editable from admin panel. It's plugin ecosystem is very good also - from SEO to automatic backups.
When I needed to convince some people that Wordpress would be a good idea to a CMS solution (not just a blog one), I created a prototype, and said that I just needed to edit a few php files (all copied from the default template), a few administration tasks and a few plugins and I was all set.
This prototype was really simple: no design, just structure. I made it in a saturday afternoon, and I made a challenge to everyone involved if they could create the same structure I created, with a full admin interface, in less time. No one could. And it's a tested plataform, yes, it's not "all MVC based", but it works and its administration is great to use.
I don't know if you have time to do it, but since is really fast to do it, I'd rather show them instead of just saying it.
One disadvantage of Wordpress is its performance. You may need to look at some cache plugins for your installation, like WpSuperCache. And be warned that if your website, in a long run, is going to have a lot of different requirements, Wordpress may not be the ideal solution.
WordPress is definitely the world's most popular CMS. The script is in its roots more of a blog than a typical CMS. For a while now it's been modernized and it got thousands of plugins, what made it more CMS-like.
Advantages -
Easy to operate-
WordPress does not require PHP nor HTML knowledge unlinke Drupal, Joomla or Typo3. A preinstalled plugin and template function allows them to be installed very easily. All you need to do is to choose a plugin or a template and click on it to install.
It's good choice for beginners.
Community-
To have a useful support, there must be a large community of users, who will be a part of e.g. a discussion board.
Plugins-
The script has over dozen thousand of plugins available on its website. They are the reason WordPress is considered a CMS, not only a blogging script. Strong majority of the plugins is available for free.
Templates-
On the scritp's homepage you can view thousands of graphics templates, that can change your website's look. You can find there both free and paid templates. The paid ones are often more advanced as well as more interesting.
Menu management-
WordPress menu management has extended functionalities, that can be modified to include categories, pages, etc.
E-commerce is available on WordPress
At Designed to Connect, we generally use Woocommerce – an e-commerce add on to WordPress to build our e-commerce websites. As an e-commerce store, you will often find yourself updating your products, pricing, sales, coupons and more. Woocommerce is extremely effective in doing all this along with offering great reports features.
Disadvantages -
WordPress updates their software frequently-
WordPress is constantly changing and growing and it needs regular updates. This is not a big deal unless you are looking for a set-it-and-forget-it solution, in which case this might not be the solution for you as it needs periodic updates.
Customization of a theme can be costly-
If the website was built upon a theme and you decide that you want to make major changes to it, it may be time-consuming to have a programmer make changes to the layout of the theme. If you anticipate needing to make major changes to the theme, consider having a theme built from scratch to meet your needs instead.
Advantages:
Low cost to upkeep / maintain website is cheap
Easy and good with usability on back-end
Tons of plugins (which can slow your site down significantly)
Write your own functions if you know PHP.
codex.wordpress.org, the documentation is so easy
Tons of updates for security
The community, the millions of users
SEO possibilities (when compared to other famous CMS)
Can make a big corporate to small website
Disadvantages:
Not the the most optimum use of its resources (but its getting better every update)
Security (also improving)
Advantages:
Simple
Huge number of themes and plugins
SEO
Easily convert site to Ecommerce
Disadvantages
Customization
Source: Advantages and disadvantages of wordpress