and I get an error if I try to view and album with 2 sub-albums. [attach type=thumb]7009[/attach] in Elkarte error log: Tipo di errore: Generale Warning: Invalid argument supplied for foreach() /index.php?action=media;sa=album;item=7 File: /themes/default/levgal_tpl/LevGal-Album.template.php Line: 45 I am using the latest version of Levgal
The add new Album link doesn't appear to work, also the tick and cross for the GD / Imagik are a bit large ;-)
I'll look at it more later, the TinyPortal stuff will need a slight change but I can do that when I get the chance as its 01:00 here and I need sleep.
I just tried this on two installs, both on different servers and both 1.1.6 - 1.1.7 then levgal, I'm seeing exactly the same issues as you were tino. This is with or without TP installed. No errors in log.
From the media dropdown menu the only buttons that do anything are the "My Media" ones, all the others just return me to the forum index. And as you mentioned, also the tick and cross for the GD / Imagik are huge when you install it.
I had to install the latest 1.1.7 patch then install levertine for it to work. I never worked out why it failed initially as is just worked then.
Check to make sure the permissions on the directories are ok. I think the css issue was due to the minify css not being refreshed.
You can have sub albums. What you need to do is add a few albums under a user or group or ownership level.
Then when you view the albums of that user or group you will see on the side an arrange albums option, choose that. You are now in a drop and drag interface like in the manage boards area of the APC. Simply drag an album towards the right and drop in on the album you want it to be a child of. You can have many levels as well.
The album order shown here is maintained, so its up to you to sort them however you want and that is how they will be displayed.
ETA: that D&D is not ajax, so arrange it like you want and click save !
Not very intuitive... and I get an error if I try to view and album with 2 sub-albums. in Elkarte error log: Tipo di errore: Generale Warning: Invalid argument supplied for foreach() /index.php?action=media;sa=album;item=7 File: /themes/default/levgal_tpl/LevGal-Album.template.php Line: 45 I am using the latest version of Levgal
The add new Album link doesn't appear to work, also the tick and cross for the GD / Imagik are a bit large ;-)
I'll look at it more later, the TinyPortal stuff will need a slight change but I can do that when I get the chance as its 01:00 here and I need sleep.
I just tried this on two installs, both on different servers and both 1.1.6 - 1.1.7 then levgal, I'm seeing exactly the same issues as you were tino. This is with or without TP installed. No errors in log.
From the media dropdown menu the only buttons that do anything are the "My Media" ones, all the others just return me to the forum index. And as you mentioned, also the tick and cross for the GD / Imagik are huge when you install it.
In the original model, 0 for ownership was for 'site ownership' so that if people deleted accounts or left groups, the content wouldn't just disappear into the ether. I vaguely remember the model supporting ownership by group (not handled the same way) but it's been a very, very long time and I am probably misremembering.
At first I though site ownership would be to allow anyone to be able to read/write to that album but then realized that it was intended as you describe. From what I've seen only gallery managers/admin can write items to a site owned album. I did my best to verify behaviors on a test smf 2.0 site with levgal and compare the interaction with the elk version.
I know I specifically built it to support multiple shared ownership at the account level, and/or ownership by a single group. I'm not sure what you'd need to change there unless you wanted to allow owner-by-multiple-groups and even then I think there might be easier ways to do that by expanding the block of data for album ownership rather than trying to repurpose owner id - again if memory serves. The main drama of multi ownership is the fact that multiple owners imply multiple hierarchies in which an album can live, something coped for with multiple account owners, but not group owners.
What I did was add group 0 to the allowed owner group list, My though was I did not see a way to have an album that any "registered" members could read and write to. One could add all valid members to an approved group, or if using post count groups expose those group names, but that IMO starts to get a bit overwhelming for a typical user. Perhaps another way would be to have a simple join/request group for that. I'm not sure one would really want an open album like group 0 membership implies.
The only permission item/group I changed/add was allowing the selection of group "0" to allowed ownership groups. I have not centralized that update just yet. I added first to see how many times empty() would poke me and that change was also the cause of the error @badmonkey reported as I sorted but did not keep the keys intact
In the original model, 0 for ownership was for 'site ownership' so that if people deleted accounts or left groups, the content wouldn't just disappear into the ether. I vaguely remember the model supporting ownership by group (not handled the same way) but it's been a very, very long time and I am probably misremembering.
I know I specifically built it to support multiple shared ownership at the account level, and/or ownership by a single group. I'm not sure what you'd need to change there unless you wanted to allow owner-by-multiple-groups and even then I think there might be easier ways to do that by expanding the block of data for album ownership rather than trying to repurpose owner id - again if memory serves. The main drama of multi ownership is the fact that multiple owners imply multiple hierarchies in which an album can live, something coped for with multiple account owners, but not group owners.
Last post by Spuds -
There will be an official announcement and release. Since the patch is large I wanted to get a little wider testing, so thats why I've been posting updates here. Should be released soon since it seems to be running fine.
Last post by Spuds -
Yes 1.1.6 will throw some depreciation notices with 7.4 but will work. 1.1.7 will clean those up, you can install 1.1.6 then patch up to 1.1.7 using the patch here: https://www.elkarte.net/community/index.php?topic=5914.msg42405#msg42405 Its not the final 1.1.7 but its 99% of it. Final should be very soon now.
