faq.tpl template file example. View post for source code.
Read the rest of this entry »
listing_feeds.tpl template file example. View post for source code.
Read the rest of this entry »
listing_archive.tpl template file example. View post for source code.
Read the rest of this entry »
listing_profile.tpl template file example. View post for source code.
Read the rest of this entry »
listing_cams.tpl template file example. View post for source code.
Read the rest of this entry »
index.tpl template file example. View post for source code.
index.tpl template file example. View post for source code.
Read the rest of this entry »
The online manual pages cover about every aspect of the RCams administration. If you are still having troubles with some of the administration features, you can either post a comment to that specific administration section, or you can contact me directly. Same goes if you would like a feature to be added or if you found a bug on the administration backend.
Administration Tasks
Backend Main Screen (to be added)
Core (to be added)
Settings (to be added)
Categories (to be added)
Featured Models (to be added)
Feeds (to be added)
Reciprocal Links (to be added)
Rotating Banners (to be added)
Maintenance (to be added)
Admin Log (to be added)
Users (to be added)
Need an extra feature? Request it!
Found a bug? Report it!
Following are the general guidelines in creating a compatible RCams template. The examples provided below are not strict and you can create your very own template modeling in terms of files and content. The info below will attempt to include most of the futures provided by the script, however you may selectively use only some of these futures.
Note: since this is quite a long topic and it is about the only thing a RCams end-user should worry about, the entry will often be update with extra info and it might take a while until it will be really complete.
index.tpl – the only file that is a must and that the script is looking for. This file will make most of the decisions in terms of what content to be shown according to the visitor navigation
index.tpl example source code
listing_cams.tpl – file is called when the user navigates to a cam listing category and the online models list is output
listing_cams.tpl example source code
listing_profile.tpl – file is called when the user navigates to a cam model profile and the model profile is output
listing_profile.tpl example source code
listing_feeds.tpl – file is called when the user navigates to a RSS/XML feed and the content of the feed is output
listing_feeds.tpl example source code
listing_archive.tpl – file is called when the user navigates to the models archive and the content of the models archive is output
listing_archive.tpl example source code
liverandomcam.tpl – file is called when a live stream should be included in the output
faq.tpl – file containing whatever tips you want to write for the visitors, as well as the 2257 Compliance that is now a must for any adult website
faq.tpl example source code
style.css – CSS file that is used by the template
style.css example source code
image/ – directory where to hold any images used by the template
After creating your basic file structure, you are ready to start populating your template files with script variables and content. As the simplest way to learn is by example, I will highlight each of the required files. You can analyze them by viewing their entries, or by downloading the whole template file and view the files on your own computer.
Download the default RCams template package (17,301 bytes).



