Free link page 1.2 software for linux

Free Link Page is a project that allows visitors to add links to your page in a specified category.

This script allows visitors to add links to your page in a specified category. It is quite easy to install.

The administration module supports deleting of existing links.

Installation:

1.Open links.pl with a text editor.
Change the url in line one, to the Perl program at your server.
Usually it is: - /usr/bin/perl or /usr/local/bin/perl for Unix.
- C:/Perl/Perl.exe for Windows (use slash "/")
Set the correct paths and required urls.

2.Upload links.pl in ASCII-mode to your cgi-bin directory
and change mode it to 755 (-rwxr-xr-x).

3.Open addlink.html with a text editor.
Change the line

to the correct location of links.pl

Thats all.

ssLinks provides an open source PHP and mySQL powered links database.
ssLinks is an open source PHP and mySQL powered links database which allows users to run a database driven categorised links section on a web site - similar in structure to Yahoo or any other categorised links collection.
Main features:
- Fully database driven utilising mySQL.
- Full template system allowing you to control the HTML output of the script without needing to alter any of the PHP code.
- Easily customisable if you wish to alter the script in any way.
- Very easy to admin via the web - log in and add / edit categories and links.
- Visitors to your site can recommend new links, which you can then validate.
- Allows visitors to rate your links from 1-10, and displays average rating.
- Rating a link more than once is discouraged using cookies.
- Number of hits each link has received is recorded and displayed.
- Very easy to set up and use, thanks to an installation script and config file.
- Built in Search Feature.
- Most popular, top rated and newest links pages.
- Its Open Sourced under the GPL
Enhancements:
- The elusive top rated SQL error has finally been squashed :o) (thanks freakysid on www.sitepointforums.com)
- Login form now uses META tag redirect instead of standard header method - this prevents conflicts with the cookie header which may have prevented some browsers from logging in.

AT Media Page provides a simple and easy to use Plone Page which can contain ATImages.

HTMLParser is a super-fast real-time parser for real-world HTML. What has attracted most developers to HTMLParser has been its simplicity in design, speed and ability to handle streaming real-world html.
The two fundamental use-cases that are handled by the parser are extraction and transformation (the syntheses use-case, where HTML pages are created from scratch, is better handled by other tools closer to the source of data). While prior versions concentrated on data extraction from web pages, Version 1.4 of the HTMLParser has substantial improvements in the area of transforming web pages, with simplified tag creation and editing, and verbatim toHtml() method output.
In order to use HTMLParser you will need to be able to write code in the Java programming language. Although some example programs are provided that may be useful as they stand, its more than likely you will need (or want) to create your own programs or modify the ones provided to match your intended application.
To use the library, you will need to add either the htmllexer.jar or htmlparser.jar to your classpath when compiling and running. The htmllexer.jar provides low level access to generic string, remark and tag nodes on the page in a linear, flat, sequential manner. The htmlparser.jar, which includes the classes found in htmllexer.jar, provides access to a page as a sequence of nested differentiated tags containing string, remark and other tag nodes. So where the output from calls to the lexer nextNode() method might be:
< html>
< head>
< title>
"Welcome"
< /title>
< /head>
< body>
etc...
The output from the parser NodeIterator would nest the tags as children of the , and other nodes (here represented by indentation):
< html>
< head>
< title>
"Welcome"
< /title>
< /head>
< body>
etc...
The parser attempts to balance opening tags with ending tags to present the structure of the page, while the lexer simply spits out nodes. If your application requires only modest structural knowledge of the page, and is primarily concerned with individual, isolated nodes, you should consider using the lightweight lexer. But if your application requires knowledge of the nested structure of the page, for example processing tables, you will probably want to use the full parser.
Extraction
Extraction encompasses all the information retrieval programs that are not meant to preserve the source page. This covers uses like:
- text extraction, for use as input for text search engine databases for example
- link extraction, for crawling through web pages or harvesting email addresses
- screen scraping, for programmatic data input from web pages
- resource extraction, collecting images or sound
- a browser front end, the preliminary stage of page display
- link checking, ensuring links are valid
- site monitoring, checking for page differences beyond simplistic diffs
There are several facilities in the HTMLParser codebase to help with extraction, including filters, visitors and JavaBeans.
Transformation
Transformation includes all processing where the input and the output are HTML pages. Some examples are:
- URL rewriting, modifying some or all links on a page
- site capture, moving content from the web to local disk
- censorship, removing offending words and phrases from pages
- HTML cleanup, correcting erroneous pages
- ad removal, excising URLs referencing advertising
- conversion to XML, moving existing web pages to XML
During or after reading in a page, operations on the nodes can accomplish many transformation tasks "in place", which can then be output with the toHtml() method. Depending on the purpose of your application, you will probably want to look into node decorators, visitors, or custom tags in conjunction with the PrototypicalNodeFactory.
The HTML Parser is an open source library released under GNU Lesser General Public License, which basically says you are free to use the library "as is" in other (even proprietary) products, as long as due credit is given to the authors and the source code for the HTMLParser is included or available with the other product. For modified or embedded use, please consult the LGPL license.

Posy::Plugin::Paginate is a posy plugin to paginate multiple entries.

SYNOPSIS

@plugins = qw(Posy::Core
...
Posy::Plugin::Paginate
...
));
@actions = qw(init_params
...
select_entries
filter_by_date
sort_entries
filter_by_page
...
);

This plugin enables categories or chronological listsing with multiple entries in them, to be broken up into a number of pages, with previous and next links. Page length is defined by the num_entries configuration setting; it will select entries depending on the page ($paginate_param_name) parameter.

This provides the following variables that can be used within your flavour files.

flow_paginate_prev_link

Contains a link to the previous page, and is empty if this link is not valid.

flow_paginate_next_link

Contains a link to the next page, and is empty if this link is not valid.

flow_paginate_page_list

Contains links to all the pages, labelled by number. For example, if there are four total pages, this would contain, by default,

[1] [2] [3] [4]

See "paginate_pnum_prefix" for information on formatting this.

Cautions

This plugin does not work if you have a hybrid site (partially static-generated, partially dynamic) and also use the Posy::Plugin:;Canonical plugin, since the Canonical plugin will redirect your query. Also, if you have a hybrid site, dont forget to set the "paginate_url" config variable.

Activation

This plugin needs to be added to both the plugins list and the actions list.

In the actions list, filter_by_page needs to go somewhere after sort_entries and before head_render, since the entries need to have been sorted, and the selection needs to be done before the head template is rendered, so that links could be put in the head part of the page if required.

Configuration

This expects configuration settings in the $self->{config} hash, which, in the default Posy setup, can be defined in the main "config" file in the config directory.

DZone Voting 1.0.2 provides you with a wonderful and useful Firefox extension which dramatically simplifies voting at DZone. Provides an unobtrusive voting widget on any link you visit from DZone. A big problem at DZone is that you have to remember to go back and vote for links you have visited, and this Firefox add-on solves that problem beautifully.

Every time you visit a link from DZone, this add-on places a small, unobtrusive widget on the target page to let you vote. Simply click the widget to cast your vote, and it will be registered just as if you had gone back to DZone. It's a simple and convenient solution. Try out the DZone Voting extension, and it will be radically easier for you to vote on DZone links.

Major Features:

1. The DZone Voting add-on also makes it easy to submit links into the DZone queue, visit a random "Surprise me" link, and control how link and submission pages open in your bowser.
2. Just click the little "dz" icon in the stats bar, and you can arrange the settings however you wish.

Requirements: Mozilla Firefox

Enhancements: Added support for DZone short URLs (Twitter).

PWP Wiki Processor is a PHP Wiki based on flat files that can create static pages.
It uses flat files as data storage, no database is required.
It has a simple cache and trash bin, and can handle file uploads.
It is able to export its contents into static HTML pages.
A Wiki is a community/collaboration tool enabling a group of authors to create a network of linked HTML pages.
Main features:
- The various text formatting rules are described on a separate page: TextRules
- PWP uses flat files to maintain the data, no database is required. Every page is one data file in the data directory. The page still contains Wiki code; HTML is created at the moment of delivery. (You can translate Wiki code into HTML but not re-translate HTML into Wiki code.)
- The file upload page lets you store additional content at your website. Upload images or other documents and link them from your Wiki files.
- Every erase operation stores the Wiki pages or uploaded files in a trash bin. If your fingers were faster than the brain, simply unerase the file from the trash bin! You can delete files from the trash physically after a certain period of time (config entry). You can view files in the trash, but not edit these files.
- PWP supports a revision history. While editing a page you decide whether your changes are big enough to create a new revision. You can view and restore the old revisions of a file. Uploaded files will also be stored in the revision history if a new file with the same name gets uploaded again. To keep the history lean, you can delete all files older than a certain period of time (config entry).
- You can view recent changes, i.e. all recently changed pages and uploaded files.
- New in 1.5.0 Now PWP offers a diff. Further, it allows to rename and copy Wiki pages.
- You can configure the number of columns and rows in list views.
- Lost some information? Now you will have to do a full text search. PWP searches in both areas, in Wiki pages and in uploaded text files! The full text search is really simple without any indexes and might become slow if your Wiki contains several hundred pages. Well, hardware speed is increasing fast and time is working for me...
- PWP supports backlinks: A list of all pages which link to the current page. PWP can also trace backlinks for uploaded files. The search for backlinks is done on the fly without indexes or similar mechanisms.
- A search for file names is available. You can type fragments like ag and a list with all matching files is presented: Page2, Age. Search searches both, the Wiki pages and the uploaded files.
- New in 1.5.0 Reports are generated Wiki pages which help you to organise your information. Available are a hierarchical table of contents, a keyword index and a trail map / teaser text report.
- A simple click on a link will generate monthly calendar pages and an annual overview. The calendar supports either the German (European?) week format or the US week format where weeks start on Sundays.
- PWP can create a table of contents at the top of each page, consisting of all H1 and H2 tags.
- Concurrent editing? With page locks! Any edit action will set a page lock which warns other editors. The lock can be forced off.
- QuickEdit lets you view a page and append, insert or prepend new text in an edit box directly on the page. (Insert requires a special editor comment: ! --(+)-- ! )
- A simple cache will speed up your operations. Changed in 1.5.0 It stores lists and search results, but not Wiki pages.
- Snippets are supported. Snippets are text fragments, which will be appended to the end of the edit box on a simple mouse click. See /wiki/conf/Snippets.inc.
- The whole appearance (colours, fonts) is controlled by a simple style sheet (CSS). You can now add your own style sheet in second place, overwriting the default settings.
- If configured, the web pages are delivered as zipped data stream, making the Wiki faster on the internet.
- Save the best thing for last: PWP can export static web pages with a different header and footer. All links on these static pages will point to HTML pages, not to a PHP script. The static files are combined with a snapshot of the uploaded files. PWP can delete and re-create only outdated static pages. This feature will speed up the process but might result in dead links if there is no full update of the static contents from time to time.
Enhancements:
- added: Recent changes report
- changed: Report sorting now available for almost all reports
- changed: Keyword index report offers invers mapping
- fixed: WikiEngine issues with mail addresses and static links
- removed: Collisions, locks should be sufficient
- changed: Minor other changes, some refactoring.

Catalyst::Plugin::Email::Page is a Perl module to email your Catalyst page.

SYNOPSIS

use Catalyst::Plugin::Email::Page;

__PACKAGE__->config->{email_page}{
email = q{webmaster@example.com},
subject = q{User Report for},
link_text = q{Report Page},
};

# In your Template
[% c.email_page_url %]

This is a simple plugin that lets a developer set and forget e-mail links in Catalyst

INTERFACE

email_page_url

Returns a link in the form of: mailto:webmaster@example.com?subject=User Report for http://yours.com/

The mailto subject is escaped using uri_escape_utf8 from URI::Escape and http://yours.com/ is the current pages uri

email_page_body

Allows you to e-mail the whole page to someone once you have the right template. Used the same way as email_page_url

To do.

email_page_anchor

Allows you to e-mail a page anchor. Used the same way as email_page_url

To do.

_construct_url

Internal routine.

Reads in the various configuration settings and constructs the mailto link. See "CONFIGURATION AND ENVIRONMENT"