I have created a page in views. Is it possible to use Views pages in entity reference field. I can able to use content types, but unable to use Views pages. Can anyone please help me on this?
Thanks.
Related
I am trying to create one html page using AngularJs with multiple views. And each view have nested states. When I am trying to use two view with nested states. It's only displaying one. Please tell me if I can use any particular steps or any link. It will be really helpful.
I have folder structure like shown in the attached imageFolder structure.
--Trying to add three child views into Parent-folder.html
A little view of what I am trying to do.
The following link will be helpful to explore nested state in angular ui router
multiple states by name
I'm working on a project where I need to use the AngularJS 1.4.3.
The problem is that I have to use the new routing of course, but on a view I need to use another partial views.
E.g.
I have a Home view, and this contains 2 dynamic table generated by data from a REST call. These tables should be partial views depends on the user role, etc.
Because the 1.4 is brand new I've not found any correct tutorial, or documentation, how can I create these type of sub-components.
Please help me,
Thanks in advance
Since nested views, and therefore ng-viewports in views do not work at the moment, ng-include is the current method of choice to accomplish this.
Edit:
I'am currently also working on a 1.4 project and we decided to use the next sprint to move to the ui router again, because of ngNewRouters many problems.
So in cakephp's layout we have the
$this->fetch('content')
right? does it mean i can only have one 'content' in one layout? I really need multiple content from multiple controller can it be done? how? please help me!!!
The layout isn't capable of pulling information from the controller. The controller is the place where the view is prepared to be placed within the layout.
When you access a CakePHP URL, it's in the following format:
http://example.com/controller/action
In other words, you're connecting directly to the controller, not the layout.
You use the controller to get data from the Models and then when everything is ready you set it to a view and then the view is displayed, with the layout wrapped around it. So, you only put HTML/CSS etc in your layout if you want it to appear in all of your views.
To answer your question, though, your controllers don't actually have any content. Your content is (presumably) in your database. Databases are accessed using Models and it's possible to pull data from multiple Models using a single controller, which is usually done by defining relationships between multiple Models.
What is the best way to create multiple views with different models using the backbone boilerplate? It seems like things are set up to render individual pages, but not to render multiple resources simultaneously.
I think I am understanding you correctly, but please let me know if I am not. Backbone shines in SPA's (Single Page Apps). I am not saying that it should only be used for an SPA. If you start thinking of views as sections on a single page, I think Backbone starts to make more sense. So when your model updates or changes, the section/view is being re-rendered and not the entire page.
Look at the Trello and read this article http://blog.fogcreek.com/the-trello-tech-stack/ - especially the part on Backbone. I think the above will answer your question more thoroughly.
Tyrone
I'm using CakePHP's ACL component to manage permissions for my app. I have about three different "Roles", with different access levels. I am using the HTML helper throughout, to create links to different pages. I would like links to only display if the user has permission to access the page.
The obvious but cumbersome approach, I guess, would be to set variables to the view containing permissions and show links based on these variables.
I was wondering if there is a better way - perhaps a helper that extends the HTML helper to provide a method that checks permissions first?
Thanks.
I wouldn't recommend to use a helper which has this sort of functionality.
This is because this helper would have to do the checking on every link you use on that page. This would slow down your application.
So I think the best approach is your approach. Set the permission on login and display your links accordingly.
We are using this in our application, too, and it works very good and fast.