As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Our customer wants to migrate from DotNetNuke to another open source .NET CMS. I'm looking for something that will have the same advantages as DNN+Dynamic Forms/Registrations - ie. possibility to create complex surveys with events (showing one field based on response from another, auto-submit if specific answer occurs, events on survey submit like SQL query execution, HTTP POST or e-mail sending).
Right now there are thousands (around 50-100k) active users (each user logs in and has her/his personal data stored in DNN surveys), so this CMS should be capable of creating rather big solutions.
What are the options? Should we stick to DNN considering migration to a newer version? Are newer DNN versions worth the rework (we're currently running on 4.9.5). Are there any open source and free .NET CMS-es that are comparable to DNN in terms of survey creation, and are better option when we think of usability, performance, stability, etc. - basically all the fields where DNN more or less fails? We were thinking of trying out Umbraco - does it have a good survey module?
Any suggestions will be much appreciated.
Personally since you have such a platform already built on DNN I would strongly recommend looking at ways to upgrade your current system and stay with it. It will be very hard to find something else that will fit the bill most likely and the migration path will most likely not be smooth.
DNN upgrades can be a bit tedious, but they are not impossible as well as performance and stability are even better with the current versions. Usability is greatly improved with teh 6.x line as well.
Umbraco has a very nice form builder (http://umbraco.com/products/more-add-ons/contour.aspx) but you have to pay a tiny bit for it - I believe it's 99EUR.
We use it for quite simple surveys/contact us pages etc.
Out of the box it does allow for multi-page surveys (though I've never tried this) but it does not allow conditional questions.
That said it is very simple for users to set up new forms and surveys so I guess it depends how complex your surveys get.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am about to develop website using YII framework. But i am not quite sure about which database i should use.
Generally insertion and selection would be there in a website. Data would be come from different relational tables as i will have more than 50 filters so that user can see what ever database they want to see.
Here is the example of website. http://property.sulekha.com/
I want to design something like this.
which new concept i can use for the optimization, for better performance.
I have few concept in my mind which i am supposing to use.
1) MemCache
2) HipHop PHP
3) Doctorin ORM
I am just wondering how facebook search is working, are they using any advance tool for search??????
Facebook architecture is a fascinating one, and you shouldn't try to copy it, because you don't need it, and as we all know, premature optimization is the devil.
scaling issues are not something you prepare for, unless you're working for an enterprise and know first hand that you'll recieve huge amounts of traffic from day 1, like the new mega.
if you're talking about a large de-normalized table, which sounds so by applying up-to 50 filters, maybe you should consider a NoSQL solution, like mongoDB.
from what I know about facebook search, is that the servers are clustered, and are basically pointers to the "real" data, which means that alot of their data isn't a physical one, but as I said, unless you plan on sporting 1 billion users - that's over your head as of now.
good luck
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am exploring CMS tools Alfresco and Liferay, but cant decide which is better for Web Content Management.
Please help me decide which tool to use for web. Opinions and suggestions are welcome.
Just use your favourite search machine and voila I've got topics covering this question:
e.g. here
If you can't decide, go for the pragmatic solution and just pick one.
You'll have to decide if you rather like the Content- or the Portal-centric approach - e.g. what else other than CMS do you expect from the solution you choose. As you ask for opinions: I'm tending to prefer a portal (but then, I'll have to disclaim that I work for Liferay) because it can integrate quite a lot more functionality - and extension is done through a well known standard interface (portlets). And I'm typically seeing requirements that ask for more than just content management.
Integration of both products is possible, but it's an additional effort that needs to be done - and you'll have to understand both. There are many people doing that, but if one solution goes 95% of what you need, you could save yourself the integration work.
But if you really want some useful answers here you might want to give more information about what you actually want to use them for, because personal opinions and suggestions might not help you with your personal requirements if you leave them unknown.
This blog post should be helpful enough as to WCM in Liferay. Talking about WCM (not Document/Enterprise content management) I would go with Liferay, because it is really easy and quite powerful, especially recently after a few new features were introduced (very cool web content staging and versioning). Alfresco is good for enterprise content management, but I wouldn't choose it for WCM, the Spring Surf and Spring Web Scripts it is using was quite hard to get used to.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I have come across a fair bit of information on CI being a really flexible framework. Does Yii also allow great flexibility? And the ability to pick and choose when to use it or your own php?
Flexibility is very subjective, so this question is a bit vague.
From my experience I can tell you that Yii is very very powerful, but in most cases when you want to go into really advanced territory you have to do things "Yii's way". If you do, you will find that the pieces of the puzzle click together really well and things go smoothly. If you don't (because presumably you haven't realized yet what "Yii's way" is), it's going to give you a hard time.
I am using YII since 2 years. I use it with combination with Zend AMF and create backend systems for Flash campaigns, create HTML5 webpages, simple pages, different competition pages and and find it usable for every case you need. The main advantage that it is really structured, logical and fast. So because of that I am spending my time on creating application logic, not on setting up environment, setting up all requests, pages, subpages etc., MVC model + ActiveRecord saves my time here.
I have been using Yii for a year now and find it very flexible. You can add your own methods to any model or write components outside models. You need to be familiar with the MVC structure, Object-oriented programming and for writing components, you need to know how to register the component in the config file and how to call it the Yii way.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am looking for some comments on Magnolia CMS.
Is there anybody out there having experience on Magnolia and willing to tell about?
I am interested in comments like usability, how fast to start with, potential problems, advantages, disadvantages (in comparison to other open source CMS).
E.g. I could not find out if Magnolia is able to use MySQL data or not.
Reason for my question is we need to build a community platform offering content, wiki, blog, news and user message exchange and all that stuff.
I have some experience on Joomla but not on Magnolia.
Any hints, comments, critics, warnings, recommendations are welcome!
Thank you very much!
Alex
BTW: I already found http://cmsmatrix.org/ which is a good starting point to identify features.
From a Java programmer's point of view, Magnolia CMS has a lot going for it. It has a pretty clean, easily extensible architecture. Lots of hooks to plug-in your own functionality, should you desire to do so.
Also, with the "blossom" module it allows for easy Spring MVC integration.
There might be other systems that provide an easier start, have more 3rd-party-modules or a bigger community. But if you are a Java developer looking for a solid base from which to implement you own custom stuff, you should definitely consider Magnolia.
Magnolia has some high server demands, steep learning curve and poor/limited documentation - you won't find many/any 3rd party books either. However, if you persevere with it you can create pretty much anything. It will work with a MySQL DB but you lose a lot of the main benefits of the system if you do not use the JCR DB.
You might want to ask this question on the Magnolia user-list where those that work on Magnolia projects will see it.
And yes, Magnolia is able to use pretty much any database as its persistence layer.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
What is the difference between custom building a CMS website and an open source CMS?
If you build the CMS yourself you have the great opportunity of going through all the problems and bugs that have already been encountered and fixed by the people the build open source CMS before. ;-)
Seriously, in my opinion, building your own CMS only makes sense if there is no open source CMS that you can customize to fit your needs. I think that you will have less trouble (and it will take less time) customizing some existing CMS.
Depends on what you need, how much time you have and how much coding experience you have. For example you could go and write your CMS, add only the functionality you need and keep it rather simple. But you'll have to debug it, take care of many issues like character encoding, security and you'll have to write even simple functionalities like an internal search engine. If you use something like Joomla, Wordpress or Drupal (just to mention the most popular ones), you'll have very well tested environments that have been patched for many security issues. You'll find hundreds of extensions like photo galleries, search engines, multiple language support. The drawback is that if you want to add something particular you have to spend time learning their API... but probably that would require less that coding something on your own... or may not. It's all about the complexity of what you need. You should try taking a look at one CMS API, I suggest a popular one so that you'll find plenty of examples on Google, then try to figure out how difficult it can be to learn and finally make your decision.