two solutions for that
- just hide them in the menu bar / index page
- have them appear in the "forbidden categories"

I'm not sure which one is the "best". Which one do you prefer ?

+1


But we can link a picture to a ping-pong category as well.
For HTML, we can use Extended Descrition and in the picture name we can mark it <!--hidden-->
So there is a bypass.

plg wrote:

I'm not yet ready to say "no content => make the category as forbidden".

As a heavy user of [extension by Piwigo Team] Extended Description, I've asked grum to give me his opinion concerning an empty category only to give a description (it's a [extension by P@t] Additional Pages job in my opinion, but when I see such a page made with [extension by Piwigo Team] Extended Description, I wonder if [extension by P@t] Additional Pages could have done it as well/simply)

My concern is also about the API. pLoader calls pwg.categories.getList, if we consider a category is invisible as long as there is no photo inside, there is a problem. If the API doesn't take this constraint into account, it's also a problem, since the API is public (you would see more categories with pwg.categories.getList than you can see by browsing HTML pages).

My current state of mind is "let's make it simple : no content, hide". And pLoader will have to change its way to retrieve the category list (this problem is minor compared to the one described in this topic).

About this page, I think I have to give some explanation.
My gallery have this structure :

--[Randonnées & vacances]
    |
   +--[#151:Patagonie]
         |
        +--[#153:buenos aires]
        +--[#152:perito moreno]
        :
        +--[#160:Sixième jour de randonnée ]


As you can see, the category #151 [Patagonie] have sub-categories.
Each sub-category have the <!--hidden--> tag in title, interpreted by [extension by Piwigo Team] Extended Description as "don't display them in the parent categorie page". As you can see on picture #2, theses sub-categories are always visible in the menu.
You can also see in the picture #1 the sub-category "Buenos Aires" inserted with the [cat=153] tag have 4 pictures.

Inside each sub-category, you have public pictures, so if you go in the sub-category, you can see them (picture #3).

So, for piwigo, all the pictures are visible (no privacy levels or no right management with the user/group permissions). The only reason why they are not visible is because [extension by Piwigo Team] Extended Description make them not visible (the plugin remove theses items from the template data before Piwigo process the template).


So now, why I don't use Additionnal Page to make this page ?
For many reasons :
- AdditionnalPage allows to add a page"outside" the gallery, but in this case I want this page inside the categories tree
- I want to make a 'travelbook' with some pictures to illustrate, and I want also direct link to all the pictures (I don't want to display all picture in the 'travelbook')


Another example on this page : http://photos.grum.fr/index.php?/category/251
I want to display some pictures ("affiche", "ticket d'entree" and all goodies) on the catgeory page on a specific place, and not with all the picture of the category.
But when I click on theses specifics pictures, I want to see them in the category with all other picture : so, I put the <!--hidden--> tag on the pictures title, [extension by Piwigo Team] Extended Description make them not visible, I add the [img=5763.251 5770.251;name] tag to tell [extension by Piwigo Team] Extended Description display them where I want, and the picture is visible with a classic URL http://photos.grum.fr/picture.php?/5763/category/251



I'm not sure my explanation are very clear ^^ but to answer the question, I think an empty category (empty because of the privacy levels or group permission or no picture) don't have to be visible and accessible by a visitor => this is not a problem to make pages similar than mine ;-)

plg wrote:

So as far as I see it, let's make it simple: for a given user, if a category doesn't contain any photo (with recursivity) then it should be added in the forbidden category list.

rvelices do you take care of it? (or do you prefer I implement it?) On my side, I'll prepare changes for pLoader/API considering that pLoader currently call pwg.categories.getList.

[Bugtracker] ticket 1053

I'll do it; it's quite easy if I remember well the code. I think it is better if we apply this feature only for non admins. Like this your pLoader will work fine and the admin will still see that some categories without images are there ...

plg wrote:

Thank you rvelices, I've made some tests on [Subversion] r3622, I don't see the empty categories anymore :-)

I've seen a strange behavior: if I set category as private, if a user with no permission tries to get into it (by setting the id directly in the URL), he gets a permission error and an invitation to connect. With the "empty implies forbidden" feature, if he goes to the category, he can see the name and its description, the category is just empty.

it was a bug it is corrected in [Subversion] r3640 and [Subversion] r3641

Hi

Is it possible to manage this evolution with 1 parameter?
In my case, i need that people connected (through web site or ploader) could see all existing categories?
Thanks
Tiico

plg wrote:

I know this problem. I haven't solved it yet unfortunately. As a consequence, [extension by plg] Community + Piwigo >= 2.0.4 => when a non-admin user creates a category, it automatically disappear :-/

[Bugtracker] ticket 1431, will be fixed in Piwigo 2.0.9