php???

[crutledge]

I have just completed a complete re-build of my win 7 pro system.

When I try to download an ebook e.g. title.mobi or lrf or epub I get the following:

title.php

I have never seen this before.

Any ideas??

Charlie

[AnotherCat]

The only site I experience this is with the MobileRead library.

If you are using Internet Explorer try adding the problem sites to the compatibility list which worked for me.

[eschwartz]

No, if you are using Internet Explorer, DON'T!

If you rename the book, can you read it? It could be it just downloaded with the wrong filename.

[AnotherCat]

Originally Posted by eschwartz

No, if you are using Internet Explorer, DON'T!

If you rename the book, can you read it? It could be it just downloaded with the wrong filename.

If the problem is the previously mentioned on they are the correct format so no issue except for the filename.

Just because you hate IE doesn't make your shouting about it of any value to the matter, nor of any interest to those more open minded.

For the only naming instances I have come across it has been a server end problem. MobileRead was fixed once, but seems to have reverted again (there have been a number of threads about this over the last year or so). On another small site I use the epubs once started getting named as zips , the site owner corrected the problem immediately when informed of the issue, so was only fleeting.

As I say, it is just a case of adding the site to the compatability list where it will probably be lonely as of the many of the other sites I visit it is the only one non compliant.

[crutledge]

The problem was IE 11. I must have allowed an ie upgrade.

I reverted to IE 9 and things are smooth again.

[HarryT]

If you do have the problem again, Charlie, you can right click the download link, select "Save Link As" (or it might be "Save Target As") from the pop-up menu, and enter the filename manually.

Seems to be working fine in the latest version of Firefox, so it might be an issue specific to IE11.

[crutledge]

Originally Posted by HarryT

If you do have the problem again, Charlie, you can right click the download link, select "Save Link As" (or it might be "Save Target As") from the pop-up menu, and enter the filename manually.

Seems to be working fine in the latest version of Firefox, so it might be an issue specific to IE11.

I LOVE MICROSOFT.

[mrmikel]

The problem comes from allowing Active X Filtering (under Safety) to be active.
Under Safety, if there is check next to Active X Filtering, click on Active X Filtering and it will uncheck it and then mobileread and a number of other sites will work as expected.

It can disable a number of sites....but if you were to go to sites which were less trustworthy it might be worthwhile turning it back on.

[eschwartz]

Originally Posted by AnotherCat

If the problem is the previously mentioned on they are the correct format so no issue except for the filename.

Just because you hate IE doesn't make your shouting about it of any value to the matter, nor of any interest to those more open minded.

For the only naming instances I have come across it has been a server end problem. MobileRead was fixed once, but seems to have reverted again (there have been a number of threads about this over the last year or so). On another small site I use the epubs once started getting named as zips , the site owner corrected the problem immediately when informed of the issue, so was only fleeting.

As I say, it is just a case of adding the site to the compatability list where it will probably be lonely as of the many of the other sites I visit it is the only one non compliant.

I only hate IE because it does weird things which no other browser does. It is not a matter of MobileRead being non-compliant, it is Microsoft which doesn't follow the standards. According to mrmikel, it is the ActiveX part of IE that is causing it. A clear case of useless Microsoft "features" that interfere with what a browser should be doing. Do you realize that good web developers have to code two versions of their website, one for IE and one for "all other browsers"? And some just won't bother, and tell you to upgrade to a real browser.

Any problem which is only present in IE is obviously a problem with IE. This problem has yet to be reported (to my knowledge) anywhere other than in IE.

[AnotherCat]

Originally Posted by eschwartz

...According to mrmikel, it is the ActiveX part of IE that is causing it. A clear case of useless Microsoft "features" that interfere with what a browser should be doing...

In fact ActiveX Filtering is by default disabled in IE, it is the user's choice to enable it, should they wish to for enhanced security. If enabled it is the user's choice as to which sites it is enabled on. With IE 11 MobileRead Library has the same problem whether ActiveX Filtering is enabled by the user or not (in my case it is always disabled).

MobileRead Library is the only source of epubs out of the considerable number of sources that I use that has this issue (or, indeed, any issue at all).

The probable causes at the server end have been mentioned in several threads over the last year, at least. But, of course, only someone at the server end can verify if those are so or not. As a number of people have reported, switching to compatability mode, or for a permanent solution just adding MobileRead to IE's compatability list is an easy and seemingly reliable solution (or, of course, using another browser, none of which are perfect).

I would recommend that from a security point of view the OP is doing the wrong thing by reverting to the superceded IE9.

[eschwartz]

Originally Posted by AnotherCat

In fact ActiveX Filtering is by default disabled in IE, it is the user's choice to enable it, should they wish to for enhanced security. If enabled it is the user's choice as to which sites it is enabled on. With IE 11 MobileRead Library has the same problem whether ActiveX Filtering is enabled by the user or not (in my case it is always disabled).

MobileRead Library is the only source of epubs out of the considerable number of sources that I use that has this issue (or, indeed, any issue at all).

The probable causes at the server end have been mentioned in several threads over the last year, at least. But, of course, only someone at the server end can verify if those are so or not. As a number of people have reported, switching to compatability mode, or for a permanent solution just adding MobileRead to IE's compatability list is an easy and seemingly reliable solution (or, of course, using another browser, none of which are perfect).

I would recommend that from a security point of view the OP is doing the wrong thing by reverting to the superceded IE9.

And I personally find using Firefox gets rid of so many problems... especially on a fully functioning WinXP box.

I will second the warning about old versions of browser software. If IE11 is doing things wrong, the prudent decision would be to move to a better browser, either Firefox or Google Chrome.

[AnotherCat]

Originally Posted by eschwartz

And I personally find using Firefox gets rid of so many problems... especially on a fully functioning WinXP box...

Perhaps not after 8 April though, when a new set of security problems will be faced by XP users .

[AnotherCat]

Originally Posted by crutledge

The problem was IE 11. I must have allowed an ie upgrade.

IE11 was started to be pushed to Win 7 via auto-update about 2 months ago, so if you auto-updated, or else if manually updated you did not uncheck IE11, you would have ended up with IE11.

[eschwartz]

Originally Posted by AnotherCat

Perhaps not after 8 April though, when a new set of security problems will be faced by XP users .

And I have vowed to upgrade my mother before then.

Also note I didn't say ALL problems.