How to show selective templates in the rule group? - endeca

Is there any way to show only selective templates corresponding to the rule group ?
For Ex. - I have to rule-groups (MobilePages & WebSearchPages), when I go to create a new landing page templates for mobile are also available in template selection for WebSearchPages And similarly templates created for the use in full-site are available in group for MobilePages.
Is there any way to avoid this, or offer only selective templates for pages corresponding to the rule-group ?
In templates I can only specify the entry of Zone & Page-style but not for rule-group -
<ContentTemplate xmlns="http://endeca.com/schema/content-template/2008" type="PageTemplate" id="MobileSubCategoryPage">
<RuleInfo zone="MobileCategoryPageZone" style="PageStyle"/>
Thanks in advance !

To the best of my knowledge you cannot restrict which types of rules are placed into specific groups.
I have sought such functionality as well. You would think that with group level permissions one would be able to control what goes into the groups as well.
This has likely changed substantially with the move to experience manager that does not have the same group concepts.

Related

Create login for multiple users with customized content with TYPO3 11.5.21

First of all, I must confess that I'm very, very new in TYPO3, therefore, my questions might be a bit confusing or not properly understandable. So, please be patient with me.
As already stated in the title, I want to create a login page for multiple users and every user should see a customized content, for example some pdf files or slides.
I was able to create a login page and it's working but I have no clue what's happening afterwards. I'm searching for a solution since days but the TYPO3 documentation is super shitty, especially for beginners like me.
My idea was to work with a MySQL database (I don't even know if this is possible). After the login all data about the customer are read from the database and defined files (some pdf and slides) should be shown.
Is this possible like that? Or how is the usual way to do that?
I'm happy for every hint!
Thanks a lot in advance :-)
cheers,
expikx
I tried to find a solution online but without success
you need a custom extension which will render the files based on the logged in user. By using the extension "extension builder" you can create a first version of your extension very quickly which can be used as base.
If you are german speaking, take a look at the videos of Stefan, e.g. https://www.youtube.com/watch?v=dhRBvTZoPQM& which document how to create an extension as well
If you use the Login of TYPO3 you can also use the access-management from TYPO3 for FrontEnd content:
for each erecord (page, content, news, ...) you can decide which group(!) of users can see it.
Each record in TYPO3 normaly contains a field (in the access tab) to select which groups can see this record.
It's up to you to define the groups each user belongs to.
And each group can access some content. TYPO3 merges it and even can give access to one record to multiple groups.
Regarding files like PDFs: if you do not need absolute access restrictions it would be possible to only list links to the files for the apropriate groups. (other users, even not logged in users could access the files if they know the URL)
e.g.:
You have users in three groups like owner of product A, product B, product C.
Of course there are owners of multiple Products.
For each group you can provide content like manuals, updates or lists of service points.
First you can give access to the pages about each product only to member of the matching group. All the content of that pages are visible only after login and if the user belongs to that group.
But you also can have mixed pages:
Maybe news where all updates are shown. Although each news record has (at least) one group to be shown to.
There could be one page with the news plugin to show all news. After login only those records are shown which belong to the groups of the user, other records are hidden. (not logged in users can see only records not restricted to any group)
If you want a individuality of content by person you need a group for each user.
If you want the user to select by himself what his interests are you need a FE plugin where he can select his memberships of individual groups.

Brand filtering on category pages

In Bigcommerce, is it possible to add brand filtering to category pages?
The current options appear to be that you can select from "all brands" by visiting the brands page, or you could use the search engine to narrow your results but you're forced to type a keyword or space. I want to offer a way to narrow the products by brand for the specific category the user is viewing.
I've spoken to tech support and they've informed me that this is NOT an option through the control panel and would have to be done through the API.
In my attempt to do this with the API however, it doesn't appear there is anyway to dynamically identify which category a user viewing. Outside of hard-coding a template for each individual category, how can this be accomplished?
I was informed by API support that this is NOT possible. Their recommendation was to submit the idea to the support team for future implementation, and that I might be able to accomplish it through a combination of javascript and screen scraping.

Drupal 7 Commerce Search API

I would like to create a searchbox like the standard one in Drupal but for Drupal Commerce (1.4). I did not use a product display, but all my products are created.
Is there a way to accomplish this?
I found this: http://drupal.org/project/commerce_search_api
and this: http://commerceguys.com/blog/commerce-module-tuesday-commerce-search-api (funny english :-) )
I've tried the second one, but I don't need a price ruler. I just want to give the visitor the possibility to search through my products. Not only the title field, but also the description field and if possible the taxonomy terms. It didn't work anyway.
Need help! Thx!
I thought to create this with views, but all good suggestions are welcome.
You could disable the Search API modules and simply use the default Search module provided by Drupal, this would enable searching through nodes, users, etc as usual.
The Search API may be over kill for what you want, unless you have a good mix of variations, prices, product attributes, etc that you would like users to use as search filters (price range, per attribute, etc).

SharePoint 2010: Advanced filtering on Managed Metadata field

I'm implementing a document management site on SharePoint 2010. Each document that is stored on the site, is tagged with one or more geographical locations indicating what the content of the document is about. I have implemented this using a Managed Metadata field that is bound to a term set in the term store containing all possible locations. The locations are organized hierarchically, so let’s say first by country, then by region, city etc.
I want to be able to quickly locate documents in a document library for a given location. SharePoint 2010 offers 3 out-of-the-box ways to accomplish this: (1) filtering on the column header, (2) using metadata navigation, and (3) using key filters.
So far, so good. Now this is where things are getting tricky. Each location in the term store is identified by a number of different labels. So each location has a default label and an average of 3 or 4 additional labels (synonyms). For example: a location could be referred to as “Amsterdam”, “S-123” and “W-456”.
I want to be able to:
Filter the document library by using any of the labels including the
synonyms
Include all locations that are below the location that he/she
specifies, in short: to recursively set the filter
Going back to the 3 out-of-the-box options:
Filtering on the column header; does NOT support use of synonyms and
does NOT support recursive filtering
Using metadata navigation; does NOT support use of synonyms but does
support recursive filtering
Using key filters; does support use of synonyms but does NOT support
recursive filtering
Can you think of a creative solution that meets my requirements using the out-of-the-box controls? And if not, what options do I have for full customization (custom filter web part, extending out-of-the-box web parts etc.)?
Hope to hear from you!
Regards,
Erik
I think I might have an answer. This works in our System - SharePoint 2010.
In you SharePoint instance, create your View of the list, but don't define any Filters. Save the View.
Open SharePoint Designer 2010 and navigate to the list and view.
In Design view, you then need to select the "WebPartPages:XsltListViewWebPart" (you may need to click one on the column headings to get the grey page elements to appear).
At the top of the screen, select the Options Ribbon tab, a green List View Tools upper-tab appears.
On this ribbon, far left, select Filter.
Define you filters.
It is tricky and not a smooth UI. Note the Group button allowing you to create groups of AND and OR elements. (I'd post an image here of the UI, but I no not have the experience points yet.)
Good Luck.

Content Permissions in Orchard

In an OrchardCms site, I need to create a hierarchical menu where I can show and hide menu items by user role. What is the best way to approach this?
One possible way would be to create and manage two menu's, each pertaining to a different layer where the layer rule species the respective Role. However, this means managing two Menu's which is not ideal. Many items in each menu would need to be duplicated.
Another way would be to create a custom Menu Part. The downside here is it seems like overkill.
Or am I on the wrong track completely, should I be looking more at filtering content items by role instead? In this scenario, I believe I would still need a way to specify menu filters.
I think Advanced Menu (available from the gallery) does menu trimming based on permissions.
Update: my bad. Try Quanta instead (part of the Science project). Should work well with Cartography.
I was able to create multiple menus filtered by role in layers with this simple PCG.RoleLayer module. You will still have to make separate menus though, and it doesn't restrict url access unless you change permissions.
After enabling the module, you can create rules for roles. For example,
role("Administrator")
Would make that layer only visible to those with the administrator role.