I've generated my list of 1000 passwords.... When compiling, do I have to tick "Password Protection" for every page, or can I protect the whole book by just protecting the index.html?
Posted on: 4:56 pm on September 16, 2006
Storyman
Unfortunately you have to either select all pages or pages individually. You might try a short cut by selecting ALL, then go back and unlock specific pages.
Starting with the FILES tab these are your options for changing the password protection:
Double click a file and either check or uncheck password protection.
Right click a file. In the pop up window select the desired attribute.
Select the file, then from the men EDIT -> FILE. Check or uncheck password protection. There is also have the option to select all of the files for protection.
Unfortunately, CTRL/SHIFT selection does not work when selecting files in the FILE tab.
[RiffRaff, I realize that this may be more information than you requested. Please understand that although it may not be of a benefit to you there are others who will be asking a question similar to yours and it is for those people the additional information is included.]
Posted on: 7:09 pm on September 16, 2006
RiffRaff
Understood - ta very much. Excellent as ever, Storyman!
Posted on: 7:57 pm on September 16, 2006
rlemire
If I could interject a comment: I'm guessing, but I think Storyman was focused on the physical act of selecting password protected pages rather than the protection process.
I'm sure Storyman would agree that it is possible to protect the whole eBook using one password protected page.
For example; if you have designed part of your eBook to act as a "demo" version, then -- to access the "Pro" section, a customer would have to click a link to the first page of the "Pro" password protected area.
You would only need to password protect the first page of the "Pro" section. Provided of course that there was no access to the "Pro" section except through the first "Pro" page.
It should also be possible to protect the whole book by just Password Protecting "index.html". However I can't be sure because I've never tried.
I do know you can protect the whole eBook by password protecting a page that comes after after "index.html".
Ron
Posted on: 4:08 am on October 1, 2006
Storyman
Hi Ron,
I see your point about not having a navigation of any sort and that would result in any pages after a protected page to be unaccessible. Interesting idea.
Of course if there is any navigation, like a TOC, then any page that is not protected is viewable.
Posted on: 8:57 am on October 1, 2006
rlemire
How's this for an idea? If you created your own TOC, one for the "free" section and a duplicate for the "pay to see" section. Then in the "free" version you could disable the links to the "pay to see" section.
Your customers could see the chapters they were missing and it would be more incentive to buy.
With any business, it is up to the individual owner of said business to ensure the success of the business. You may make more or less than any sample figures or results that might be quoted on our web sites or other publications. All business involves risk, and many businesses do not succeed. Further, Answers 2000 Limited does NOT represent that any particular individual or business is typical, or that any results or experiences achieved by any particular individual/business is necessarily typical.
Disclosure:
Our company's websites' content (including this website's content) includes advertisements for
our own company's websites, products, and services,
and for other organization's websites, products, and services.
In the case of links to other organization's websites,
our company may receive a payment, (1) if you purchase products or services,
or (2) if you sign-up for third party offers, after following links from this website.
Unless specifically otherwise stated, information about other organization's products and services,
is based on information provided by that organization,
the product/service vendor, and/or publicly available information - and should
not be taken to mean that we have used the product/service in question.
Additionally, our company's websites contain some adverts which we are paid
to display, but whose content is not selected by us, such as Google AdSense ads. For more
detailed information, please see Advertising/Endorsements Disclosures
Our sites use cookies, some of which may already be set on your computer. Use of our site
constitutes consent for this. For details, please see Privacy.
Click privacy for information about our company's privacy, data collection and data retention policies, and your rights.
