[Kde-imaging] [Bug 277661] New: KIPI facebook exporter incompatible with Firefox 4 (solution: use .html extension not .php)

[Richard Neill]

https://bugs.kde.org/show_bug.cgi?id=277661

           Summary: KIPI facebook exporter incompatible with Firefox 4
                    (solution: use .html extension not .php)
           Product: kipiplugins
           Version: 1.9.0
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: Facebook
        AssignedTo: kde-imaging at kde.org
        ReportedBy: kde at richardneill.org


Version:           1.9.0 (using KDE 4.6.3) 
OS:                Linux

If I export from Digikam to Facebook, then the first time I do this, KIPI
creates a local temporary file   /tmp/xxx.php  and launches the default web
browser. This is supposed to trigger that web browser to sign into facebook and
install the KIPI import/export app.

If the kde-system-default browser is Firefox 3.x, this works. It also works
fine with Konqueror. However, for Firefox 4, it is broken.

Firefox 4 throws the user a message saying it doesn't know how to open files of
type PHP.  While this is irritating, it's technically correct: a file:// URL
with a local file ending .php  has no web-server to inform firefox of the right
Mime-type. So Firefox asks the user what to do with it, and (of course, refuses
to open it with itself).

The workaround would be for digikam to generate a file ending in .html

Reproducible: Always

Steps to Reproduce:
1. Start afresh with a new facebook account (or at least without the kipi
import/export app installed), and have kde's default browser be firefox.

2. Export some photos to facebook with digikam. 

3. Firefox will refuse to open the local file.

Actual Results:  
Firefox puts up a prompt saying "You have chosen to open xxx.php..... what
should Firefox do with this file". 

Expected Results:  
Firefox should open the file and then process it.  Although Firefox is being
apparently stupid here, I believe that Firefox is correct, albeit pedantic.



The file that digikam generates is an HTML file. Use the .html extension for
it, rather than .php.

A simple test case is:

  echo "hello" > /tmp/test.php
  firefox file:///tmp/test.php

which fails (but works if it's /tmp/test.html).

I'm filing this under "crash" severity because the effect is to totally break
the system, even though, technically it doesn't segfault.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.