Last 10 Submissions RSS Feed

Twitter tweetssnippet

Fri, 20 Aug 2010 12:56:05 +0000

Another Twitter tweet snippet.

Using twitters own scripts.

Just a simple one, nothing fancy ;

demo output: http://etomite.vitusware.com/twitter

RTE Editor

Wed, 11 Aug 2010 17:08:47 +0000

This release fixes the problem of the erroneous style code being inserted into a document on load.

mv_findorphans

Thu, 22 Apr 2010 22:20:41 +0000

Snippet name: mv_findorphans
Snippet description: Finds and reattachs orphaned pages
Revision: 1.0
Date: 2010-04-03
by Mario A. Valdez-Ramirez

With Etomite 1.1 you can accidentally detach a branch (subtree) from the document tree by setting a descendant page as the parent of the current page. Common symptoms of this problem are disappearing pages (they no longer appears in the menus or in the Etomite manager), frozen sites (they take several seconds or even minutes to load and finally only display a "Fatal error: Allowed memory size of XXXXX bytes exhausted" message or a "Fatal error: maximum execution time of XXXX seconds exceeded").

Add this snippet to any page (to a test page not listed in the site), with [!mv_findorphans!], then load the page, click the search button, select what orphan pages to reattach to the test page, and then click the attach button.

You should reattach only the pages that look like the main document for each orphaned subtree. For example, if the documents are: 5->20, 6->20, 7->20, 20->21, 21->22, 22->5, then it looks like the root of the orphaned tree was 22, so that is the only node you should reattach (the other pages in the subtree are already attached to the document 22). When finished, remove the snippet (or unpublish the page), as its security has not been fully tested.

This snippet has been tested with orphaned pages created while editing pages in Etomite 1.1. It has not been tested with corrupted page trees created by database server crashes or manual manipulation. This snippet assumes that the orphaned subtrees are caused by simple circular references (a page having a descendant as parent) and that there is at least one page attached to the root (with parent 0).

MobileDetect

Wed, 17 Mar 2010 21:31:55 +0000

/* Thanks to http://www.russellbeattie.com/blog/mobile-browser-detection-in-php */
/* There are no options, just call the snippet in your template header in place of your css link. */
/* The detection is not 100% foolproof but should work on most devices. */

$websiteCSS = "website-css/web-design.css";	/* Your css file for mobile phones */
$mobileCSS = "website-css/mobile-design.css";	/* Your normal css file link */


$output = '';

/* Start of detection code */
$isMobile = false;
$isBot = false;

$op = strtolower($_SERVER['HTTP_X_OPERAMINI_PHONE']);
$ua = strtolower($_SERVER['HTTP_USER_AGENT']);
$ac = strtolower($_SERVER['HTTP_ACCEPT']);
$ip = $_SERVER['REMOTE_ADDR'];

$isMobile = strpos($ac, 'application/vnd.wap.xhtml+xml') !== false
        || $op != ''
        || strpos($ua, 'sony') !== false 
        || strpos($ua, 'symbian') !== false 
        || strpos($ua, 'nokia') !== false 
        || strpos($ua, 'samsung') !== false 
        || strpos($ua, 'mobile') !== false
        || strpos($ua, 'windows ce') !== false
        || strpos($ua, 'epoc') !== false
        || strpos($ua, 'opera mini') !== false
        || strpos($ua, 'nitro') !== false
        || strpos($ua, 'j2me') !== false
        || strpos($ua, 'midp-') !== false
        || strpos($ua, 'cldc-') !== false
        || strpos($ua, 'netfront') !== false
        || strpos($ua, 'mot') !== false
        || strpos($ua, 'up.browser') !== false
        || strpos($ua, 'up.link') !== false
        || strpos($ua, 'audiovox') !== false
        || strpos($ua, 'blackberry') !== false
        || strpos($ua, 'ericsson,') !== false
        || strpos($ua, 'panasonic') !== false
        || strpos($ua, 'philips') !== false
        || strpos($ua, 'sanyo') !== false
        || strpos($ua, 'sharp') !== false
        || strpos($ua, 'sie-') !== false
        || strpos($ua, 'portalmmm') !== false
        || strpos($ua, 'blazer') !== false
        || strpos($ua, 'avantgo') !== false
        || strpos($ua, 'danger') !== false
        || strpos($ua, 'palm') !== false
        || strpos($ua, 'series60') !== false
        || strpos($ua, 'palmsource') !== false
        || strpos($ua, 'pocketpc') !== false
        || strpos($ua, 'smartphone') !== false
        || strpos($ua, 'rover') !== false
        || strpos($ua, 'ipaq') !== false
        || strpos($ua, 'au-mic,') !== false
        || strpos($ua, 'alcatel') !== false
        || strpos($ua, 'ericy') !== false
        || strpos($ua, 'up.link') !== false
        || strpos($ua, 'vodafone/') !== false
        || strpos($ua, 'wap1.') !== false
        || strpos($ua, 'wap2.') !== false;

/* end of detection */

if($isMobile)	{
	$output = '	';
	}
else 	{
	$output = '	';
	}

return $output;

YouTubeImage

Fri, 18 Dec 2009 15:33:39 +0000

#by Sylwester K. sever2/at/o2.pl

## inserts with thumbnail generated by YouTube
# related with YouTubeList and YouTubeVideo

## example
# [[YouTubeImage?v=VIDEO_ID]] thumbnail for any video
# [[YouTubeImage?id=11]] thumbnail video used in Description of Document(11)
# size - check by yourself

# sizes ??? - sometimes are difrent

# 0 - 480x360 or 120x90
# 1,2,3 - 120x90
# deault - 480x360 or 120x90
# hqdeault - 480x360
# hq1, hq2, hq3 - 480x360

YouTubeList

Fri, 18 Dec 2009 15:25:16 +0000

## by Sylwester K. sever2/at/o2.pl

## YouTubeImage snippet needed

## This snippet makes of titles and links for your YouTube videos published on separate Document with YouTubeVideo snippet
# example: [[YouTubeList?cols=1&size=hqdefault]]
# id - Document ID whose children are used to build list
# cols - number of columns in table default 4 for vertical list use 1
# limit - number of document to use
# size - size of thumbnails (see YouTubeImage for more info)

YouTubeVideo

Fri, 18 Dec 2009 15:10:28 +0000

## by Sylwester K. sever2/at/o2.pl

## usage
# post YouTube's VIDEO_ID in snippet call [[YouTubeVideo?v=VIDEO_ID]]
# or publish whole YouTube's video URL as Document Description
# you can also call this snippet with id of document witch have VIDEO_ID in Description
# instead of using ID of Document where it was called
# all parameters are optional
# links id Decripton are used to build YouTubeList

## examples:
# [[YouTubeVideo?v=VIDEO_ID]] any video
# [[YouTubeVideo]] video from this Document's Description
# [[YouTubeVideo?id=11]] video from Description of Document(11)

## parameters description:
# http://code.google.c...parameters.html

PDF writer

Tue, 17 Nov 2009 16:49:47 +0000

/************
PDFWriter V1.0
Use: A snippet to export etomite pages as PDF
Cris D 2009-11-17
Etomite 1.1
based on the FreePDF class http://fpdf.com
*****/

Installation instructions:

Unzip the contents of this zip archive.
Create a folder called "pdf" in the root of your site.
Upload the fpdf.php file to this folder.
Upload the folders "images" and "font" to this site also.

Now you should have:

siteroot > pdf > fpdf.php
siteroot > pdf > images > logo.gif
siteroot > pdf > images> pdficon.jpg
 siteroot > pdf > font > [contents of font folder]

The other files and folders in the fpdf16 are for reference only
and it contains many really good tutorials and samples of how to use it.

Copy the contents of the pdfwriter.txt file and save it as a snippet in your etomite snippet library.
Call the snippet in a page or in your site template.

There are 2 optional configurations:

$image [0] || [1] (Default 1) : A switch to show an icon or a text link to get the PDF.
$linkMessage = "Export to PDF";

In addition, there are many ways you can lay out the page - I will not be providing support for this - it's up to you.
There's enouogh help included in the tutorials and samples for you to work this out yourself.

Enjoy.

[updated snippet documentation to clarify the uploaded file structure]

Etomite Prelude (Russian Language for v1.1)

Thu, 05 Nov 2009 22:30:33 +0000

Архив содержит Русский языковой файл.
Файл содержится в папке manager/includes/lang/russian.inc.php
Кодировка win-1251

siteErrorHandler

Sat, 31 Oct 2009 03:33:20 +0000

/*************
Snippet: siteErrorHandler V1.0

Author: Cris D 2009-10-31 (acknowledements to plaincart for the concept).

Use: Allows etomite users to manage errors for a site in a centralised manner by using sessions.

Dependancies: Nill- will work on any etomite installation with sessions configured (a requirement to installing etomite in the first place).

Installation:
Copy the contents of the snippet and save it as a new snippet called "siteErrorHandler"
Call the snippet in the template of your site before any other snippets
(in the head or above the html is OK) like this:
[!siteErrorHandler!]

Snippet output:
The snippet itself does not actually output anything- it just loads the functions into the working memory for your code to use.

It provides a user-friendly way to store, markup and retrieve errors centrally.

There are 2 functions to use it:

1) setError('error message'); loads an error to the session.

2) displayError(); gets the session errors, runs them through a mark-up routine and sends them back to display for the user.

A note on checking if an error is currently stored:
Once displayError(); is called, the session errors are cleared until the next time displayError(); is called. Therefore, to test if errors are stored, you must either set another local variable like:

$error=true;

or check the session errors explicity by using something like:

count($_SESSION['site_error']);

See examples below for more on this.

DON"T PANIC: the amount of writing below is not an indication of how complex this is to use, I have just provided a lot of examples and documentation so it is easy to apply to your site. It's actually really easy to implement.

Uses of siteErrorHandler 1) Centralised display of errors in a page or template:

If you have a central location in your site or template where you want errors to occur,
you can call a snippet in that section of your template that is used to display any errors,
for example:

//Snippet: showErrors V1.0 Cris D 2009-10-31

return displayError();

//end snippet showErrors

in this case, if there are no errors, nothing will be displayed.

Uses of siteErrorHandler 2) Setting and displaying errors conditionally

You may like to choose where and when errors display during code at runtime,
then you can just call the function and add the errors to the output of the snippet,
for example:

Quote

//sample code using setError() and displayError()

setError("You have made a boo boo!"); $error = true;

if(!$error)
{
<...runcode...>

} else {

$out = displayError();

}
$out .= "";
return $out;

Using siteErrorHandler:

setError can take the error messages in a number of ways, the most common will be as text,
but it will take a number of methods, for example:

setError("Error message."); //as text
setError($error_message.$user.$date); // as variables
setError($language['message1']); // as an array item
setError($localErrorArray[] = $message); // build a local array of errors to interact with at runtime

These error messages that are set can be retrieved and interacted with by using:

$_SESSION['site_error'][$i];

or if a local array is built:

$localErrorArray[$i];

Example of use:

Quote

setError('text');
setError($arr[] ='Message 1');
setError($arr[] = 'Message 2');
setError($arr2=('1'=>'one', '2'=>'two');

print_r($_SESSION['site_error]);
Array
(
[0] => text
[1] => Message 1
[2] => Message 2
[3] => Array
(
[1] => one
[2] => two
)

print_r($arr);
Array
(
[0] => Message 1
[1] => Message 2
)

return displayError();

will return:

 

 
	text
	
	Message 1
	
	Message 2
	
	Array

Note that passing a whole array to setError will not return array elements as error messages.

/*************
Examples of use including error checking logic embedded in etomite code:

//check for existing errors from previous pages
$currentErrors = count($_SESSION['site_error']);

if($currentErrors > = 1) 
{
return "You have existing errors to resolve before you can do your email bit";
}

if( $_POST['email'] == null )
{
setError('You must enter your email address.'); $localerror = true;
}

if(!$localerror){

$output = "Your email address is: ".$_POST['email'].".";

}else{

//show all errors so far if there are any
$output = displayError();

}

//default view- show the form
$output .= "



";

return $output;