User home galleries

How would the flow work? They'd go to the site and have a login page, then after they log in they'd be sent to a specific album? Can they see the other albums? I'm guessing that you could write a module that traps the user_login event and registers a new shutdown event to redirect the user to a specific album. That would probably get you off the ground there. Your module (let's say it's called "xxx") would have a modules/xxx/helpers/xxx_event.php file that contained class Xxx_Event which has a user_login() function which would do something like:

Event::add("system.shutdown", array("xxx", "redirect_user"));

then you create xxx.php in the helpers directory which contains a class called Xxx and a static function called redirect_user() which does:

url::redirect("albums/1");

Where you inject the id of the id you want to redirect to there, instead of 1.

Then your login page is:

http://example.com/index.php/login/html
(that page is unthemed, but we can work on that)

---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!

Ah, right. The ajax code does this:

      print json_encode(
        array("result" => "success"));

Which triggers the dialog box to close and refresh the current page. Perhaps a better approach would be for you to store a value in the session, then subscribe to the gallery_ready() event and when that fires, check the session. If the value you stored is there, delete it from the session and do the url::redirect.

---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!

Awesome! It would be really great if you created a fork of the gallery3-contrib repo on GitHub and added it there.. that way we can use revision control on it and start getting others involved too. I installed it in my test G3 and it worked fine after I made one tweak. When you refer to database tables in SQL you should wrap it in {curly} braces so that it handles table prefixes properly. So the two database lines in your installer become:

  $db->query("ALTER TABLE {users} ADD home int(9) default NULL;");
  $db->query("ALTER TABLE {users} DROP COLUMN home;");

Also in general, we don't want to modify tables from other modules because it can cause that module to break on upgrade. A better way is to create your own table instead and store the data there. You can listen for the user_deleted event to get rid of the rows in your table to keep it in sync.

Finally, I would be happy to create a way to let you get this into the user edit page. The way to do that is to generate an event when we create the form, and then generate an event when we successfully process it. For an example of how this works, look at modules/gallery/helpers/album.php in the get_edit_form() function. Towards the end we call:

  module::event("item_edit_form", $parent, $form);

Then the tags module in tag_event.php listens for that and has:

  static function item_edit_form($item, $form) {
    $tag_value = implode("; ", tag::item_tags($item));
    $form->edit_item->input("tags")->label(t("Tags (separate by , or ;)"))
      ->value($tag_value);
  }

So it's adding its own element to the form right there, and then this gets displayed when you edit an album. In the form processing code we trigger a "item_edit_form_completed" event, and then the tag code processes the result of the form.

I've gone ahead and added these same events to the user code:

 user_add_form_admin            admin adding a user
 user_edit_form_admin           admin editing a user
 user_add_form_admin_completed  successfully added a user (admin)
 user_edit_form                 user editing their own settings
 user_edit_form_completed       successfully edited a user (admin and user editing own settings)

Try hooking in to those!
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!

I made all the changes you suggested.. let me know if there's anything else I missed. Let me know when you submit the code to your fork and I'll pull it into the main repo!
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!

I've pulled your code into the contrib repo-- great work, thanks! For bonus points, you can update your code to conform to our code style: http://codex.gallery2.org/Gallery3:Coding_Standards which will make it easier for me to help you keep the code up to date when I make API changes, etc.

Also.. what error were you getting when creating new albums? Start a new thread for that if you're having a general problem and we'll get to the bottom of it.
---
Problems? Check gallery3/var/logs
bugs/feature req's | upgrade to the latest code | use git | help! vote!

you need to run the upgrader:
http://codex.gallery2.org/Gallery3:Upgrading

Windows is not supported.

Dave

_____________________________________________
Blog & G2 || floridave - Gallery Team

Floridave - This was a fresh install from the tip of the trunk sometime last week, rather than an upgrade. Chances are I caught it whilst someone was still developing that module (I was just checking the new methods for my module)... but if not then there might be a bug in the initial table creations. I've been using Beta 2 (with no problems) instead for my client development and will probably wait for beta 3 until I download again.

Yeah, I know it's only supported on linux/unix, ... I'm fine with that .. all my live sites are linux/unix... just not my development box.

Ben

Benjamin Albert Smith - Photography

All looks good to me.. cheers..

Ben

Benjamin Albert Smith - Photography