Community @ The Turning Gate

Thanks Rod.  I believe I followed the correct procedures.  I think it was a connection problem.

I'm moving to a new server with the SAME domain name.  I plan to copy the ttg-be folder, templates and auto-indexes and put them in the exact same place.  I don't want to waste time and bandwidth downloading everything, so I'm hoping Publisher will just connect and see that all the photos need republishing.  I don't use any plugins so that will make it simpler. I'll let you know.

Charles

You'll be happy to know I finally have this solved.  

My mistake number one was setting the top-level folder to photog/wildwood - but I assumed I had to do this for each level of auto-indexes when you said:

Mistake number two was missing the brackets in this line and just looking at the levels you created:

I was under the assumption that an autoindex should never be uploaded to anywhere other than the templates/autoindex folder manually via ftp.

So, I created an auto-index and manually uploaded it to photog/ which now will be the top-level auto-index, and I set the top-level folder in Publisher to photog/ so that now each Album Set will be an auto-index within that folder.  Only one instance of Publisher is needed.

Thanks for all your help.  Sorry about all the back and forth figuring this out.

Charles

Done.  It's always been there.

Not sure what this means.  I have to have my top level folder set to photog/wildwood - since that is the top of my catalogue within photog.

Problem for me is that I cannot get the auto-index to publish in photog/wildwood.  Maybe the pics below will help.

http://whatwant.ca/photog/WildWood/ttg.html

I had to use the link - for some reason the image tag doesn't work.

Thanks
Charles

Thanks Ben.  I haven't gone over this in detail yet, but at a quick glance I see you're going by the same assumption that Rod did which is that I want more Album Sets within each year.  This is perfect for "nature" etc. but to clarify, WildWood is just the name we use for our garden at home.  So WidlWood is the ONLY autoindex.  There is no further breakdown from there into albums because each year contains all the photos from that year.  I could break it down into months I suppose but that would require more click throughs.  I'll add more to this when I've studied what you've done.  So, I don't want Album 1, Album 2, Album 3 within each year.  That's where I ran into problems.

Hi Rod, Clearly, I'm confused by some of your advice.

The following comments assume that I'm using an instance of Publisher with the top level gallery directory set to photog/WildWood, because if I don't create an instance of Publisher with photog/WildWood as the top level gallery Publisher doesn't place anything in the WildWood folder because it's using photog as the top level and there is no way to tell an Album Set what folder to put itself in on the server.  (As I said somewhere else in this post if you could simply set the Album Set slug to "WildWood/WildWood-2014" you could use the default instance of Pubisher with the top level gallery set to photog - that would solve everything.)

I'm using "photog" instead of "galleries" so you're saying here  (I think) to make "photog" "WildWood" but I don't want that because there will be other top level folders as well (nature, zoo, etc.) 

Or, to create an Album Set within an Album Set - which doesn't work, it's creating the two levels of yearly folders (WildWood-2014/WildWood-2014).

In my tests these Album Sets show a connection to the autoindex that I have created in the Web Module and uploaded to ttg-be/autoindex/ when I create them (in the dropdown), but when I go to the index page's URL there is no index found.

This results in the two levels of yearly folders. This makes sense to me - I'm creating two levels of Album Sets so Publisher creates two levels of folders.  Anyway, it seems counter intuitive to have to create an empty Album Set for every year - just to place an Album inside of it.

I don't understand the connection between uploading an autoindex in the ttg-be/autoindex folder and the pics in the separate photog folder.  How does Publisher find the index.php file (and the rest of the files to display the index) for the appropriate autoindex when it's in a separate folder?  This works OK (for me) if everything is in the root photog and I only have one autoindex - but as soon as I create another level (Photog/WildWood) there is no connection between the autoindex and that folder.  I just get an error on the album index level. I just checked again, the site root of my autoIndex is set to http://whatwant.ca/photog/WildWood/ - and that is the correct upper/lower case structure in case my server is particular about that.

This is the current state of affairs.

Guest admin is enabled here: http://whatwant.ca/ttg-be/admin/

I have removed the autoindex in the photog/WildWood folder so you can see the 403 error (everything in photog is set to 777 and everything in ttg-be is 755) http://whatwant.ca/photog/WildWood/

The following is created in an instance in Publisher called WildWood with top level galleries folder set to photog/WildWood/

I've made an Album Set called WildWood 2014 with an Album inside it called WildWood 2014.  If you go to this page:
http://whatwant.ca/photog/WildWood/wildwood-2014/ - you'll see this error:
"Unable to find ./../../../ttg-be/publisher/application/../../templates/autoindex//setup.xml"
Because, as per the screenshot of how Publisher uploaded that Album it put it here:
http://whatwant.ca/photog/WildWood/wild … wood-2014/

I've made a second Album with NO Album Set called WildWood 2006.  This is where it should be:
http://whatwant.ca/photog/WildWood/wildwood-2006/
However, you'll notice that the "home" link in the Breadcrumbs is photog, not photog/wildwood/ and if you go to home that page is also a 403 error.

Charles
Have a good weekend.  I won't revisit this till Monday - it's only a personal setup so there is no rush to get it solved. Thanks.

Hi Rod,

I updated my post just as you added your answer, not sure if you saw my latest edit.  As you said here - I should create a new Publisher instance for WildWood so that's what I did.

But I have to use Album Sets because I want an Auto Index page at photog/WildWood.

I still don't get it - I want this:

whatwant.ca/photog/WildWood/
                                                  /2014
                                                  /2013
                                                  /2012 ...etc.

And I'm still getting this:

whatwant.ca/photog/WildWood/2014/2014
                                                  /2013/2013
                                                  /2012/2012 ...etc.

If I don't create a new instance of Publisher with the WildWood folder as the top level the Auto Index assumes that /photog is my top level and puts the index there.

I'm trying to make my top level folder 'photog' for all of TTG because there are other folders in that URL that are not photo galleries - so eventually I want the structure to look something like this

whatwant.ca/photog/WildWood/
                                                  /2014
                                                  /2013
                                                  /2012 ...etc.
whatwant.ca/photog/nature/
                                             /boulevards
                                             /butterflies
                                             gardens ...etc.

whatwant.ca/photog/zoo/
                                         /2014
                                         /2013
                                         /2012 ...etc.

So WildWood, nature, and zoo are all auto-index pages that contain the folders below them as individual galleries.

Currently I have "photog" and "ttg-be" as top level folders.  Should I put ttg-be inside photog? 

Thanks for the offer of Ben's help.  I think if I delete everything and reinstall ttg-be it will remove the reference to the missing folder.  At this point I'm still trying to setup the structure so I don't mind doing that.

BTW I've completely removed CE3 but the CE3 Publisher is still in LightRoom even though I used the LightRoom delete button to try and remove it.  How do I remove it?  (If you want I'll post this as a separate question.)

That's working now, thanks - and thanks for the hint to only publish metadata.

I got it, thanks.  I didn't need all the CSS in the arrow code so the complete final CSS is:

/* arrow colours */
.mfp-gallery .mfp-arrow-left:before, .mfp-gallery .mfp-arrow-right:before  {
    color:#647a53;
}

/* arrow shading none */
.mfp-gallery .mfp-arrow {
    opacity: 1; 
    text-shadow: none;
}

/* x window close colour */
ul li .img-close {
    color:#647a53;    
}

/*  x window close shadow none */
.img-close {
    text-shadow: none !important;
}

It's difficult to figure out that page code.  I was trying to use source code but it shows the thumbnail page with the js code for the popup.  The inspector is a big help but it doesn't stay focused on the page because it's a popup window.

Thanks for your help.

Thanks, that worked.  I also made the opacity 100% and removed the shadow using this:

.mfp-gallery .mfp-arrow {
    opacity: 1;
    filter:  alpha(opacity=100);
    text-shadow: none;
    }

One other related question, how do I do the same (100% and remove shading) on the close "x" button? (I added this to the question for further searches - hope that's OK.)