We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 4429
    • 429 Posts
    I’m trying to think about how it would work for other users.

    I want people to be able to login and create their own photoblog too. obviously these people would not have access to the manger.

    Overall i’m looking for the site content to be a collection of user blogs.
      • 7923
      • 4,213 Posts
      Then it get’s hard again, and out of MaxiGallery scope. You need to do a system where frontend users can create new documents with specific template that has a MaxiGallery call in it. And if the galleries should be only manageable to that specific user that creates the blog/gallery, you need to have the webusers ID in the MaxiGallery call.

      Here’s one example of creating that. But that’s pretty old post and it would be better to do it with FDM snippet now. FDM snippet does have a lot of bugs in it, so you’d need to dig up that thread if you encounter something.

      It’s not an easy task to set this up, but if you spend some time with it, you learn much about MODx and will get it done.

      EDIT: Btw, the tutorial in the wiki doesn’t create the galleries so that they could be managed only by the person who created it. They can be managed by everyone on that specified webgroup. You would have to implement it so that the webuser username / id is saved on a TV when the document is created and then that TV is used in MaxiGallery call in the document template for &manager_webusers parameter.


        "He can have a lollipop any time he wants to. That's what it means to be a programmer."
        • 4429
        • 429 Posts
        This thread should probably be moved as we have moved as we have wondered from the Maxigallery path.

        I’m just trying to rack my brain to see how this would work and how to go about it step by step.

        I’ve gone back to using the modxhost template as a base until i get the required functionality.


        Here is how I see it working:
        a) A user joins the site and is automatically directed to a page that they can create a blog on - I’ve seen a post about auto creation of pages for new users so thats fine.
        b) On this automatically created page there will need to be a call for Maxigallery and either Newspublisher or FDM - I have sucessfully installed/used FDM but prefer Newspublisher for blog content.
        c) Each blog post must be a new page in order for it to have its own gallery
        d) Only the author i.e the user can edit his/her blog
        e) Only the auther can edit his/her images

        Now what if that user has more than one blog?

        I was thinking the structure might be:

        User blogs
        ---John
        --blog about Spain
        -- blog post 1
        -- blog post 2
        --blog aobut Russia
        ---Carl
        ---Mike

        The pages and structure will need to be created dynamically as the user adds posts/blogs.

        What are you thoughts? I am I over complicating it?

        This is very difficult for me as I know nothing of php or programming other than cut and paste.
          • 7923
          • 4,213 Posts
          Yes, you got it right.

          I would suggest to use FDM for the creation and editing of the blog post documents, because it can handle TV’s. You need to make it always store the webuser username to a TV when the document is created. From this TV you can then get the username for the MaxiGallery call in the template. E.g. The blog post document template would have the MaxiGallery call [!MaxiGallery? &manager_webusers=`[*webusername*]`!]. That way all the "user submitted" galleries in the blog post documents are only editable by them self automatically (+site admin and backend users who have rights to edit that document).


            "He can have a lollipop any time he wants to. That's what it means to be a programmer."