so

it's work but it's not userfriendly..

for each forum you want to be restricted you have to do that :

1 - the forum have to be first public
2 - all members select to access this forum have to be logged one time and access to this forum public
3 - then in the back end set this forum to registered
4 - allow in the back end all the members access to this forum wiht the admin
5 - done

each time you want to add a user you have to delete all member access, set forum public and re start at step two lol



in fact the problem is the gestion of the seccion table in mysql
normaly when a user logged in the script have to set seccion table (jos_fb_sessions) according to the private user table (jos_fb_private_users) but it doesn't.


so possible solution is to use the hack normaly (set registered forum, allow access)
but each time a new member who have to access normaly to this forum you have to also modifiate his seccion into the mysql table like this :

Caoma wrote:


DROP TABLE IF EXISTS `jos_fb_sessions`;
CREATE TABLE IF NOT EXISTS `jos_fb_sessions` (
`userid` int(11) NOT NULL default '0',
`allowed` text collate latin1_german2_ci,
`lasttime` int(11) NOT NULL default '0',
`readtopics` text collate latin1_german2_ci,
`currvisit` int(11) NOT NULL default '0',
PRIMARY KEY (`userid`),
FULLTEXT KEY `allowed` (`allowed`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_german2_ci;

--
-- Contenu de la table `jos_fb_sessions`
--

INSERT INTO `jos_fb_sessions` (`userid`, `allowed`, `lasttime`, `readtopics`, `currvisit`) VALUES (62, '8,10,14,13,18,46,19,20,53,22,24,23,27,29,50', 1204057311, '', 1204066904);
INSERT INTO `jos_fb_sessions` (`userid`, `allowed`, `lasttime`, `readtopics`, `currvisit`) VALUES (121, '8,10,14,13,18,46,19,20,53,22,24,23,27,29', 1204059364, '', 1204061172);
INSERT INTO `jos_fb_sessions` (`userid`, `allowed`, `lasttime`, `readtopics`, `currvisit`) VALUES (117, '8,10,14,11,12,13,18,46,19,20', 1172505754, '', 1204041837);
INSERT INTO `jos_fb_sessions` (`userid`, `allowed`, `lasttime`, `readtopics`, `currvisit`) VALUES (74, '8,10,14,13,18,46,19,20,53,22,24,23,27,29,50', 1204061349, '396,522', 1204066564);
INSERT INTO `jos_fb_sessions` (`userid`, `allowed`, `lasttime`, `readtopics`, `currvisit`) VALUES (109, '8,10,14,13,18,46,19,20,53,22,24,23', 1204066186, '501,366,226,250', 1204066244);

it's an exemple ;
In red userid : Number of the member, you have it if you pass your mouse on his profil
In blue allowed : the forum id allowed to this user (same thing mouse over the forum)



here in french :

www.bestofjoomla.com/component/option,co...5234/catid,44/#45365



the hack only permit to "remember" the seccion



normaly the seccion is delete after 30 minutes of inactivity so also another way to don't use the hack : Caoma resolve it hack with this :

open fireboard.php

find

//grant them 30 minutes of inactivity; then recheck privileges and try to send them back where they came from
$previousVisit = $fbSession->currvisit;
$database->setQuery("UPDATE #__fb_sessions SET allowed='na', readtopics='', lasttime=$previousVisit where userid=$my_id";
if (!$database->query()) die ("Serious db problem:" . $database->getErrorMsg());

replace it by :

//grant them 30 minutes of inactivity; then recheck privileges and try to send them back where they came from
$previousVisit = $fbSession->currvisit;
$database->setQuery("UPDATE #__fb_sessions SET , readtopics='', lasttime=$previousVisit where userid=$my_id";
if (!$database->query()) die ("Serious db problem:" . $database->getErrorMsg());

allowed='na' is delete...
but but it's really no user friendly

baboon wrote:
so

it's work but it's not userfriendly..

for each forum you want to be restricted you have to do that :

1 - the forum have to be first public
2 - all members select to access this forum have to be logged one time and access to this forum public
3 - then in the back end set this forum to registered
4 - allow in the back end all the members access to this forum wiht the admin
5 - done

each time you want to add a user you have to delete all member access, set forum public and re start at step two lol





Incorrect.

not sure if it was changed in the version written by others for j!1.5.1

The work flow fo J! 1.14 is as follows

- Create a forum
- Make it's access to at least "Registered" (This makes it "private in a regard"
- Add a user to the forum through private access

The forum is now private to that user and any other user who is in the forum

Your process makes absolutely no sense according to not only the fireboard work flow but the way that I wrote the software.

You should re-assess how you are doing it

Dannymh wrote:

Incorrect.

not sure if it was changed in the version written by others for j!1.5.1

The work flow fo J! 1.14 is as follows

- Create a forum
- Make it's access to at least "Registered" (This makes it "private in a regard"
- Add a user to the forum through private access

The forum is now private to that user and any other user who is in the forum

Your process makes absolutely no sense according to not only the fireboard work flow but the way that I wrote the software.

You should re-assess how you are doing it


sorry i forgot to precise it : my test is under J 1.5 and follow some answers about the hack for this version
for the for J1.5 i reproduce this process several times and in two different installation of J1.5 in two different PC.

if i follow the "normal" instruction give for the hack under J1.0x, it's doesn't work, members selected don't access to the restricted forums, like i say the table Jos_fb_sessions is not refreshed according to the ACL. :/



this tread will be more comprehensive if it 'll be split one for J1.0x (hack stable) and another for J1.5 (hack unstable)!?

baboon wrote:


this tread will be more comprehensive if it 'll be split one for J1.0x (hack stable) and another for J1.5 (hack unstable)!?

Agreed. though I had a bit of an issue understanding you walk through. From what I understand, I would have to add everyone to the restricted forum at one time. If i needed to add another person or two, I would have to set the forum back to everyone readable. Restricted it, and re-add everyone to the restricted forum?

Thebroke wrote:
From what I understand, I would have to add everyone to the restricted forum at one time. If i needed to add another person or two, I would have to set the forum back to everyone readable, Restricted it, and re-add everyone to the restricted forum?

not exactly, for each new members :

1 - delete all members add (include the admin)
2 - set it public
3 - all old and new members add, have to logged in at least one time to see it public.
4 - set it restricted
5 - add old and new members to access restricted in one time (with the admin too)

like i say i think it's more usable to do this by mysql lol

Making the change to mysql would make it so all people wouldn't have to access the forum in public view?

I wish there was a simpler solution =

I don't understand why the workflow was changed for the 1.5 version?

AFAIK it was only changed to remove the AJAX search primarily.

The original solution never touched the sessions table. In fact the sessions table was irrelevant. The user was added to the forum and no user level permissions were changed

Thebroke wrote:
Making the change to mysql would make it so all people wouldn't have to access the forum in public view?

Yes if you using the permissions by the table seccions you don't have to repeat the process each times you add a user ...

but finally it's peharps more simple to don't use the hack for j1.5 and only the solution suggest by Caoma (see the link give before in my post)


Dannymh wrote:
I don't understand why the workflow was changed for the 1.5 version?



AFAIK it was only changed to remove the AJAX search primarily.



The original solution never touched the sessions table. In fact the sessions table was irrelevant. The user was added to the forum and no user level permissions were changed

i don't understand too lol

the workflow i wrote is the one i found by iteration who work with the hack for J1.5.

the Caoma suggestion and the analyse of the table seccion make me suggest that it work with this but as you say it's maybe an error of analyse

the hack for J1.5 don't work correctly ... so using the seccion can be an alternative.

perhaps a idea to follow :


Now I have found the error/bug.

At Joomla 1.013 the Table "jos_core_acl_aro_groups" provides a field "group_id".
At Joomla 1.5 the Table "jos_core_acl_aro_groups" provides a field "id".

The Content of both Fields are the same, but the fieldname is different. Now I have create a new field with the name "group_id" an copyed all contents from "id" into this.


This problem was listed here, I can't find it now to link to it. (I'll try and find it later when I have a bit more time).

Your right it revolves around group_id.

You need to change $aro_group->group_id to $aro_group->id in some of the files.

Important thing I forgot was to change the files contained in the template I was using, so it didn't work at first. But its working now. Members can access the restricted boards as normal.

The files I changed were;

view.php
showcat.php
listcat.php
fb_sub_category_list.php

These were in the template directory of the template I'm using

You also need to change fb_pdf.php in the sources directory.

I'm using Joomla 1.5 stable and Fireboard 1.0.4


www.bestofjoomla.com/component/option,co...w/catid,75/id,42569/

Is there any way you can link what lines you changed in each file? Unfortunately I am not nearly as well versed at php as you are