want to set category in phpbb3 - phpbb

I am new to phpBB3. I have just installed phpBB3 on my localhost. I have gone through it. I am getting one problem that if I want to create two types of forum
1. Pre Sales which can be seen by any visitor or visitors who are logged in
2. Post Sales which can be accessed by only the visitors who have paid for that
please guys is there any solution for that?

For the Pre sales forum, you don't have to do anything special. Guests will be able to see that forum by default.
For Post Sales, you will create your forum, but do not copy permissions from any other forum when you do so. Then log into your Administrator Control Panel, select the Forums tab. On the left select Forum Permissions.
You have two options at this point. If you are placing users into groups, for example a customer group that can access Post Sales, you will use the Groups column. Otherwise, you'll be managing each individual user. I'm making the assumption that you will want to do this by group.
Select the group(s) you want to have access to this forum from the bottom right box. Click Add Permissions and they will appear in the upper right box. Now highlight all of them and select Edit Permissions.
From the next screen you can customize what they can('t) do on this specific forum. The easiest is to select one of the preconfigured options (Standard, Standard+Polls, etc), but if you want to can manage specific permissions as well.

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.

VSTS Restrict access to sensitive work items

Foreword: I've searched around on this question a fair bit and found answers which are close to a solution, but not what I'm looking for. So here I am, and I hope someone can help me. I'm relatively new to VSTS, so be gentle (or at least constructive) ;P
The Question: I'm looking for a way to restrict access to specific tickets (NOT by ticket type) that contain NDA protected data, whilst keeping them in the same backlog and iterations as the rest of the tickets related to a project.
We have many different NDA protected customers, so whilst creating a new ticket type per NDA, and restricting access to this, could work, it's not the solution I'm looking for.
Alternatively, I'm barking up the wrong tree, and there is an entirely different and "better way" to support this use-case?
Edit 1 - More info: Let's say I have 1 backlog for a product. It contains only 2 work items. It's important there is only 1 backlog for planning and overview by a product owner.
One of the two work items contains sensitive information only half the development team should have visibility to. How do I keep both tickets in the same backlog and iterations, but hide the sensitive one from some team members?
Thanks in advance for your time!
Regarding permission of work items in a team project, you can set the permission in area and iteration scope, but can’t for specific work items.
So, you need to put these work items in different area and manage permission for this area. Simple steps:
Go to team project admin page
Work=>Areas
Click New/New child, to create a new area.
Click …=>Security, set the permission for the group(s) or user(s)
Click the default team’s settings => Areas
Click + Select areas to add that area in order to show related work items (in that area)

Archive subsites from sites in SharePoint 2010

I have a requirement to find a way to archive subsites from a site.
When I say 'Archiving' I mean moving a subsite from one site to another so the end users can still access the subsites and check the history etc.
The main site is a Training site and the subsites are training courses, when these courses have ran there is no need for them to be sat under the training department site and I can envision it becoming confusing with too many of these subsites.
I know I can move them using structure and content in site admin but don't really want end users to be doing that after each course has ran ( we have had over 500 this year!)
Has anyone else faced a similar issue or have any advice to how they would go about it?
Many thanks
Is there a need to retain the subsites? If so, instead of moving the site, perhaps changing the way your users access the sites would be an easier way. You could set up a list with the current classes (assuming you don't have one already) and include a field in that list that links to the course's subsite. Create a view that shows only the current courses so the end users never see the other subsites.
If you don't need to keep the subsites, you should look into some kind of workflow that can kick off when a class expires that deltes the subsite. I'm pretty sure you can't create a workflow with Nintex or SharePoint Designer to move a site to another location, so you may need to code something with C#.

Permissions issues with Office365 Sharepoint, Owner account

I have just been tasked with overseeing an Office365 Sharepoint team site, and there is a very odd legacy issue that was left unresolved by the last administrator. We have the standard set of groups that you would expect to see (visitors, members, owners) and one of the folks here is in both the Members (contribute) and Owners (full control) permission groups.
However, her ability to access things is... strange. She can view most everything, and add new content to most everything (lists, forms, etc.) But she cannot edit any documents, list items, etc. Nor can she delete items.
Is there a way that her permissions (full control) could be in conflict with another setting? What should I look for to investigate further?
All help will be greatly appreciated, as this is quite mysterious.
Cross-listed at: https://sharepoint.stackexchange.com/questions/58306/permissions-issues-with-office365-sharepoint-owner-account
You want to look at the document libraries and lists in question, by default they inherit permissions but this can be changed. Select the library and select the permissions icon from the top ribbon to check to see what that particular user's rights are for the items in question.

Can I show different articles to different users in Joomla?

I want to create a structure in Joomla for users. A different article for different registered users. I do not have groups. For example If I have 3 users, and when they click on a menu (for example, "Info") they see a different article from each other.
User A sees something different when he clicks on info and user B something else and user C something else.
How can I do this; are there any components?
There is no feature in Joomla or extensions that I know of that allows you do this. If you are using Joomla 2.5/3.0, then you will be best off creating different user groups, then creating 3 separate menu items, 1 for each group that only they have access to.
If you are Joomla 1.5, then you only extension that I know of for adding custom user groups is ArtofUser, which is still limited in it's own way.
Can you not just use the newsflash module to show an article from a category - and then put all these articles into this category. Or are these users in different user groups in which case it would be better to simply create an article connected to a menu item for each user group