What Makes FrontPage Tick?

What Makes FrontPage Tick?

Submitted by sahdow on Thu, 2005-08-18 20:26.

FrontPage generates or uses a number of hidden files and folders to automate web development. These primarily apply to FP 2002 or lower, but when working on a site that uses the FrontPage extensions (contains themes, navigation buttons or other components), they are also used with FP 2003.

FrontPage Hidden Folders Defined
(These folders can only be seen when your web/site settings have been adjusted
to view hidden files & folders)

_overlay Overlay files for text on GIF and navigation buttons. These files are transparent GIFs that are overlaid on top of button or banner images to build a complete text on GIF or navigation button composite image.

_derived Files that are dynamically generated by FrontPage and that can be regenerated at any time, such as *.htx files created by the Search component and composite text on GIF images.

_borders Shared border definition files that are included in pages that use shared borders. (Top.htm, Left.htm, Right.htm, Bottom.htm)

_fpclass Compiled Java class files that implement some FrontPage-based features.

_themes Files used for each theme Themes storage. Each theme that is applied to a web is uploaded into a uniquely named subfolder of the _themes directory.

_private This folder is created in each FrontPage-extended web. It is intended to contain user files that are not viewable by a site visitor.

_vti_bin FrontPage Server Extensions executable files for run-time, authoring, and security functionality. On some servers, these files are not present.

_vti_bot Used for custom FrontPage-based components (WebBots) created using the FrontPage SDK. This folder contains the implementations of custom components. Custom components installed in these directories are optionally downloaded to the author’s machine when that component is inserted by the author.

_vti_cnf For each HTML page and graphics file in a FrontPage-extended web, there is a configuration file of the same name. Each configuration page contains a set of name-value pairs, identifying such things as the last author to edit a page or the editor associated with a file.

_vti_pvt _x_todo.htm Contains the current settings of the To Do list.

_x_todoh.htm Contains the changes to the To Do list.

_vti_map Contains image map files.

_vti_script *.idq Query files created by the FrontPage Search component when using Index Server on IIS.

_vti_txt This folder contains text indexes for the WAIS search engine only. It is not used by Index Server on IIS.

fpdb When FrontPage creates a Microsoft Access database as part of the Save to Database form handler, it stores it in this folder. Also, the sample database included in FrontPage is stored in this folder.

FrontPage Hidden & Server Files Defined
(These files can only be seen when your web/site settings have been adjusted to view hidden files & folders, or if you are a are the Webhost running FrontPage Extensions.)

Access.cnf Contains HTTP server-specific access control information

Administrators.pwd Encrypted names and passwords of administrators. On Netscape servers only.

Authors.pwd Encrypted names and passwords of authors. On Netscape servers only.

Bots.cnf Used for custom FrontPage-based components (WebBots) created using the FrontPage SDK.

Botinfs.cnf Custom FrontPage-based components (WebBots) information listing

Deptodoc.btr Dependency database for the web.

Doctodep.btr Dependency database for the web.

Fpcount.exe Run-time portion of the Hit Counter component.

Frontpg.lck Root web only. Lock file to keep Web server resources from being accessed simultaneously.

Linkinfo.cnf Back links for URLs not in the current web.

Service.cnf Contains meta-information about the web.

Service.grp Lists the members of the Administrator and Author groups. Used only for CERN and NCSA servers.

Service.pwd Contains the encrypted password files. Not used on IIS and WebSite servers.

Service.stp Contains the absolute file-system path to the FrontPage-extended web’s Service.pwd and Service.grp files. Used only for CERN and NCSA servers.

Services.cnf Contains the list of subwebs.

Services.org File used as the basis for Services.cnf when reinstalling the server extensions, so that subwebs are not created as subdirectories of the root web.

Service.lck Lock file to keep web resources from being accessed simultaneously. Should be a zero-byte file at idle time.

Structure.cnf Contains FrontPage-extended web navigational information storage.

Svcacl.cnf File used to store whether subwebs have unique permissions settings and any IP address restrictions, so that when reinstalling the server extensions the correct permissions settings are reapplied to any subwebs.

Users.pwd Encrypted names and passwords of end-users. On Netscape servers only.

Uniqueperm.cnf The presence of this file indicates that the subweb has unique permissions settings, as opposed to permissions that it inherited from the root web. Present only in subwebs. Used on IIS only.

Writeto.cnf Back links for files that can be written to by users of the web, such as Save Results form handler result files. Files that can be written to by users of the web have a looser security setting than regular web content.


Filed under: Website Editors on January 23rd, 2004 No Comments »

Ten Great Ways To Sell Advertising On Your Website

Scott F. Geld
http://www.marketingblaster.com/

  1. Offer a discount to your customers when they spend overa certain dollar amount for ad space. You can also apply this tip to the amount of ads they buy.
  2. Offer your customers a free bonus for renewing their ad order. It could be an ebook, special report, online utility, etc.
  3. Sell advertising space between your content. You just break an article in half and insert the banner or classified ad between it.
  4. Write content that’s tailor made to mention and relate to the product your customers are advertising. This is more work but, you’ll sell a lot of ads.
  5. Tell your customers when they buy an ad you’ll also add it to your free ebook and message board for free.
  6. Offer to endorse the product your customers are advertising before or after their ad. In all honesty, you would have try out the product first.
  7. Write a review for your customer’s product to place under their ad. This is similar to a testimonial or endorsement but more in-depth.
  8. Offer a buy 2 ads and get 1 free deal. With the slow economy and advertising sales, most businesses are bound to be looking for a good ad deal.
  9. Give your customers a ton of free bonuses when they buy ad space. It can be submission software, an ebook full of advertising or copywriting tips, etc.
  10. Guarantee your customer’s advertising results. If they don’t like the traffic they receive, give them a refund or another ad for free.

Scott F. Geld is the Director of Marketing for MarketingBlaster.com, a company providing targeted traffic and direct links starting at just $10 each. For more information, please visit: http://www.marketingblaster.com/

Filed under: Marketing & Publicity on January 23rd, 2004 No Comments »

CAN-SPAM Act of 2003

The law is intended for the email distributor sending unsolicited messages

CAN-SPAM Act of 2003

 

The President recently signed the CAN-SPAM Act of 2003. This law is a positive step towards fighting spam while making it easier for legitimate email marketers to comply with anti-spam laws.

 

The law is intended for the email distributor sending unsolicited messages, using deceptive practices, or distribution of sexually orientated material, as the title suggests, Controlling the Assault of Non-Solicited Pornography and Marketing Act of 2003.

What You Need to Know about the Can-Spam Act

The law goes into effect January 1, 2004 and is preemptive of all state laws. This means that it overrides the thirty-six states that already have spam laws.

 

Thanks to the ever extending powers of Federalism, you only have to comply with the federal law. This means that more aggressive laws, like California’s, that provided a right of action entitling recipients of prohibited spam to sue for statutory damages of $1000 per message, are no longer valid. The federal anti-spam bill does not include a private right of action.

 

While this new law will not stop spam, it does make most spam illegal and ultimately less attractive to spammers. The law is specific about requirements to send commercial email and empowers the federal government to enforce the law. The penalties can include a fine and/or imprisonment for up to 5 years.

 

Most e-mail list servers already comply with a number of features of the new law. We do however, highly recommend that you contact your provider, or your attorney for additional details on how to ensure you are in compliance with the new law.

Key points that will keep you out of trouble:

  • Use a permission based list (opt-in), which means that you don’t have to comply with the unsolicited email requirements stated in the law.
    This law does not seem to impose any regulations on permission based email lists. Although, the concepts below are ideal for any type of email list.
  • Falsifying Headers - “Do not use misleading email header information (Often used to make filtering spam difficult or to attempt to hide the senders identity)”
  • Valid FROM Line Email - “Your email campaign’s “From” address should be verified and accurately identify you as the sender (In English, You can receive e-mail from the stated “From” address)”
  • Subscription Removal Function - “Include the ability for your subscribers to opt-out of future emails, promotions, and/or eZines”
  • Misleading Subjects and Material - “Make sure that your email campaign’s “Subject” line is straightforward, not misleading (Do not use catchy phrases just to increase the chances that your email is read)”
  • Respect Remove Requests - “Any unsubscribe requests that come to you via a reply to your email must be honored within 10 days of the request”
  • Alternate Contact Information - “The new law requires that all email campaigns include the sender’s physical address”
  • Sexually explicit material - “Requirement to place warning labels on commercial electronic mail containing sexually oriented material”
What does the Future hold?

 

Included in the federal law is an option for the FTC to institute a “Do Not Email List” and for the feasibility the list to be determined no later than September 2004. For many reasons, the solution that has worked so well for phone numbers does not work well for email addresses. The FTC recognizes these issues and will be cautious in the way they proceed.

More Information on the Can-Spam Act of 2003 and e-mail marketing practices

Read the federal law, If you have specific questions about your organization, we recommend that you contact your attorney.
Click Here to download the attached printable PDF Version

Filed under: Email on January 22nd, 2004 No Comments »