The portal files are kind standard functions for member management login, logout, register new member with some Ajax, password reminder, private messenger Ajax version, admin area, member list, database page view with security levels and Ajax, member profile view/edit/delete, Search, rank is a member XP game that is mainly gained though the Forum.pm in the /lib/modules folder.

The modules folder has Chat, simple wiki, simple faq, Image Gallery, RSS Feeds module, Clock that uses GD and was from some web site...., Error log which shows logged warnings and die error from the system w/delete, Forum is a combo of a Forum/Articles/Polls, server info is a Perl Digger script only works for *nix OS's

There is a Capcha module that a few codes use like login and register.

Before you even get to the some of the codes above there is ban, anti-spam which is experimental along with /lib/TG.pm, stats log - logs user activity, member authentication is a session.

A lot of the development went into the SQLSubLoad.pm file in /lib. The method in that file can help you put subroutine where you want them though out parts of the theme and before the theme loads.

Also uses the AUBBC module i made for a lot of the html tag substitutions and to secure form inputs to the database. A wiki entry in the sql.txt was left about the AUBBC module. It has a lot of tag the portal supports.

Other capability it offers is a tag converter for URL paths to the cgi-bin an none cgi folders. That can be used in the main & member menu and theme editor. sub eval_theme_tags in /lib/theme.pm

Plus a few more thinks that makes life easier.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.