Community @ The Turning Gate

Thanks, Mark.  I can see the problem on my test server and will work on a fix for this.  In the mean time, is there a button at the bottom of the page called "'Update All Modules"?  Can you try that and see whether it completes the upgrade?

I'm not sure how that would have come about.  Can you visit Designer > Pages, click on the name of the page you want to load on your home page.  Click Edit Properties and set Index Page to 'yes'.

Hi Nico, thanks for pointing that out. Assuming Backlight is actually immediately under the top of your site, then the double slash is nothing but a superfluous slash. I'll look into it.

Hi Jan, his is another issue for your host to fix. When files are uploaded they are initially saved at a location configured by your host. It is that location or the permissions configured by your host that is causing the error. We have no control over this. All Publisher does is take those files and move them to a location within your website.

As the developer of the LR plugin, I think it’s a limitation in how our code works with the Lightroom SDK (software development kit). It’s been a long time since I looked into it so I’m not completely sure of the following cause. Lightroom’s publishing system wants to create one rendition per photo, and when it does it that way, the chain of other plugins get called. Our Publisher creates its own order of doing things so that we can generate multiple renditions per photo. That breaks the way that Lightroom would then interact with other plugins.
It was necessary to build it that way so that all the renditions of each photo could complete before moving to the next one. Otherwise we’d have the case where all the rendition types for all photos in the collection would need to be created before doing that again for each rendition type. That makes for a poor user experience as there would be a long delay before any photos started to be marked as published, and also creates issues if publishing stops for whatever reason. You could end up with the situation of all of your photos only having some of their renditions published.

Hi Markus, v3 does not present the user with the “I’m not a robot” field. It determines whether the user is a robot by other means. If you do want that field then set up v2 instead.

We’ll be looking at an alternative to the small icon (a label and link to terms instead), but for now that icon needs to be there as part of the service agreement with Google. It’s added automatically.

Hi Jan, in case the problem as already been resolved on your server, with the error cached, can you try visiting Designer > Templates > Clear Template Cache ?

Hi Jan, there is a misconfiguration on your host.  The configuration is set up to try to write to a directory that the web server is not allowed to.  This is not related to our code.  Can you try talking to your host's technical support to resolve this.  Specifically, the error is:

open_basedir restriction in effect. File(/home/ucvhprxm/.php/php-mail.log) is not within the allowed path(s): (/home/ucvhprxm/domains/jcfotosite.nl/:/home/ucvhprxm/domains/include/:/etc/pki/tls/certs:/tmp:/var/tmp:/usr/local/lib/php/:/usr/local/php55/lib/php/:/usr/local/php0/lib/php/) in Unknown on line 0

It would be good if anybody experiencing this could check the network traffic via the Developer tools to see whether the images are being fully downloaded from the server.

Not what you are looking for, but I have put in a fix in our working code to stop the Hero section from displaying when a cover image is not set. With the current behaviour,  that means it will be disabled entirely in Search.

I'm glad to hear that. Errors in something your host had set in the.htaccess?

Hi Mark, thanks for the suggestion.  This is something we're looking into.  We'll need to see if it's possible without running into memory limits during the zipping process.