I am reorganizing my episerver site structure which is as given below:
The idea behind the same is that the sites keep on growing & to manage the same ,adding it under container pages that will be
manageable.
In the above example ,both start page 1& 2 belongs to same set of groups which is why it is clubbed into container page A.
Now after reorganizing , when I try to assign the common group of start page 1 & 2 on container page A, the Add Users/Groups is disabled.
Is there a way to assign the group on a container level rather than individual site level.
Any input is appreciated.
Related
Can anyone guide me to a route to take as far as making a basic page in drupal 7 and then having that page load a block with images inside based on URL path.
So I have a content type that is for 1 type of pages and another content type for another type of page. Each content type has 30 pages. I don't want to create 30 pages for 1 page that will have the same content over and over but with a different logo.
http://www.example.com/contenttype1name/%/staticname
I need to make the menu have an argument passed and then based on what is passed go get the correct image.
Sorry if this is confusing. Thanks for your help.
You should look into the views module - it allows you to easily create a view with dynamic parameters (contextual filters) that allow you to easily tackle things like this.
I used contextual filters on views and nodesymlinks along with panels that was already installed.
Modules Used:
Views
Nodesymlinks
Panels
Step 1: admin > Modules > Add Modules/Enable.
Enable Nodesymlinks
Enable Panels and panelizer
Step 2: admin > Structure > Views > Add View.
Make view, name it and check block not page (I used Fields).
Step 3: admin > Structure > Views > your view.
Add filtered Criteria - Content type = your type.
Content should be Published only.
Add contextual filter: title.
Configure contextual filter: Content: Title.
Provide default value. Select Raw Value from URL.
Path component select 2. You can add it where you want in the URL.
Use path alias and check it.
Under More you need to check this box: Transform spaces to dashes in URL.
Check it in Views and save.
Step 4: admin > Content > Add Page.
Add a basic page.
On the bottom of the page you will see: Provide a menu link. You want to check that box. Now you will be able to add all the menu links that you wish this page to show up on. Add links/Paths and titles. Make sure you use argument 2 in your link to be your content on the views block in step 3.
Step 5: admin > config > content > panelizer.
You want to go into this pages panelizer, could be basic or whatever your content type would be. Add your views block and save.
Step 6:
Test it. If it doesn't work then you need to check your titles in argument 2 in the URL. Worked for me. Saved me a ton of time.
In summary, I am looking for a content-based access control solution, NOT a user role-based solution.
The scenario: Page 1 contains content from various access control levels (i.e. levels a, b, and c).
Currently in Drupal, you can display/hide content based on user role. However, I want to block access to the entire page if the user is not in the highest content level required.
Example: A user with access level a and/or b would be blocked from seeing page 1, but a user with at least level c would be able to see the page and all of the content on it.
The catch being that the per-page access levels must be dynamic to prevent incorrect page tagging as content is added, updated, or removed.
Does a module like this exist already, and if so, what is it?
If this doesn't exist, is there a straightforward way of implementing this?
Server configuration is Drupal 7 with some Open Atrium 2 modules.
I'm not sure on what you mean on access control levels, but lets say they are functions you can call (with returns).
In this case you should implement hook_node_access for controlling access to a node or hook_field_access for controlling access to a field.
https://api.drupal.org/api/drupal/modules%21node%21node.api.php/function/hook_node_access/7
You should return 'NODE_ACCESS_DENY' from it if you want to deny acces.
https://api.drupal.org/api/drupal/modules%21field%21field.api.php/function/hook_field_access/7
You should return FALSE if you want to deny access to a field.
I have made one block for most visited links (Top Links) in my drupal website but I dont know how to list most visited from different pages. For example, if I have created a page named drupal and within that page i have added some content with some title, then i have to examine and count those titles and list the top visited title from each and every page on my homepage(only one from each and every title that is most visited) and list them on my homepage block.
Could anyone help me with this.
Thanks in advance!
Make sure the statistics module is enabled. Visit /admin/config/system/statistics (Drupal 7) and make sure Count content views is enabled (ticked).
Use views to create a block the usual way; for example add a field like Content: Title. Then make sure you add a sort criteria of Content statistics: Total views (desc).
I am developing site using Drupal7 with JD Fashion theme from Joomlart
I have created one vocabulary and terms it in the taxonomy.I have use this terms for menu navigation and added some stories(node) for each menu item.
In post setting I have kept no of nodes in main page to 3 using admin/content management/post setting.
But it is only working for home page and not for inner pages.
I want to restrict the no of nodes to 3.
How can i do that?
Is their any module or extension for pagination to control no of article per page?
You can turn on the Taxonomy Term view in the Views UI to have more control over the taxonomy pages. This view is automatically generated by the Taxonomy module, but is disabled by default.
Once turned on you can set the Pager in the Page setting area to Display a specified number of items and set the numer of Items per page to the desired number.
This will limit the number of nodes displayed in the Taxonomy pages.
You can do this without views.
The number of nodes displayied in taxonomy page is determined by the default_nodes_main variable, that also controls, the n° of nodes in the home page and the number of blog posts.
You can adjust that at admin/config/system/site-information > front page > n° of nodes in front page.
So, beware of side effects. I made a search in all of the D7 code and i found out that default_nodes_main appears in
blog.pages.inc:26
blog.pages.inc:66, limiting the number of post
node.module:2601, limiting the number of sticky nodes (front page)
taxonomy_pages.inc:55, limiting number of nodes in the taxonomty page
Known the consequences, you can use that setting.
Before I get into the details, here is the overall goal:
I want to have a group of users which get access to a feed, and any new items that appear in that feed they will get access to as well.
Details:
I am using Organic Groups, Feeds/Feed Items, and Views. I have setup a single Organic Group and added a single user to it. I have taken a Feed and added it to the group as well.
I have tried a few different combinations of the queries for Views and here is where I am at currently: http://cl.ly/2T1a0s1A0j3A0I0d3i1u
There is a relationship setup between the Feed and the Feed Item. There is a filter setup that says if the user has permission to view the Feed they should be able to see the Feed Item.
However, when I login to the user account and visit the URL (which used to just be static and take no arguments, ignore the % I just added) I get a blank page.
It would be great to get some help figuring out this problem and/or some pointers on how to debug it + learn more about Views and how I could use Views/OG to solve this problem.
Thanks,
David
The best way I did OG Groups was to create the group under content type. Once that is done. go back into content type and click on Feed scroll down to OG Groups tab click on it. You should seeNODE in the drop-down box and Groups in a select box below. Make sure node is clicked and Group is highlighted. Click save and now do the same for Feed Item. There is one thing to be mindful of, when the feed imports, it will be bundled with the group however the feed it self will be separate from the nodes created linked only by the group. One way to make it easier to manage is to place the feed and the feed items into the same book when setting up the feed. It akes life much easier that way.