Comus Variables
Básicamente la plantilla está controlada por {{macros}} especial que colocas en tu página web, los macros le dicen a Comus Thumbs dónde quieres posicionar las cosas, Comus luego escanea la página de plantilla, e inserta los enlaces y pulgares como lo solicites, o realizará operaciones especiales en la página, es el resultado en una nueva página y directorio de tu elección. |
| Terminología Macros, Variables,Extensiones,Modificadores,Links,Thumbs. |
| Una visión rápida de la terminología |
Esta sección proporciona una introducción a los bloques de construcción del script, que proporciona una imprenta para la información más detallada que sigue. |
FORMAT: {{category-type-index}}
Where category is either 'all' or the case sensitive name of a chosen category, and type is one of [link or archivelink] and index is the selector of which link in thelist to use.
EXAMPLE: The 1st, 3rd and 2nd link in the list, taken from only the teen category.
| Lesbians - Young Lesbian Closeup | Babes - Busty Aria Giovanni | Teens - Cute Brunette Poser | Lesbians - Young Lesbian Closeup |
NOTES: You would use this type, if you wanted very specific control over your layout, maybe you want to place banners and blind links in the middle of your table, this is a perfect use for Singular links.
-Singular links do not need table tags, unless you define the link template in such a way to require them.
-If singular links do not find any images in a particular category, or do not have enough images to complete the list, then they will search at random throughout your gallery listings, to make up the difference.
-By default images have priority over links, but once used as an image or a link the gallery will be flagged and will not be available to the other lists.
-Note in this example I deliberately doubled up on the 1st teen link, the script automatically places the first occurance of the link in both locations.
-Indexes start at 1 and run sequentially upwards, if you miss an index (1,2, ,4,5) then the script will drop your last images, in this case it would see there were only 4 links requested, and it would have no image avail for index 5.
FORMAT: {{category-type-index}}
Where category is either 'all' or the case sensitive name of a chosen category, and type is one of [thumb or archivethumb] and index is the selector of which link in the list to use.
EXAMPLE: A custom table of 3 by 3 thumbs, taken from the teen database
 |
 |
 |
 |
 |
 |
 |
 |
 |
-The lower the number the higher the priority of that image in your list. So index=1 is the very first thumb pulled from your list, depending on how you have ordered your list, this could be a high priority image. By default, images are sorted at random but weighted by the rank you assign to them through the approval process. Each prefered submitter can have his own default rank that you can assign, and each standard submitted gets a default vote of 7. This gives you 3 levels of downgrade and 6 levels of upgrade to play with. Each level represents approximately a 10% jump, so votes of 1 should consistently fall somewhere within the top 10%, as the votes fall more towards the extremities they become less eratic, while votes in the mid ranges will tend to bounce around a lot. This is done so votes you upgrade, will tend to get sent to the top of the list, and votes you down grade will tend to randomize at the bottom, while votes in the middle will get a fair jumbling.
-archivethumb types are explained below, but basically pull from the list after all links and thumbs have been processed.
FORMAT: {{category-type-index}} Where category is either 'all' or the case sensitive name of a chosen category, and type is one of [link or archivelink] and index is the selector of which link in the list to use.
EXAMPLE: A custom table of 3 by 3 links
| Fetishbizarre - Slut Gets Spanked | Amateurs - Amateur Panties | Teens - Tawnee Vids/pics |
| Babes - Babe In Stocks | Anal - Anal Please | Fetishbizarre - Hard Bondage |
| Teens - Beautiful Erotic Brunette | Interracial - Sluts W Huge Cock | Lesbians - First Lesbian Experience |
FORMAT: {{include-(path or url)sourcefile}} Where include is the keyword to trigger this macro, and sourcefile is the name of the file to include.
ALIAS: This command is an Alias for {{showfile-sourcefile}}
EXAMPLE: A default include file has been set up for this demo. It contains a single thumb and a short messge. The file itself is created in the next section, note that because of the forward reference that any changes to the file will not be reflected until the next refresh of the page.
This is an included document test_out.txt
-Included files do NOT get interpreted by the template processor, they just get added to the current output, to process macros on a page file, see below.
-By default files are extracted from the /templates folder, but you can use ../ path modifications to reach the rest of your drive, or you can just use a direct http:// url, but note where you use the url it will interpret your page first.
-Includes allow you to use special sections like 'headers' and 'footers' which are built into your pages at compile time, allowing you the benefit of shtml/php/asp includes without having to have a runtime script while in production. That means you can run the TGP side of your site entirely in HTML only mode, reducing server overhead and costs considerably.
-Includes can also be used to load your archives or the results of custom template builds. (see next section for info on custom templates)
FORMAT: {{makefile-(path or url)sourcefile-targetfile}}
Where 'template' is the keyword to trigger this macro, and sourcefile is the name of the file to load and process and targetfile is the name of the file to save results to.
EXAMPLE: Building a custom template
When this macro is placed on a page, it will first check to see if a rebuild is required, if it is then it will load the desired template from your /templates directory by default, or it will search the path, or load from the http:// URL you have specified.
-The source file can also execute the same macros as your makefile template. It can build and include pages and write them to disk (into the templates folder by default). You can also specifiy other locations by adding relative path information to the filename. IE. {{makefile-testin.txt-../../testout.txt}} would take the file testin.txt, parse it and write the results 2 folders up from the ct/templates folder. (Assuming Comus is in the subfolder /ct/ then it would write the file into the main index folder of your site.
-You might need to make sure that PHP has permissions to read/write the files. New target files will usually complain about permission errors, you will need to chmod 777 the target file, so that both you and Apache have read/write/execute to the target file.
-Templates can be used to create Archive pages. The script will start pulling thumbs from the top most 'makefile' macro found within Templates Control Center and then execute the 'makefile' macros found within each source template. The lowest macro on the page, gets the eldest thumbs. Remember this if you are trying to lay pages out and are wondering why your new thumbs are not showing up.
-Once you have created a page, to reference or link to the page you can either { include } it using the method mentioned above, or you can include it using a php or an SSI include. Or if you have designed your template so that the page can stand completely alone, you can name it with a .html extension and reference it directly.
-The macro works on both templates and the Make Files Section found inthe Templates control center.
-Note that no links or code are created ON the page that actually invokes this macro. If you need to link to the resulting page, or if you need to view the results, then you will either have to create a link to the page, or you will need to use an include to load the results into a page. So for example, you could use an include to load the template result onto your main page.
-If you use this feature it is best to try and build the template, before you try to include it.
-A resulting template page can only be manipulated by the first macro which calls it, subsequent requests to write to the same file during the same session, will be ignored.
-Your target filenames can have any extension they like, and so your templates can be in any scripting language you like.
-You have the option of loading the template file with any language you like, Comus's include method should be the fastest during run time, because it compiles the code right into the page so that it can be static. But you can load the page dynamically at load time if you like with PHP/ASP/SSI/JS or whatever.
NOTES: Archive galleries are the galleries that remain after all the current galleries have been extracted.
-By placing multiple makefile macros in the makefile template it gives you the option of creating separate pages which contain archived links and thumbs.
The method we use for accessing the archive galleries is to simply control the order in which we request the pages from within the master Makefile template.
[START MAKEFILE]
{{makefile-indexpage.txt-../../index.shtml}}
{{makefile-archivepage.txt-../../archive.shtml}}
[END MAKEFILE]
Will process your indexpage.txt file FIRST and write it to index.shtml in your web root folder, pulling the most current galleries. It will then use what remains in your pool to create the archives.
NOTE:You need to make sure you use macros within the archive pages which only look for thumbs which are 1 day or older say with an query-age1}} extension, or your archive page will probably try to pull fresh galleries, as all basic non extended macros will always try to grab fresh thumbs by default.
For example.
The system has a default query for pulling galleries of one day older or more.
{{all-links-20-1-query-age1}}
Will list a vertical column of 20 links, which are 1 day or older.
-The idea is that you create a separate template page to your main page for holding your archived galleries, and then on this archive page you place your {{category-type-dimension}} macros.
-Then you either place a direct link to the resulting file, from your main page, or you can include the resulting page, by using a macro/shtml/php/or the scripting language of your choice. Note because of the nature of the macro ordering, when using {{include}} for displaying archived gallery pages you will have to display the archives from the previous build, or in other words, the archive listings will be 1 build old, when displayed. (hope it makes sense as to why)
| Local Variables-Only avail within link and thumb templates | |
| Variable | description |
| %onpage% | The number of times the gallery has been displayed on a page, or actually used in a build, this ONLY increases when the gallery is actually used. |
| %clickperiods% | The number of times galleries have been built since this gallery was listed as new, note that this increments regardless of whether the gallery was actually used on a page. |
| %periodsshown% | The number of DAYs passed since the gallery was newly used on the site. |
| %clicks% | The number of clicks on the gallery. |
| %ctr% | The Click Through Ratio for this gallery, a score defined as clicks/clickperiods. |
| %cat% | The condensed category taken from the database as entered in the [Category] section. |
| %category% | The category taken from the macro - IE shows 'all' for all. |
| %rawcategory% | The category taken from the database without condensing (no removed spaces). |
| %url% | The target url. |
| %overurl% | The target url, used for mouse overs (without trade script). |
| %domain% | The domain only of the target URL |
| %desc% | The truncated description, (max length set by you) |
| %description% | The full description |
| %uid% | The unique id assigned to the gallery |
| %id% | The true id for the gallery |
| %nick% | Submitters name |
| %thumbname% | The actual file name to the thumb |
| %thumbheight% | The thumb image width |
| %thumbwidth% | The thumb image height |
| %thumbsize% | For compatibility, width of square thumbs |
| %numpic% | Number of pics in the gallery (always 2 chars, ie 00...08,09,10,11) |
| %piccnt% | A running count of the total links and thumbs displayed |
| %numlist% | A running count of the links and thumbs in this set only |
| %thumbsize% | For compatibility, width of square thumbs |
| %vote% | The ranking score (1-10) assigned to the gallery |
| %rank% | The ranking score assigned by you |
| %clicks% | The number of times the gallery has been clicked |
| %dis_date% | Custom formatted date of submittal |
| %TODAYS_DATE% | Non formatted day of the month, with no leading 0's |
| %submit_date% | Custom formatted date of submittal |
| %submit_hour% | 00-24 hour of submittal |
| %submit_day% | 01-31 day of submittal |
| %submit_month% | 01-12 month of submittal |
| %submit_year% | xxxx year of submittal |
| %accept_date% | formatted date of approval |
| %accept_hour% | 00-24 hour of approval |
| %accept_day% | 01-31 day of approval |
| %accept_month% | 01-12 month of approval |
| %accept_year% | xxxx year of approval |
| %listed% | formatted date of first listing |
| %listed_date% | formatted date of first listing |
| %listed_hour% | 00-24 hour of listing |
| %listed_day% | 01-31 day of listing |
| %listed_month% | 01-12 month of listing |
| %listed_year% | xxxx year of listing |
| Global Variables-Available Anywhere | |
| Variable | description |
| %this_date% | formatted date of today |
| %this_HOUR% | 00-24 hour of today |
| %this_hour% | 00-12 hour of today |
| %this_day% | 01-31 day of today |
| %this_month% | 01-12 month of today |
| %this_YEAR% | xxxx year of today |
| %this_year% | xx year of today |
| %sitename% | The domain name of your site without http:// |
| %siteowner% | The name you chose for yourself in setup |
| %tgpemail% | your registered email address |
| %recip% | Your recip link with http:// info |
| %refreshperiod% | The current refresh period |
| %this_period% | The current refresh period |
| %totalposts% | Total number of posts made |
| %logins% | Total number of webmaster logins |
| %hits% | Total hits on the page |
| %total_galleries% | Total approved galleries in the system |
| %updates% | Number of days passed since the site was new, the actual age of your site. |
| Local Variables-Only avail within link and thumb templates | |
| Variable | description |
| %lshave% | Text Link Shave value, will be replaced by either the 'lshave' value from Category Control Center or the #80# modifier value from within the macro, the macros have priority over category settings, there is one other thing that can affect lshave and that is the proxy capping settings. |
| %tshave% | Just like lshave only it is intended to affect the thumbed listings |
| %group% | Taken from the {{GROUP#SHAVE#category-type-index}} GROUP modifier can be used to send trades to your trade groups. |
| %category% | Feeds a compressed category tracking code to your trade script, you canuse this to track link popularity. |
| %proxy% | Feeds a code to the script of 'p' for a proxy click or a 'n' for a normal click. You can use this to track outgoing proxy traffic to identify hitbots. |
This would allow you to dynamically control shave ratios based on macro position, or category, it would also pass link tracking information through to the script, which would look like, p_TXT_Teen for a click on a teens text link from someone on a proxy server. (FYI Abnormal outgoing Proxy server traffic is an indication of someone using a hitbot on you, and can be used to monitor cheaters, if your ratio.)
FORMAT: {{category-type-index-query-"string"}} | {{category-types-rows-columns-query-qindex}} where query is a keyword to trigger this macro extension and qindex is an index to preset query (See below)
{{all-thumbs-3-3-query-"description like '%blonde%' or url like '%blonde%'"}} EXAMPLE {{setquery-1-"description like '%blonde%' or url like '%blonde%'"}} {{all-thumbs-3-3-query-1}}
This would first define a query and give an id of 1, the second macro then uses the defined query to search descriptions and urls for anything containing blonde. Note that the query is a mySQL WHERE clause and must be within double quotes ""
NOTES: Advanced capability, highly flexible and powerful. Finally, as I started thinking about all the options that I could build lists with, I decided to just expose the database query string and structure to you. So whatever your imagination can think of, is available to you. You will need to know how to structure a mySQL WHERE clause - so go look up queries on mysql.org.
Basically it gives you the ability to build custom lists and filters using less than, greater than, equal to, similar to, starts with, ends with,etc,etc and order them in any way you please. (If the script does not detect an ORDER BY, then it will assign its default ordering algorithm of date desc,rand()*vote.)
NOTE: It is not a full query, but just a WHERE clause.
You can use the 'query' capability of the post/review/search page to test the results of your queries, before you actually use them.
See the next section for an advanced application and examples of this option.
| Available fields | |
| Field | Description |
| id | Unique ID code |
| ip | IP of submitter |
| nickname | Name the submitter gave |
| Email address the submitter gave | |
| url | URL of gallery |
| category | Gallery Category |
| description | the full string of what the user gave the gallery |
| date | The date it was subitted in YYYYMMDDHH format |
| newpost | Yes if not yet approved |
| accept | Waiting/Yes/No |
| vote | 1=good ... 10=poor |
| recip | 'Yes'=has recip |
| sessionid | A unique 6 char string |
| numpic | Number of pics linked to images found in the gallery |
| filesize | Byte size of html page |
| thumbname | If blank then a link else if has a name then we have a thumb |
| mailme | Wants contact if approved |
| listed | The time that the gallery was listed in YYYYMMDDHH format |
| mgdate | The time that you approved the gallery in YYYYMMDDHH format |
| thumbwidth | The pixel width of the thumb |
| thumbheight | The pixel height of the thumb |
| clicks | The total number of times the link was clicked |
| timespent | The estimated time people have spent looking at the gallery in secs |
| exitclicks | The number of people who never return from the gallery |
| periodsshown | The number of times you have listed this gallery |
NOTES:This uses a combination of features built into Comus, and works with the custom 'Query' capabilities of the script.
To invoke counting set 'click counting' to Yes in the config setup page, this will modify all outgoing links on the page to re-route via cc.php and then on to your trade script.
The script will keep a running count of clicks and impressions and time spent at every gallery, now you can start using it in custom queries to build lists.
1 Galerías más frecuentadas para el día
{{setquery-1-" periodsshown=1 order by clicks DESC»}
2 Más popular para la semana
(Supone que su período de refrescos es diario, de lo contrario ajustar en consecuencia)
{{setquery-2-" periodsshown > 8 AND periodsshown > 0 ORDER BY clicks DESC»}
3 Random pero ponderado por clic
{{{setquery-3-" periodsshown título0 ORDER BY (clicks*rand())+(clicks*rand())+(clicks*rand()) DESC»}}
4 Sobre las galerías promedio ponderadas por voto
{{setquery-4-" periodsshown título0 AND clicks œ sum(clicks)/count(*) ORDER BY (vote*rand())+(vote*rand())+(vote*rand())}}}
5 selecciones de categoría múltiple
(Asegúrese de utilizarlo como categoría 'all' primero) y luego el script se filtrará para usted.
{\fnMicrosoft Sans Serif}}
6 Consultas combinadas, top clasificadas con selección aleatoria de los votos prioritarios del mes primero, clics segundo
{{setquery-7-"(vote=1 OR (periodshown י 30) ORDER BY vote,clicks DESC"}
¿Nota cómo no se limita a usar sólo números para el identificador de consultas? como en [query-multicat] y también que puede utilizar el %global variables% definido anteriormente en las consultas también.
Ahora para poner en práctica una de estas consultas en su lista usted extendería la macro añadiendo el -query-query name} al final de su macro, IE:
 |  | |
 |  |  |
 |  |  |
Hay una macro depuradora especial que le mostrará la lista de consultas disponibles, esto podría ser útil si usted está pensando en construir una consulta personalizada. Es posible que ya hayamos definido uno como una consulta de sistema predeterminada, y puedes usarla en su lugar, o los perhps la usan para construir una consulta personalizada. Para mostrar la lista de todas las consultas activas que puede utilizar,{\fnMicrosoft}Para usar las consultas simplemente use el [key] como su 'query identifier'
query[age0]=" periodsshown >-1 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) )"query[age1]= "periodsshown > 0 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) )"query[age2]= "periodsshown > 1 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age3]= "periodsshown > 2 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age4]= "periodsshown > 3 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age5]= "periodsshown > 4 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age6]= "periodsshown > 5 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age7]= "periodsshown > 6 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age14]= "periodsshown> 13 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age21]= "periodsshown > 20 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[age28]= "periodsshown > 28 ORDER BY periodsshown, ( (vote*rand())+ (vote*rand()) + (vote*rand()) ) "query[days most clicked]=" periodsshown=1 order by clicks DESC, mgdate DESC"query[this weeks most clicked]= "periodsshown < 8 AND periodsshown >0 order by clicks DESC, mgdate DESC"query[last weeks most clicked]= "periodsshown < 15 AND periodsshown >7 order by clicks DESC, mgdate DESC "query[random by click]= "periodsshown>0 ORDER BY (clicks*rand())+(clicks*rand())+(clicks*rand()) DESC "query[above average]= " clicks > sum(clicks)/count(*) ORDER BY vote*rand()"query[last weeks best]= " ((vote= 1AND periodsshown >7 AND periodsshown < 15 ) ORDER BY clicks DESC "query[weeks best]= " ((vote< 4 AND periodsshown < 7) ORDER BY clicks DESC,vote*rand() "query[months best]= " ((vote< 4 AND periodsshown < 30) ORDER BY clicks DESC,vote*rand() "NOTA: Estas son sólo algunas de las consultas disponibles, hacer un basurero para ver si he añadido o cambiado.
Coeficientes de Skim por MacroEsto se hace a través de un modifer macro, donde prefijo su categoría con un valor de relación de skim, como {{#80#all-thumb-1}}
Esto alimentará el valor de 80 a la variable %lshave% o %tshave% dentro de su prefijo de script comercial y definiciones de sufijo (encontradas dentro del centro de control). Tenga en cuenta que lshave y tshave no tienen que ser un número, también pueden ser cadenas de texto que alimentan otros argumentos para su script de comercio, o incluso múltiples argumentos, IE{#p=50 limitx=latin#all-thumb-1} Esta forma de modificación de scripts comerciales requiere mayor prioridad sobre las relaciones comerciales por las definiciones de categoría descibed siguiente.
Tasas de comercio por categoríaEs posible alimentar ratios de comercio a través de sus scripts de comercio por categoría utilizando las variables %tshave% y %lshave%. Usted encontrará las relaciones de esquima para estos dentro del Centro de Control de Categoría.
Totalmente desactivando el script de comercio para sólo 1 páginaTambién puede desactivar cada comercio en una página, utilizando la macro {{notrades}}. Coloque este macro cerca de la parte superior de la página, para que pueda estar seguro de que está activado para toda la página. Se puede utilizar en las páginas de archivo para eliminar el script de comercio por completo.
Disabling the trade script for a sectionEs una mejor idea para modificar su relación a 100 que eliminar su script comercial de la ecuación, porque de lo contrario no será capaz de medir los clics entrantes/salientes, y podría arruinar sus estadísticas y software de análisis.
FORMAT:{{setthumbtemplate-new link template}} {{setthumbtemplate-new link template}} donde setlinktemplate y setthumbtemplate son palabras clave especiales para activar este macro y nuevo link template es lo que podrías poner en un enlace o plantilla de pulgar
EXAMPLE{{{setlinktemplate-traducidoa href= '%url%%]
NOTAS: Esto cambia todo el formato de enlace en la plantilla actual. Puede utilizar esto para modificar el formato de enlace o tabla sobre una base de sección por sección, pero necesita combinar las opciones de creación de plantillas y de inclusión, porque esta macro afecta TODOS los enlaces en una plantilla. Por lo tanto, si desea reemplazar su estilo de enlace sólo para una sección, entonces tiene que poner las secciones en diferentes plantillas, activar esta macro en la nueva plantilla, y luego volver a su página principal e incluir el resultado.
Si utiliza esto en una plantilla y luego incluye otra plantilla, su estilo no será heredado por la plantilla incluida, a menos que esa plantilla también tenga un modificador de configuración.
FORMAT:%this weekday-index% donde índice es un valor de 0 a 6 representando 0 a 6 días atrás.
EXAMPLESi hoy era lunes en el servidor entonces,
%this weekday-0% = Mon
%this weekday-1% = Sun
NOTAS: Esto crea un código de 3 letras que representa el día de la semana, el código de 3 letras es sensible al caso. 'Mon,Tue,Wed,Thu,Fri,Sat,Sun' Puedes usar esto para crear un conjunto de archivos de imagen que representan encabezados para tus días de semana. IE: Si tuvieras un conjunto de cabeceras llamadas, 'Monday.gif, Tueday.gif,Wedday.gif, Viernes.gif,Satday.gif,Sunday.gif' (Nota la ortografía), entonces tu campo src img parecería img src="%this weekday-0%day.gif".
Puede tener tantos archivos como desee en su sitio. Por defecto, el script tratará de asegurarse de que ninguno de los archivos use las mismas imágenes dos veces, aunque puede anular esto, y tire de las imágenes de nuevo para páginas personalizadas.
Por lo general desea construir su archivo de página principal primero, y luego construir las páginas sub, y luego finalmente construir las páginas de archivo. La orden es importante, porque el script correrá por el edificio Make File las páginas como las encuentra, y tirar de sus galerías como va.
El comando principal de la plantilla del fichero es la macro {{Makefile-sourcefile-targetfile}}, dondemakefilees el comando de invocar esta macro ysourcefilees el nombre del archivo para utilizar como plantilla de origen, ytargetfilees el nombre del script resultante o archivo HTML que contendrá todos sus enlaces y pulgares.
Puede tener un número ilimitado de archivos de plantilla, y puede escribir a un número ilimitado de archivos de destino. En cualquier lugar de la unidad de disco, siempre y cuando tenga permisos.
Cada archivo de destino es una página estática precompilada, y puede ser de cualquier extensión de archivo o tipo. Recomendamos hacer html solamente Archivos de destino, porque se cargan más rápido, con menos carga de servidor, y son menos costosos para ejecutar.
Diseñar un sitio para Comus es casi el mismo que cualquier otro sitio web, con un paso añadido, de en realidad compilar las páginas del sitio a través del script. Usted todavía puede utilizar sus herramientas de desarrollo estándar, simplemente subir sus archivos en la carpeta /templates que contiene todas sus macros, y luego dejar que Comus haga el resto, construyendo y publicando sus archivos en su sitio.