Tilman

Thanks for the info, this setting is pretty important to me, because 95% creates a little too big image sizes for what I need. Good to know I can change that!
Would be nice to have the chance to set this in the wppa backend. Right below the setting for the image size in Table I:A3 would be perfect, at least this is where I searched for it… possible in a future release?

I have to agree, as a hardcore nextgen-gallery user (>10 running installations) i am suprised how much you can do with this plugin! The config backend is so much better than nextgen’s and the support is amazing ?? I am sure I will be around for quite a while…
I have to add something, I think you missunderstood me here. I set the table IX:B5 to 100 pics a day. unfortunately, this comes out to be 100 pics per day per album. So the user can upload a lot more Images than intended just by creating more allbums.

• If owners only is checked: (Table VII-B1): On creation of album: Set parent to the lowest id (will most of the times be the first created) of an already owned album.
• If owners only is checked: User can set parent to one of his own albums only
• Admin can decide if non admin users can change the ownership (give albums away)

In addition to the “Flat Album” as default, this definitely solves a lot of trouble I have right now! I am looking forward to this, thank you ;-).

I guess I would add a “Limited Album Admin” Role in Table VII:A where you could define capabilities aside from the “real” Album Admin. I would, for example, not give a Subsriber the right to

• Use alt thumbsize
• Link type
• Link to

Most of those capabilities would only confuse the user and I think it’s best to keep the backend as easy as simple for the “regular” user.

Sorry, I didn’t want to offend you, it was just a well-meant suggestion.

It’s good to know the plugin has been tested with numbers this high. It’s a lot of work moving all the images, it would be mean if I had to stop after including some 10,000 pictures.

On the other hand, I don’t really understand the trouble here. I mean, you still could name the files like the ID, for example: 12694.jpg. I have no problem with that. There only needed to be an additional field called “path” which gives back the additional path within the default images path. For example, if I use the browser upload, the field path would be empty, because those images are loaded into the default path. But if would I use the import feature, the path would be /pathtoablum/subalbum`.
If I move the images around in the Album Admin, e.g. moving them to another album, the album ID would change. The path wouldn’t. I know, it’s not pretty if you have an image /myholidays/summerholidays/spain2011/123.jpg which is included in the album My holidays > Winter Holidays > Austria 2012 but if I (as owner of the website) care, I have the chance to delete the images, and upload them in the right folder before importing again. I would do that, because a neat folder structure means a lot to me, but maybe others wouldn’t, the frontend, however, should look the same.

I really don’t mean to offend you, maybe it’s just not that simple like I see it. If so, I would be glad to learn something here ;-).

I know this has been asked already in another thread, but the fact, that all images are stored in the same folder is a deal here, too. I don’t like the idea of having the user images in the same folder as the rest. Wouldn’t it be possible to at least create subfolders for the users like /wp-content/uploads/user/username123/?

I am trying to create a user gallery as well and I manage to set it up as far as it seems to go. Users can register as subscriber and they get their own album in the album “Users”. The feature, that empty albums are not displayed is really perfect here!
Some problems, though: I want the users to be able to create sub-albums to sort their images, and that is where the trouble starts. I gave “Subscriber” album admin and image upload rights, but only in the album they own. This works more or less. The user can create albums in his user album and upload images to the different albums.
First problem: The 100 pictures per day threshold doesn’t work here, because it’s seems like the user get’s a new 100 images for every album he creates.
Secondly, the user still has too much rights. He can create albums only in his own album, but he can set rights as he likes. So he can set the owner to somebody else and thus can’t upload images to his own album. Also, the other user can now upload images into his ablum, because he is the owner…
The user can also set “parents” of the new album to “none” which is bad, because the album will not show on his profile page. Even worse, -none- is the default setting, so a lot of users will no see this option and wonder where their album had gone.
He can also set Links, which is also quite bad in my opinion, so he can create albums and link to any page of my website, which can get quite confusing.
And lastly, the user won’t see any albums in “Album Admin” menu, because it shows the albums with “parents” set to “none” by default, and that’s the level the user has no rights to edit. A click on “Switch to Flat Table” shows his albums, I guess a lot of users won’t find this.
I conclude: Beeing able to build a user gallery is a killer feature! The whole plugin is very nice, but this might be the best feature of all. Flawless integration with the wordpress user management, it’s a dream! I just wish to have this little feature, to make the user be able to create albums. It’s not practially working right now, but if you could make it work, that would be awesome!

had the same problem at first, turns out, you have to be logged out to see the form… took me a while ??

Okay, I was able to solve my problem. Might sound stupid, but updating did the trick. I am always very careful when updating themes, even though I put a lot of efford in “styling around the style.css” to not make my settings get deleted in an update, i am only updating when I have the time to fix possible problems… so I was a little bit behind with the updates but didn’t thought of it beeing a problem. Turns out, it was all I needed to do.

Thanks! In my case, I wanted to erase all the things that are published by the theme if the post is sticky.
So I set the if(!is_sticky()) around the <p> tag. So

<p class="timestamp"><?php the_time('j F, Y (H:i)') ?> | <?php the_category(', ') ?> | By: <?php the_author(); ?><?php edit_post_link('[e]',' | ',''); ?></p>

became:

<?php if (!is_sticky() ) { ?>
<p class="timestamp"><?php the_time('j F, Y (H:i)') ?> | <?php the_category(', ') ?> | By: <?php the_author(); ?><?php edit_post_link('[e]',' | ',''); ?></p>
<?php } ?>

Just for the search engine Visitors.. ??