Community @ The Turning Gate

Still struggling and struggling, wondering if this client-response-thing will ever work, on any of MY providers, after so many hours and un expected fails.

Can somebody tell me if this PHP.INI suggestion

[[This entry in your own php.ini file may work:
mail.log = /dev/null
That sends any logging to the null device, effectively making it disappear rather than try to write to a file.]]

could also be applied to .htaccess in case users have no access to the PHP.INI ? And if so, what would be the right syntax?

Ah..well...Easter it was... behold, there's cause for celebration of the resurrection

First of all: many thanks for all your feedback.
I've been out for a few days, came back today and found the error miraculously gone - for now
No word from any helpdesk/provider etc.

Since this remains as much a mysterious as a recurring problem, I thought I'd add some more technical information from the PHP-corners of my site/host hoping that you "cracks" might discover some trace of a structural solution.

However, I cannot find a way to upload my screenshots to this forum.
Anyone?

Yes Daniel, that is very true.

All more of a shame that the same problem unexpectedly keeps coming back and every (!) hosting provider has the same reaction: it's not our fault, contact your software coders. From pillar to post, so forgive if I don't quite see where reporting gets us.

Hi Matt,
Since yours is - as far as I know - the ONLY solution for self hosted Client Response interaction, I very much welcome enhanced attention for documentation. The YouTube suggestion is fine of course, but as a not too regular "back end" user (if it ain't broke....) i find step-by-step tutorials in a more static form much more useful. For the same reason I was/am still unhappy that there is no (!) way to generate a printed/pdf version of the current documentation. Some of us still happily use or need (some) paper with jotted exclamation marks in order to learn from our mistakes...

Extending the search capabilities (with targeted results in stead of too full text) and hyperlinking inside the documentation would save very much time and effort.

I have been using TTG solutions since before you came up with its beautiful, Korea inspired name, and in spite of all tech giants trying to make our life easier, many of your solutions are still one of a kind. Tutorials and better documentation however would doubtless draw many more clients who are fed up with the big company's inflexibility and lack of customization options. Maybe your first target in the past was the professional photography community to which I do not belong, which in practice means that for lack of routine I every once in a while face the need to re-invent the wheel for my (new) sites. As a final remark in this context I would point to a number of reviews and comparisons where a degree of un-intuitiveness was associated with TTG's ever evolving solutions. Although I think there would historically be logic in that, I agree that there's room for improvement here.

I hope this will help in some way. You did ask for it....
Cheers,

(another)Michael.

Wow, that was fast.

Yes, I do very much hope things get easier, because what I saw on your test site makes me quite jealous.... I hope there will very soon be template files to share.

One thing was left over from my previous post: how to customize my website with a header, a logo, a background picture or canvas?
Using a template would make such changes appear on each and every page of my site, wouldn't it? So should I edit a page made from a template then, if I e.g. wanted to use a different backgroud (color/image) on each page?
I'm sorry but things are still confusing as "in the old TTG days" all such options were very clearly layed out within the Lightroom web module.

Hi Rod,
Thank you for this swift reply. The point where you elaborate on the template function is very helpful. I had no idea that there was to be an order in which to use them. The term album is confusing as it sometimes means a group of pictures, and sometimes the page where such a group is shown. Or am I wrong here.

No, I was not referring to any CE4 material, but talking within BL. Suppose I start of making a site with the default templates, all pages would derive their settings from them. Clear! However, when I change the template I used afterwards (!) and/or make a completely new template and assign that one as my default.... what happens with the pages already existing (based on the "previous" default).
Maybe, just maybe it would be a good idea if someone made a few drawings/illustrations of these relationships.