Community @ The Turning Gate

OK. My message was posted before I could read your last one.

When I purchased the Galleria add-on, there was no mention of the Pangolin page template being required. So, I have to re-design the whole album set, which is not what I expected.

OK, Rod.
Thanks for the quick reply.

I'm still wondering why this problem still occurs randomly in Firefox only, whatever my settings. Here is a new example :

https://dl.dropboxusercontent.com/u/554 … roblem.JPG

Original page here :

http://www.ppphoto.fr/galleries/

F5 usually fixes the problem but this is annoying.

Hi,

The .htaccess file installed when I started with BL already contains such code

# ------------------------------------------------------------------------------
# | Web fonts access                                                           |
# ------------------------------------------------------------------------------

# Allow access from all domains for web fonts
...

Adding the code shown in the page pointed to by the above link while maintaining the existing code is certainly not a good idea (I tried) : after doing that, the Lightroom publisher plugin no longer works (all actions trigger an error - the plugin is no longer able to communicate with the web site).

I'm not familiar with the syntax used in .htaccess files so I'm wondering whether the existing code should be removed before adding the code suggested by the page mentioned above. Or is the mentioned post outdated ? Are these two pieces of code conflicting ?

Thanks.

==== Current contents of my .htaccess file ====== (this is actually the .htaccess file contained in the BL + Pages package)

# ------------------------------------------------------------------------------
# | Web fonts access                                                           |
# ------------------------------------------------------------------------------

# Allow access from all domains for web fonts

<IfModule mod_headers.c>
    <FilesMatch "\.(eot|font.css|otf|ttc|ttf|woff)$">
        Header set Access-Control-Allow-Origin "*"
    </FilesMatch>
</IfModule>

<IfModule mod_rewrite.c>
    RewriteEngine On

    ############################################################################
    # Edit this section for servers using FastCGI

    # For FastCGI (or seeing the error message 'No input file specified.':
    # add # to the start of the next line
    RewriteBase /

    RewriteCond $0#%{REQUEST_URI} ([^#]*)#(.*)\1$

    # For FastCGI (or seeing the error message 'No input file specified.':
    # add # to the start of the next line and remove # from the line after)
    RewriteRule ^.*$ - [E=BASE:%2]
    #RewriteRule ^(.*)$ - [E=BASE:]

    ############################################################################

    RewriteRule ^(.*)$ - [E=QS:mod_rewrite=on]

    RewriteRule ^([^\/.]*)-single.php$ %{ENV:BASE}single.php?%{ENV:QS}&id=$1 [QSA,L]

    RewriteRule ^([^\/.]*).css$ %{ENV:BASE}index.php?%{ENV:QS}&extension=css&name=$1 [QSA,L]
    RewriteRule ^([^\/.]*).js$ %{ENV:BASE}index.php?%{ENV:QS}&extension=js&name=$1 [QSA,L]
    RewriteRule ^([^\/.]*).gif$ %{ENV:BASE}index.php?%{ENV:QS}&extension=gif&name=$1 [QSA,L]
    RewriteRule ^([^\/.]*).png$ %{ENV:BASE}index.php?%{ENV:QS}&extension=png&name=$1 [QSA,L]
    RewriteRule ^([^\/.]*).jpg$ %{ENV:BASE}index.php?%{ENV:QS}&extension=jpg&name=$1 [QSA,L]

    #RewriteCond %{QUERY_STRING} !mod_rewrite=on
    #RewriteRule ^index.php$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]

    RewriteCond %{QUERY_STRING} !mod_rewrite=on
    RewriteRule ^mobile.php$ %{ENV:BASE}mobile.php?%{ENV:QS} [QSA,L]

    RewriteCond %{QUERY_STRING} !mod_rewrite=on
    RewriteRule ^(.*)download.php %{ENV:BASE}download.php?%{ENV:QS} [QSA,L]
   
    RewriteRule ^$ %{ENV:BASE}index.php?%{ENV:QS} [QSA,L]
   
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d

    RewriteRule ^(.*)$ %{ENV:BASE}index.php?%{ENV:QS}&page=$1 [QSA,L]

</IfModule>

Ben, Rod,

Yes, what I observe is consistent with what you explained. Thanks. Problem fixed.

Now back to a recent discussion about the lack of documentation in BL. Don't you think that these mechanisms should be explained in the documentation ? Ben, your post should obviously belong to the documentation (did I miss it ?). This would save time for both the support and the users. Currently, the documentation makes the assumption that everything about Publishing Services is known by the user. I guess that I'm not the only BL user (migrating from CE3 or CE4) who is using a publishing service in LR for the first time.

I did some further testing today :

1. I selected another image and modified some of the basic settings (Exposure, Contrast, Clarity,...)

2. I used the "Publish now" command and the image was not updated on the server (no export step in the history).

3. I tried again after disabling the "Push metadata without updating the existing photos" option. Same result.

4. I then modified the cropping for this image. This time, the image was updated on the server (export step visible in the history).

5. I made further modifications to the basic settings for this image and this time the image was updated on the server. I repeated the test and each time, the image was updated.

6. I re-enabled the "Push metadata without updating the existing photos" option, made new modifications to some basic settings and again, the image was not updated.

7. I disabled again the "Push metadata without updating the existing photos" option, made new modifications to the basic settings, re-published and the image was correctly updated.

So, it seems that there's an initialization problem with some state variable and also that there's something wrong with the "Push metadata without updating the existing photos" option (this has already been mentioned in another thread, by the way).

PS : How do I add an image to a post in this forum ? It would be much easier to show what's happening if it was possible to insert a screen capture.