1 Topic by onyx

  • onyx
  • Member
  • Offline
  • Registered: 2005-06-20
  • Posts: 39

Topic: "dynamic" rootpath

Hi,
I'm trying to install MCFileManager and have an issue..

I'm implementing it as a stand-alone (although I have tinymce installed too). I'm using it as a means to let users "attach" files to their posts. On the question post page, there's a link 'Attach Files' and when clicked on, MCFileManager launches. The uploaded files for each post would be stored in a folder designated just for that post. .e.g.

/attachments/post343/
/attachments/post344/
/attachments/post884/
... etc ...

The rootpath is set to /attachments but it has to be /attachments/<postid> depending on the variable <postid> which is known by my own PHP script.

The user posting (e.g. post #333) should not be able to go back into /attachments. They are to be confined in /attachments/post333/.

Keep in mind that <post id> is different everytime a user makes a post so the script has to somehow be able to specify a different rootpath every time there's a post.

What is the best way to achieve this?

Please let me know if you need further clarification.

2 Reply by spocke

  • spocke
  • Administrator
  • Offline
  • From: Sweden, Skellefteå
  • Registered: 2004-11-25
  • Posts: 14,357

Re: "dynamic" rootpath

This could be done by creating a authenicator class and setting a session before. When the "post" page loads set a session value for example:

$_SESSION['post_root'] = "/attachments/post74545";

Then in the authenicator plugin you will be able to grab this value and insert it into config like:

function init(&$config) {
    $config['general.rootpath'] = $_SESSION['post_root'];
}

There are a description on how to create authenicators in the manuals and there is also a example plugin in the plugin directory that shows how this is done. Hope this gives you some idea how to do this.

Best regards,
Spocke - Main developer of TinyMCE

spocke's Website

3 Reply by re_phil

  • re_phil
  • Member
  • Offline
  • Registered: 2005-08-31
  • Posts: 12

Re: "dynamic" rootpath

Am I getting it right that I can use this function to modify each users rooth path ?

I have the following issue:

Several users log in. Each user is responsible for it's own area. Therefor I want to make it possible to specify folders that the users can access.
For examply User "user123" is the one who takes care of the imprint. The Folder /downloads/imprint/ should be the only folder he has access to, thus his root folder. Same with the image manager. /images/ is the normal images folder but the user should see /images/imprint/ as his root folder.

Another user "user456" is then responsible for contact and has only "/downloads/contact/" and "/images/contact/ as his folder. And so on.

An administrator of the website, however, should be able to access all the folders so his roots would be "/downloads/" and "/images/".

Please let me know how this can be realized. Thank you very much in advance.

The corresponding user folders are known by my own scripts.

4 Reply by spocke

  • spocke
  • Administrator
  • Offline
  • From: Sweden, Skellefteå
  • Registered: 2004-11-25
  • Posts: 14,357

Re: "dynamic" rootpath

I suggest you write your own authenicator if you have enough PHP skills. You could also do this by using the session authenicator and then switch the user session key to vaious values and set it to a empty string when the root is logged in.

More info about the user key:
http://tinymce.moxiecode.com/filemanage … r_key.html

Best regards,
Spocke - Main developer of TinyMCE

spocke's Website

5 Reply by re_phil

  • re_phil
  • Member
  • Offline
  • Registered: 2005-08-31
  • Posts: 12

Re: "dynamic" rootpath

OK, I'm not quite sure whether my PHP skills are good enough for that but I'll give it a shot.
I'll let you know if I made some progress or not.

6 Reply by spocke

  • spocke
  • Administrator
  • Offline
  • From: Sweden, Skellefteå
  • Registered: 2004-11-25
  • Posts: 14,357

Re: "dynamic" rootpath

The ${user} user approach is very simple. Simply set up a session key correctly and it's done. Building a own authenticator is more complex but gives you higher flexibility since such plugin can modify any of the config values on the fly.

Best regards,
Spocke - Main developer of TinyMCE

spocke's Website