When would I use profiles in my web app?
To quote Scott Allen:
A good web site will remember me.
Perhaps the site will remember my
favorite color scheme, or my preferred
shipping address. Either way, if a
site makes me feel like I’m not just
another IP address on the web, I’m
more likely to return in the future.
Adding a personal touch for your
end-users can make a difference.
Use Profiles to enhance the experience of your website, read more about ASP.NET Profile Properties on MSDN.
Related
I want to change a website from wordpress to wix. The challenge is that- If I connected the existing domain directly to wix, will I lose my mailbox?
Please suggest how to connect mailbox to wix without losing it?
It's a bit of a strange question.
Wix is indeed a SaaS, providing hosting, a domain, ... which means that in order to use Wix, you either develop your platform within their SaaS environment OR you use their SaaS environment to provide services to an external platform.
I see only one option to adhere to the requirements you shared. If you want to keep the current host, but you want to use Wix, you'll have to provide services from Wix to your external website.
For the moment, this sounds more like an architectural question, so you might want to be more explicit.
I am building a web consisting of MediaWiki and phpBB as its subcomponents. Also WordPress may be added in future. My current problem is to choose a single unified authentication method (not to force users to have a special MediaWiki account, a special phpBB account, etc.).
Which approach would you recommend me? The basic limitation is that it is a simple LAMP server (no LDAP database). Possibilities I know about:
Use a decentralized protocol such as OpenID, OAuth 2.0, etc. I would prefer this approach. However, OpenID is not supported by Google any more so OAuth 2.0 would be probably more appropriate.
Use DB of users from phpBB and install some plugin to other subcomponents (MediaWiki extension for phpBB auth.)
Use DB of users from MediaWiki and install some plugin to phpBB.
Use some specialized web application for user credentials management and install plugins both to MediaWiki and phpBB.
I think the main point you already understand: You need one of your new platforms to be the central user store. The problem you know have to find out:
What platform has the plugins to interact with each other? It's possible, that you find plugins, that only works "in one direction", and for mediawiki itself you will find a log of outdated extensions, that maybe won't work anymore with the latest mediawiki versions and updates.
The other point is, that you should think about WordPress now, too. After you selected one central user store you mostly can't change it with a lot of work, so I would check for an integration of WordPress now, too.
Looking at that and a short search i wouldn't prefer MediaWiki to be the central user storage, and i'm not sure, if phpBB is the best solution, too :/
I think one of the best would be to use LDAP, extensions and plugins seems to be supported and working for the latest versions of each software. You yould have a central user store, which could be easily integrated in other applications, too. What is the reason you can't use it, an LAMP stack could handle this, too?
The second solution i would consider to choose is to use Google's user store and access it vi OAuth 2.0. MediaWiki, phpBB and WordPress supports this with plugins and/or extensions.
At the end of the day a login is a login is a login. All the custom fields specific to individual applications can be properly bridged with plug-ins. Make the app that will require the most babysitting your main database and thus login system. In many cases it's the forum, but that really varies by site.
I would caution that many new forum admins eventually want to upgrade from phpBB to something that's more powerful and modern. I was one of those admins. Yes, phpBB is as good as an open-source forum gets, but it just doesn't compete with the commercial forum apps. So keep that in mind if you make phpBB your main database.
I'm not entirely sure how to properly ask this, so please bear with me.
I have an idea for a site I would like to build, which would basically be a site for members to create some data and have it housed in my database. I would like to offer a value-add to the site which would allow people to spin off their own website via my own "website builder" tool (probably some sort of CMS). Their website would be able to communicate with my master database to display their data.
Getting down to the crux of the topic, I'm looking for architectural advice/ideas/etc. regarding what services I could use to do this. I'm not looking a 100% automated solution, but something along these lines (which may not be completely correct, I admit):
Customer puts in an order to create their own site, using my tools.
I setup a separate domain for them, roll out the CMS foundation to the site, and the customer has full editing control of the CMS to design it however they would like.
The CMS would have some customizations so that it includes functionality to call APIs located on the master site, which would return the relevant data.
In the research I have done on SO, I've seen a lot of mentions of Umbraco which honestly looks like a good start. I'm just worried that when I go to upgrade a version, I have to deal with overwriting my custom API functionality. I'm guessing this is the nature of the beast, and requires me to accept/plan for it.
Does anyone have any thoughts about this? Some high-level starting points? Thanks!
I've been thinking about this same issue for my customers.
It is not hard to automatically roll out a stock cms such as Wordpress or Joomla. This sort of thing is done all the time by "1 click installers" that DreamHost and others have.
Including custom widgets or plugins for the CMS that can connect to your main app is also not hard.
For dns, you can use Amazon Route 53 or other DNS services that include a good api at the dns management level.
I suggest that you focus on using a CMS that is very popular (eg Wordpress or Joomla) rather than something less well known such as Umbraco. Using a more popular system will drastically reduce your training costs--remember that if you supply the CMS to your customers, then they'll also expect you to supply the support for it...
I need a intranet portal for a Repair factory in which 100 Technician worked.
The main purpose of this portal is "sharing technical information (like technical bulletins etc)".
I also create a simple website/portal with HTML,Javascript. Which is running sucessfully.
But Now we need a Blog like site in which Technician can share own experience/knowledge with other. for this requirement i tried with Joomla,wordpress, drupal etc.
firstly suggest me which platform is best? i have beginning knowledge of PHP, JavaScript and JQuery.
requirement:
Technician can post a article within one or more defined categaries.(like model,level of information,Electrical or mechnical etc.)
After submitting articles, it sent to the Technical Specialist or Technical Editor for approval.
after approved it is published to Blog with ranting,commenting option.
Which theme,plug-in is suitable?
Take a look at Plone (http://plone.org/), I think it fits perfectly for your needs.
Plone lets non-technical people create
and maintain information for a public
website or an intranet using only a
web browser. Plone is easy to
understand and use — allowing users to
be productive in just half an
hour — yet offers a wealth of
community-developed add-ons and
extensibility to keep meeting your
needs for years to come. "
For those looking these days and who want / need WordPress you can use Woffice (https://woffice.io/) or Thrive. Both have all these features.
Our shop is primarily .NET but because of the lack of any really good popular .NET CMS products, we have chosen to use WordPress (and Drupal at times) for our public facing sites.
I realize this is highly subjective, but it is the conclusion we came to for our purposes. One could certainly make a case for DotNetNuke and others, but that is another conversation.
I would like to know if I can integrate small components into WordPress sites, primarily to do simple forms (logon, lost password, contact us, change user settings, etc...)
Can I do this with an iFrame or another method that I am not thinking about?
The only simple way to do this is to make <iframe> tags pointing to ASPX files.
Even if you could, I wouldn't recommend it. Since you are talking about forms, could you not just write php or javascript that communicates with the .net files? I'm not to sure about how Web development in .net works.