It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 10 years ago.
I have one doubt !
User group
|— Manager
|—|— Administrator
Manager is the parent,Administrator is the child..right ?
But the administrator have permission for to edit the Manager profile ? how its possible ?
Any one please explain me
Not quite. Think of it more in relation to inherited permissions rather than a parent-child relationship.
The reason it is shown like that is that Administrator, by default, inherits all of the permissions that the manager has + has some extra. So Administrator has more permissions that the manager does.
Attached is a sample of the default permission setup.
OK, so answering comment relating to permissions for your component. To set the permissions for a specific component (rather than global permissions) one would go to the components menu, select the component and set the permissions in there. e.g. see the attached image for Joomla's built in Banner Manager, under Components | Banners, click on the Options icon and then on the Permissions tab. See the default here.
The Manager has access to lots of functionality here, but you can change the dropdowns from Inherited and Allowed to Disable to stop managers from being able to do anything in this component. Likewise you could give more access to other user groups, etc. So, for example, if you only want Super admins to be able to access the component, just set manager and administrator to "Denied" and set super-users to Allowed.
Related
This is related to the language of a website like FB, amazon, booking, etc.
When you open one of this sites, or when you click on the search and goes to the site, it opens with a language by default.
There is custom dimension (Cd-session- diatect, or something like that) that is the langueage of the site, but is the last one you had in your session. Would anyone know what is the custom dimensions in Google analytics to filter by this "first visit"? I heard there is something to filter by the first time you visit the site but I cannot find it.
Thanks,
A custom dimension, by definition, does not exist by default. So you should create a custom dimension like the one you are already looking at but with hit scope instead of session.
In this way you can see which language of the site was active on the landing page, which is the first page of each session.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 9 years ago.
How do I set up Angular to send the correct headers when making Cross Domain Ajax Requests?
What worked for me:
After about a full day of trying to find an answer to configuring my Angular application to work with CORS, I finally came up with a solution that works! Assuming you have set up the server correctly - the only thing you need to do on the client is delete the default header in your app config.
angular.module('myApp').config(['$httpProvider', function($httpProvider) {
delete $httpProvider.defaults.headers.common['X-Requested-With'];
});
The X-Requested-With header identifies the request as an AJAX request - and by default cross domain is not allowed. So all we need to do is remove it from our default settings and BOOM! It works.
For our application we are using a play backend(1.2.5) - The line of code we needed to add to make that work was:
Add headers to allow cross-domain requests. Be careful, a lot of browsers don't support these features and will ignore the headers. Refer to the browsers' documentation to know what versions support them.
Parameters:
allowOrigin a comma separated list of domains allowed to perform the x-domain call, or "" for all.
allowMethods a comma separated list of HTTP methods allowed, or null for all.
allowCredentials Let the browser send the cookies when doing a x-domain request. Only respected by the browser if allowOrigin != ""
Http.Response.current().accessControl("*", "GET,PUT,POST,DELETE,OPTIONS",false);
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 11 years ago.
I'm wondering if anyone's given the new api introduced with rails yet? I began a mock app through facebook and heroku and it actually generates the beginnings of a sinatra based project. Has anyone crossed over to rails by chance?
I'm actually working on an app using the new OpenGraph & Rails. With the koala gem, it's pretty easy for example to post an action on the timeline of an user, you just need to do a
res = api.put_connections(current_user.fbid, "namespace:verb", myobject: "link_to_my_object" )
And you will get the action's id in response if all it's fine.
I did the mock app too, and it works fine for the app (stuffed cookies). I need to understand the javascript a bit more to move it over.
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.
Closed 13 years ago.
I’m planning on using Ajax with my web application, but as I’m novice and don’t have much experience I wonder when ajax should and when should not be used? I plan to code with jQuery/php if it makes any difference.
AJAX is most useful when your application wants to present a data set to its user in many different ways. Sorting and filtering and in general interacting with a data set feels best when there are no delays waiting for a server to redraw the pages and send them over the network. It's also nice for handling display of new data arriving on the server -- the client can just pull the data that is new and merge it into the data set on the client rather than requiring a whole new page draw including all the data you've seen before. This can save quite a bit of bandwidth.
AJAX should not be used when you need to keep your application simple, though technologies like jquery are making the client side easier and easier to get right. But in general I would say that if the information you're delivering is pretty static -- it only needs to be viewed in one or two ways, then an AJAX approach may just be overengineering.
That is not an easy question to answer without more information about your application. I find myself using Ajax to save very complicated pages. For instance I might have a page with a datagrid on it where people can enter multiple records at a time. It is also nice when you want to do partial updates of pages maybe when filtering a list or doing paging. Using ajax usually a lot more work than just posting back to the server so don't go too overboard.
For me, Ajax is useful in interacting with the DB, and for JQuery is for trapping entries of the user without bothering the whole page. So AJAX and JQuery, if mastered, will create a one hell of a website.
For when not to use it see When NOT to use AJAX in web application development?
In terms of when to use it my thoughts are:
When you don't want the user to endure a full refresh of the page when they trigger an action
When a rich UI is important to you.
When you can achieve the same effect without using AJAX using Jquery/JavaScript
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 4 years ago.
Improve this question
I'm trying to get some ideas about how to develop a web login screen. I'm using DynamicData Webforms, so most of powerful frameworks offers a lot of options, but I'll be very grateful to read your suggestions.
Thanks in advance
Edited:
beyond the functionality, I'll want to read your view-point about the presentation model, i said, im using fx3.5 so improve more than 2 textbox for a single login or using the login aspx control, i have in mind use silverlight but is possible to "light my webapp" that is build in webforms and dynamicdata with out change all the presentation layer?
More Undestandable: Example of using Extjs as Presentation Framework for View Layer, but my project is webforms so this will be nice for MVC.net i said cause is more flexible in json concerns
alt text http://rodotelmi.rebstech.com/wp-content/uploads/2008/07/picture-1.png
Please have a look at 65+ examples of login screen for some inspiration...
65+ Login form design
I would say that it depends on your application. If you are developing a public web site where you want to drive up the number of registered users and increase the click count on your publicly available pages, then a full-featured* login or a convenient login control on each page makes sense. If it is an intranet application where login is required to access anything, then a simple login page with minimal information is appropriate. You also need to decide if login is persistent across browser sessions or not and whether you want to give the user a choice, that will determine whether you need a "remember me" button or not. You also want to provide links to contact information and basic help (or a means to recover a lost id/password) if appropriate.
by full-featured I mean something similar to #Danny's suggestion that other parts of the application be easily accessible from the login page.
I do not like when website have only 1 field than you need to press a button, than it's a field for the password : In two steps.
Keep it simple and minimalism. I suggest you to have your login screen in all windows when the user is not login and not have him to go on a login page.
Have 2 textboxes : email (or username) and password.
A button to submit.
A link for "Forget your password".
A checkbox to "remember me".
The trick to a good login screen is to make it as interesting as the rest of your application, and give users useful links and other information there, as well as within your app (anything that doesn't require credentials, of course).
Take a look at the Facebook login page for a good example. In addition to the normal login infrastructure, you can search for users from there, sign up for the site, see their policies, etc.
the trick is make it as minimal as possible learn from google UI
This book is great book for UI design does not take your much of time to read Dont make me think
Keep it as simple and friendly as possible. It is important to make it the key focus if it on it's own screen so minimise the page to only show what you need, otherwise make it prominent in the header or sidebar.
For design and layout inspiration check out Pattern Tap or box.mepholio.
For the best user experience and form completion time, top aligned labels and a left-aligned submit button are good way to go if you have enough vertical space eg http://www.sanchothefat.com/projects/forms/login.
This resource can be useful too.
http://webdesignledger.com/inspiration/interface-design-loginsignup