Community @ The Turning Gate

Support community for TTG plugins and products.

NOTICE

The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.

This forum is now closed, and exists here as a read-only archive.

  • New user registrations are disabled.
  • Users cannot create new topics.
  • Users cannot reply to existing topics.

You are not logged in.

#76 Re: CE4 Publisher » Small annoyance/feature request » 2015-03-27 02:33:32

Rather, you should look into our custom thumbnail support in CE4.

That could work in some instances. However (and it may be something I don't understand), what I thought was a pattern of nested auto indexes breaking thumbnails, is actually something else. I'll start a new thread so as to help some one else if they run into it.

#77 CE4 Publisher » Small annoyance/feature request » 2015-03-26 08:54:38

scottfrey
Replies: 9

Publisher creates Thumbnail (and other directories) on the server as 755. Owned by Apache, with the group being Apache.

Is is possible to have publisher set permissions to 775 so that (via ftp) I can modify the contents of directories (my login is part of the apache group)

This is kinda important when creating nested published albums, as it is necessary to manually add thumbnails to the parent thumbnails directory (assuming there is no way to have auto index traverse each directory looking for thumbnails). Or when publishing panoramas when one needs to delete one thumbnail

#79 Re: CE4 Publisher » Small Bug » 2015-03-18 07:50:28

any further progress on this?

#80 Re: CE4 Auto Index » Minor but annoying issue » 2015-03-12 03:21:16

I find the fade works really nicely when the album description displayed in the auto index is of the same text appearing in copy on the gallery itself.

Agreed, that's How I do it smile

It would be awesome if the "page copy (md)" field of the Page Content tab would pre-fill from the "Title" and "Description" fields of the Base Settings Tab as:

##[Album Tittle]
[Album Description]

Then I would not have to copy and paste so much wink

Please consider that a feature request (or perhaps a button to fill it in, or "leave blank to use Album Title and Description")

#81 Re: CE4 Auto Index » Minor but annoying issue » 2015-03-11 08:39:57

That's the right answer!:

.album-title {
     font-size: smaller;
}    
.album-description {
     font-weight:  lighter; 
}    

added the font weight tag. Put the height back to 100

#82 Re: CE4 Auto Index » Minor but annoying issue » 2015-03-11 06:27:40

Adjusting from 100px to 104px seems to have worked around it.

Some descriptions are going to be waaaaay too long to accommodate by making the height tall enough to accommodate the whole thing. The fade is a really elegant solution BTW

Another way would be to have the Album Title and Album Description be the same size font, but I haven't figured out where that is set yet...

#83 CE4 Publisher » Stack Overflow? » 2015-03-11 06:24:25

scottfrey
Replies: 3

Any idea what would cause this repeated error dialog?

MetadataHandler.lua:2155: C stack overflow

When publishing

#84 CE4 Auto Index » Minor but annoying issue » 2015-03-10 13:31:46

scottfrey
Replies: 6

I like the new fade text, but...

If your album title breaks to two lines, it looks really bad. Can there be some logic in where the fade starts if there is two lines?

see: http://www.lightsmithy.com/collections/

#85 Re: CE4 Publisher » Small Bug » 2015-03-10 07:40:53

If you were to export both files to disk as JPEGs, how does Lightroom manage the names so that they're distinct?

Lightroom appends _1 to the end as 20150221-IMG_0416.jpg and 20150221-IMG_0416_1.jpg

I notice that photoshop appends "copy" to the name (or lightroom does on export)

#86 CE4 Publisher » Small Bug » 2015-03-10 06:55:59

scottfrey
Replies: 4

I've run into a small, but repeatable bug.

in using Onone's perfect effects, I've managed to create several instances of files that have the same name and different extensions. For example 20150221-IMG0426.dng and 20150221-IMG0426.psd (the psd is a gritty black and white)

If I publish both images, Publisher publishes two copies of the psd, and ignores the dng. If I export the gallery, Lightroom correctly exports both the dng and the psd.

If I make a virtual copy of the psd, ( so it becomes 20150221-IMG0426.psd/copy 1) it publishes correctly.

The same behavior happens if I have 20150221-IMG0426.psd and 20150221-IMG0426.tif, it publishes 2 copies of the tif.

I DOES NOT do this when creating duplicate names using "edit in photoshop", so it is something with the way Perfect Effects creates duplicates. Perfect Effects is available for Free at the moment: http://www.on1.com/products/effects9free/

It also does not do this when publishing to Facebook (correctly publishes both files to Facebook), so I am assuming it's something the TTG publisher's code

#87 Re: CE4 Publisher » Best practices for upgrading from CE3 to CE4 » 2015-03-07 08:35:22

you'll need to update each instance separately. the migration tool requires you to select a source and destination Publisher instance

So I will need to set up the three new instances of CE4 first. Then just migrate each instance as a separate task.

When I went through my CE3 -> CE4 transition, I first developed the new CE4 site in a sub-domain. .....

After all that was in place I ran the CE3 to CE4 Publisher migration tool.

Thanks, that is very helpful. I'll stick with a path that works.

Since I created new publisher templates with new names I needed to go through each album and album set in Publisher and assign the new templates. But that only took a few minutes. It all went very smoothly.

I really can't see a way around that. Unless you had named your templates something really generic. Which seems rather problematic.

#88 Re: CE4 Gallery » Masonry, Elastic » 2015-03-07 08:25:55

Thanks! That was it.

Now, is there a way I can make a plugins.php change that will override that (else I have to edit the code with each update)

I know that Masonry relies on Javascript, which can tax resources (this is why you see huge galleries that use Masonry take a long time to load). Perhaps this is why the standard gallery is fed to mobile devices: because of limited memory or other resources.

That and Matt believes iPads should be mobile devices (we've had that discussion before). I disagree on this point (and the mobile menu now solves most of his very valid objections). I get very offended when my iPad is trapped in a mobile site, that is probably a character flaw on my part wink

iPads can handle it, I've been running my CE3 site that way for a while, iPad 2s handle it fine

#89 Re: CE4 Gallery » Masonry, Elastic » 2015-03-07 05:10:45

That's kinda my point, iPads should not be treated as mobile devices (IMHO). How do I exclude iPads from getting redirected to mobile.php? (even at the expense of the new, nicely done mobile menu if nessessary). Something triggers the redirect. It's not width (though that would be nice)

#90 CE4 Publisher » Best practices for upgrading from CE3 to CE4 » 2015-03-07 05:07:51

scottfrey
Replies: 3

I am currently using Pages, Publisher,Stage and Autoindex. on CE3

I've purchased and will be upgrading all those, and some time in the future, moving to Wordpress for most of Pages functionality, but not yet.

Also, I have three instances of CE3 Publisher pointing at three different top level directories (Portfolio, Collections, NSFW (which is a separate Lightroom catalog))

What is the best order to do all this in?

I've made a new gallery template, and installed publisher (in the Docs, I am to the point that I run the upgrade tool). I assume I should setup Autoindex in my top level folders (before running the upgrade tool), then promptly run the upgrade tool. How does the upgrade tool deal with multiple instances? Do I just run it once for each instance?

Instead, should I setup and export Pages first? (which would install auto index)

The upgrade instructions could be a little more clear on best practices

#91 CE4 Gallery » Masonry, Elastic » 2015-03-07 03:34:06

scottfrey
Replies: 5

What setting do I need to change to retain the masonry grid when viewed with an iPad? (rather than the mobile grid)

#92 Re: PHPlugins (CE4) » Missing /lib/autoindex/ » 2015-02-28 00:51:53

Indeed it is that simple. One should not muck about with code late at night

#93 Re: PHPlugins (CE4) » Missing /lib/autoindex/ » 2015-02-28 00:48:08

Is it as simple as taking the autoindex folder from 'sample auto index export'/resources/autoindex and putting in it /lib on the server?

#94 Re: PHPlugins (CE4) » Missing /lib/autoindex/ » 2015-02-28 00:40:07

I will have Pages, but it seemed appropriate to develop a single page first. Since installing pages with unfinished (i.e. non working menus) would break my current site.

I will use CE4 pages to start with, then covert over to wordpress 'page' eventually. I was intrigued by Matthew's "published galleria" home page and want to use that.

I was unable to find installation instructions for Autoindex in the docs. Also unable to find any lib folders that contain autoindex.php in order to modify the code... in other words, I've nowhere to point it to.

#95 PHPlugins (CE4) » Missing /lib/autoindex/ » 2015-02-27 16:28:09

scottfrey
Replies: 5

Trying to get site wide auto indexing multi-level menus working and failing

When I enable that section of menus in plugins.php, I get a page that stops loading right at the auto indexing menu. I suspect the culprit is:

require_once($theroot.'/lib/autoindex/autoindex.php');

as I don't have a /lib in the site root. I am unclear how to get it there. Exporting an Autoindex web page does not create it. It isn't in the zip file.

CE3 referred to the resources folder

require_once($theroot.'/resources/autoindex/autoindex.php');

which I am assuming is replaced by the /ttg-be folder, but there is no /lib folder in there (and the path would be wrong in that case)

I am probably missing something obvious... but what and where is the /lib folder I should upload?

(I have not run the migration tool yet, as it would seem that it needs a CE4 template to work from)

Board footer

Powered by FluxBB