I need some help/suggestion on how I can export a user from our "development" site to our "live" site. Basically we have two different environment as normal but one of the user has been testing on the "development" server and would like all his data moved over to the "live".
The problem is we can't move everything but not the user and his data themselves. Any help/suggestions will be much appreciated.
This is not easy to do. To answer fully, what do you mean by the "data" of the user, do you mean role settings, etc. or do you mean the nodes and other items he has been working on?
If you mean the role settings, it is easiest to just manually recreate the user in the new context. If you want nodes, look at https://www.drupal.org/project/node_export. For other types of items, views, etc., there are similar modules which will export those items.
Related
I am working on a project where my client has no idea about joomla admin panel.
So I have decided to provide a separate admin pannel which my client can access and manage few things.
I am also having multiple pages and sub-pages in this admin panel.
Lets say I want to give multiple manage links.
manage item
sub-menu
manage item 2
I am little confuse how do I do it, once I thought about component and moduel but I don't know how to add menu links in components for front end.
I am using joomla 3.0.
Many thanks in advance.
If your intention is creating a backend alternative to joomla to control joomla's frontend, this is a hard thing to do if you are just a e-commerce website developer.
But if you need a different account other than your administrator account, you can add one account and edit it's privileges.
A second admin panel for easier use? sorry that sounds not good. Just do it like serhat above said. make a new account for joomla admin-panel. cut of the privileges so the user see only the things he has access to! its better then coding a fully new admin panel. there is already a fully configurable panel so why do another one?
Give the users just what they have to see and hide the rest (via admin-privileges)
I am currently working out an admin interface with a Live Preview and I am still not 100% on how to structure it properly.
My page basically consists out of two parts. The Admin Interface and the Live Preview. Obviously, the Admin Interface fills some variables with data and the Live Preview displays this.
Therefore, the Admin Interface needs to bind variables, that the Live Preview will bind for reading.
Furthermore, the Live Preview in the end (if possible) should be re-used as the final product that displays a set of information. All it does is display a single JSON file that is received from the server (when in product mode) and in case of the Live Preview it will need to update the data Live as its edited.
One more note: Both, the Live Preview and the Admin Interface consist of elements like directives again and parts of the Admin Interface need to be loaded dynamically by having a user add a page with a certain type of content.
After researching how modules are handled I came up with the following:
Live Preview is a Module
Admin Interface is a Module
My page includes both modules
Both of them should be connected to something central that provides the ability of editing the data (bound variables?) and reading the data so its updated live.
Ideally, this would be a service, so later on when loading the "Live Preview" as an actual product, can just use the same kind of service which in this case provides the information from our Database instead of a variable in its scope.
Is this a good approach? Is there a way to have a service that on the one hand side can be edited lively like in a two way binding so that my live preview can also pick it up? Is there something I can use instead of the services, like a controller? How should I go on about this?
You are doing everything right. I don't think that it is relevant as to whether the preview and admin panel are their own modules or contained within one. You will find people using module seperation in a wide variety of ways within their Angular apps.
What I think you said that is important and correct is to connect the preview and admin panel via a Service. Other methods of connecting these two (i.e. $rootScope) are costly and bad practice.
If you will be re-using live preview in many locations of your application I would wrap it in a directive.
You should feel confident in your approach, it's a good one.
I have a winforms app and want to customize for differents clients, I need a simple mechanism to create a version for client1 with one commandline app for example. I only want to change the color of the window and of buttons and a smart logo. I dont want to change it manually every time I need a client1 version.
Maybe you can put in your app.config some configuration tags, some properties you need. And then let's say, through your setup process, you modify the configuration based on client desires( that's if I understood correctly.
I don't know what kind of app you have but I had an app that is accessible for 3 different types of users which are admin, receptionist and patient. I used password authentication and inside the forms, I used simple if/else clauses according to authentication types to arrange which user could use which parts of the app. But as far as I understand you need something like an interface in case any other client takes part in the app later.
Total DNN noob. I can code some WebForms and MVC, but having no luck finding anything concrete out there about doing what I want in DNN
How would I go about setting up a client portal in DNN? I want to have separate areas for the client, including a main dashboard that aggregates content for the client from the other areas. The other areas would include a matter area (with matter information - some auto generated for client, other information to be input by client), a documents area, an events area, a tasks area, a communications area (for chat, or forum style questions) and a profile area for the client (contact info, invoicing, etc.).
What I'd like is for a client to login and see only their items. An admin would log in and get the same "screens" or "areas", but with aggregated content for ALL users.
I know that's a lot, but I would imagine setting me up with a way to do the overall app and then how to create the areas to navigate to would get me going. I know there are modules for each of those things out there, but a) I wouldn't know how to integrate this into one client app and b) some are cost prohibitive.
Most of what I find focuses on setting up one module. Do I go that route and set up user controls within for the different areas? Or do I create separate little modules and tie them together? This is primarily where I am stuck. I can create something like this with standalone web forms or MVC. Hooking into DNN is where I get stuck.
I appreciate any guidance / samples.
There are a LOT of questions here and many ways that you can go about doing this. You could use third-party modules to handle this but you will need to figure out exactly which ones give you the functionality that you want.
If you are looking to do things custom, this is where it gets a lot easier. DNN for users can manage user identity and roles. Based on what you are saying it seems like you would have some custom modules that store all information based on UserId. By default you only display the information for the current user. However, if the user is in a specific role, say for example "Administrators" you would display all content.
This is pretty easy as with any DNN control that inherits from PortalModuleBase you have the UserId available to you as a property. Then you can use UserInfo.IsInRole("Administrators") to check for admins.
To resolve this problem on my own, I started out by installing Profile2 and Profile2 registration. At no point was I able to generate a page based on the user name (eg, {domain}/private/register). I figured it was not coming up b/c I checked off that anonymous users could not see published pages (which is a site requirement). However, I might have done something wrong but I went over the instructions several time and I don't think I made a mistake. Any suggestions would be helpful.
I think you may have to create a new content type, similar to the normal story or article types, and publish restricted content as the new page type. Apply the access restriction to this content type, and leave the default content types alone.