Community @ The Turning Gate

When you add a package to your cart, the items in the package are added but not assigned to specific photos. What you are seeing is placeholders. The thumbnails will be visible once the customer assigns products to the items int the package.

Hi Stefan, TTG BE requires that your server have these three standard modules enabled:

PDO
pdo_sqlite
sqlite

It looks like at least one of those isn't enabled.  I suggest you contact your host's technical support and request these three PHP modules be enabled.  Can you provide a link to your site, so I can try to work out which of those three is missing?

We have made a silent update to the Publisher that works around this issue. If you download the publisher files again (with the 203b zip file), then replace the ttg-be/publisher/application directory.  After doing so, visit the Publisher Dashboard, and click on the link 'Update Album Files'.  This copies over an updated copy of lib.php to every album you have.  The error should then be gone.

Hi Morten, I'm glad that worked.  Curiously, 'é' represents é, and not the apostrophe.  Could you have entered that by any chance?  gallery.xml is created by Pages, to communicate to Publisher the link and name to the page linking to the top of your galleries.  With the configurability of Pages, without this file Publisher wouldn't be able to figure out how to reach that link.  For example, it could be 'Services' and services.php, or 'Home' and index.php.  gallery.xml communicates that.
XML formats require special markup for special characters. 

The solution will be for Pages to wrap the value in a <![CDATA[ … ]]> tag.  We won't be able to do that soon, as it requires a change to Publisher before the change can be made to Pages.  So we'd be looking at the version of Pages that comes after the next Publisher update.

Having said that, does it actually say <name>foto&acute;s</name> in the file on the server, or is there an apostrophe there?  I'm seeing different things in different browsers, and can't tell whether the browser is trying to be smart with the apostrophe.

Hi Chris,  thanks for the feedback on this.  I'll try to replicate the issue, and make a fix if I can.  If it's not confidential, can you message or email me the galleries and login so that I can at least try to see the issue on your site?

I'm not happy with the multiple cookies and hope to change the mechanism so that the locks are stored in a PHP session instead.

Hi Chris, my thinking behind updates with letters behind them is that the fixes are unimportant to the vast majority of users.  We want to avoid giving you upgrade fatigue.  The only change of significance with 203b is a workaround to avoid an issue with the open_basedir restriction that has affected two or three users.  If you hadn't experienced that issue (which would be obvious to find, as it raises errors directly into the browser) then there's no need to update the files.
When 2.0.4 comes out, I'll update the changelog with a list of changes between the initial 2.0.3 files and 2.0.4.  At that point we'll also announce the update and recommend all users to update their files.

As well as what Jim said, it may help to republish the photos in the gallery.  If the thumbnail sizes don't match between the old and new templates, then the design may break like this.  Make sure that the 'push metadata' publisher option is *not* set before republishing.

We use the full list of timezones that PHP understands.  Have you been able to work out which city corresponds to the timezone you're in?

Also, that last message doesn't sound good.  It means the hard drive is full.  That's something you'll need to take up with your host's technical support.

TTG BE requires the following modules to be enabled for PHP:

PDO
sqlite
pdo_sqlite

It looks like pdo_sqlite hasn't been setup.  I suggest you contact your host's technical support and ask them to enable the pdo_sqlite module.

Hi Al, we aim to be compatible with all PHP versions from 5.2 onwards.  The newer versions include features that aren't compatible with the old, however we play it safe by only coding to feature available in all of 5.2, 5,3 and 5.4. 
It's more likely that the configuration of the server you're using has changed with the move to 5.3.9.  PHP is unique (but not in a good way) in that the way the language operates can change depending on the configuration of the server.