Community @ The Turning Gate

An explanation on the above:

Publisher tries to add an album on the server if it's found not to exist at the time of publishing photos.  Since the Default Album wasn't setup through the usual Publisher 'Add Album' process, it doesn't have a slug.  The server detects this and attempts to throw an error.  Unfortunately, that part of the code tries to reference a file that doesn't exist and instead returns errors that aren't intended for human consumption.  This error handling has been fixed in my working code, so at least should provide a more meaningful message in the future.  Ideally we'd have the Default Album not exist, so that this problem couldn't arise, but that's something Lightroom creates on its own.

Hi Martin, glad to be of help.  That register_globals error is raised by phpLiteAdmin, which isn't TTG code.  Still, it's always safest to have register_globals disabled.  Depending on how a site is coded, with register_globals enabled, a malicious user could try to set a server-side variable by passing it in the URL, e.g. yoursite.com/?logged_in=true. 

Removing albums alone may not fully clear-up the database.  Each album has a set of photos.  Each photo has a set of renditions and metadata.  So if just the albums are removed without the related photos (and subsequently related renditions and metadata), then there will be orphaned data in the database.  It's not likely to cause a problem, but it's worth keeping in mind.  In any case, if you're delving into cleaning up the database to any significant degree, I strongly recommend that you first make a backup of ttg-be/data/publisher/master.sq3, so that you can restore it if needed.

Here's my tip to improve search time:

1) Login to TTG BE as full admin
2) On the TTG BE Dashboard, click 'phpLiteAdmin' under 'Special Links'
3) Enter the additional password of 'admin'
4) On the left-hand side, click 'publisher/master.sq3'
5) Click on the SQL tab
6) In the large text area, paste the following code:

drop index photo_metadata_name_index

7) Click 'Go'

I can do the above for you if you find those steps are intimidating.  In that case, please email or message me your TTG BE admin login.

An explanation of the above: Database indexes are used to speed up queries on fields that are frequently searched.  The index that we're removing was meant to speed up searches for metadata named 'caption'.  Unfortunately, in this case, the optimisation had the opposite affect, and drastically slowed down queries for captions.  I am assuming this is because indexes work best for unique values (such as the name holding email addresses), and not for repeated values, such as the name being 'caption', which are far from unique.  While each photo has a unique ID, every photo has metadata named 'caption'.  The index just doesn't work well in that case.

Note that the removal of the index will be included in the next Publisher upgrade, due in the new year.  So if you don't remove it now, it will be removed when the Publisher is updated.

Hi Martin, the backslash you are seeing is called an escape character.  It is used behind-the-scened to correctly pass a forward slash between the Lightroom Publisher and the publisher code on your server.  There's nothing amiss here.

I'm glad to hear.  It's rudimentary because that is only one of several scenarios the cart pricing needs to handle.  It needs to be checked with orders that do and don't include shipping, and those that tax and don't tax shipping amongst other scenarios.  Other components affected include the price appearance in the purchase dialogue, the total given in the widget, and those in the order emails.  Also, the labelling needs to be changed through several areas, and localisation of those labels needs to be added in.

Hi Juergen, this is not an advertised feature and I had not anticipated that it would be stumbled upon prior to purchase.  The setting was added in anticipation of the feature, since having the setting already in the database makes the upgrade smoother when the feature does get added.  I will get back to working on back taxes, hopefully for a cart upgrade either late this year or in early January.

Antagonising the mods is not helpful.  It is not possible to tailor the email text for different products.

Hi Rod, the function had been there all along, but only documented recently.

Hi Kris, I have fixed the cart for you.  The problem was that you had version 3.0.3 of the cart installed.  It's now running 3.0.5, which is compatible with the latest Gallery plugin.

A couple of other points to note:
* The version of the cart still shows as 3.0.3 for me, since the process to complete the upgrade will only occur after logging in as full admin.  In the case of 3.0.3 to 3.0.5 this completion is nothing more than updating the version number.
* Your old cart files are in cart_303.  Once you're happy with the cart, you can safely remove this directory.

Hi Fabian, so is it all working now?  If so, that's great.  Let us know if you're still having issues.

Hi Stine,  you're running an older version of the Cart (3.0.1).  The current version is 3.0.5 and includes a fix for the issue you've encountered (fixed in 3.0.2).  To upgrade from 3.0.1 to 3.0.5, download the latest zip file, and perform these steps:

• Replace the ttg-be/cart/application directory

• Replace the ttg-be/cart/lib directory

• Login as admin to ttg-be/cart/admin

There is a work-around to change the "digital download" back to a virtual product.
Edit the product and force it to have an error upon submitting the form.  One way to do this is to clear the text from the Title and attempt to click Save Product.  From there, you should have access to a drop down for the product type.  Set it to virtual, type the correct Title back in and click Save Product.  You may also need to enter the Download Directory again, which is typically photos-for-purchase.

(this process of being able to edit the Digital Download is itself the bug that allowed it to be accidentally changed to Physical in the first place.  So it's using the bug to fix the entry caused by the bug).

Thanks for the link.  What's the username and password?

Without having seen the gallery, I see that it was generated with Gallery 6.0.4.  The latest version is 6.1.2, with several bug fixes and improvements made since 6.0.4: http://ce4.theturninggate.net/docs/doku … _changelog

Try updating Gallery and re-exporting your gallery to see whether that fixes it.  Also make sure you are running the latest version of the cart (version 3.5)