Contribute as Simple WCMS

Track

Add trackback URL

Trackback

Trackbacks is allowed for this entry...

cvb

cvbcvbcvbcv

zxczv

PodcastingDemo

This is the post containing mp3 enclosure.

sampleenclosure-1.mp3

12121

this is from Thexia - alright!!!!!

Giving some hope to crisis-ridden Satyam, the World Bank has said it could review the eight-year ban imposed on the company provided the software exporter takes "corrective action".

A World Bank official said Satyam has to show it has again become a responsible vendor to do business with, when asked whether the multilateral lending agency would relax the ban on the software exporter.

"The vendor would have to demonstrate (that) corrective action had been taken to address the original causes of the ... Ineligibility," a World Bank official from Washington told PTI in an emailed statement.

The official further said action should substantiate that Satyam is "again a responsible vendor with whom the Bank can do business".

The World Bank banned Satyam Computer Services for eight years in 2008 for providing "improper benefits" to Bank staff and for failing to maintain records relating to fees charged for sub-contractors.

More over Satyam bidders won't get to see accounts before bidding

 The suitors seeking to take over the scam-hit Satyam Computers will not be able to go through the restated financial statement or the third quarter results prior to the bidding, a senior company official said.

"Obviously... (the bidders would not be able to see them as these documents would not be prepared by then). Considering the nature and extent of the fraud, it will take quite some time to make them. The bidders will have to go by their judgement of the company and its intrinsic value and they all know what is the position of the company," Satyam Chairman Kiran Karnik told PTI.

He said with market regulator Sebi amending the takeover Code, this move will help the company to move quickly on the sale process.

Satyam's investment bankers -- Goldman Sachs and Avendus-- are preparing the bidding norms for suitors and are learnt to have stressed on the credential of promoters and details of their other businesses, if any, to avoid a similar situation which Satyam found itself in after its founder and Chairman B Ramalinga Raju disclosed fudging the company's accounts on Jan 7.

 

test2

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

Using Contribute the site administrator can control if a user of Contribute can delete the included ssi from the main page.

Sample web page using ssi:

   Mainpage.shtml

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>

<head>

<title>SSI Test</title>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

</head>

<body>

<!--#include virtual="/ssi/includes/inc_27.shtml"-->

<!--#include virtual="/ssi/includes/inc_28.shtml"-->

<!--#include virtual="/ssi/includes/inc_29.shtml"-->

<p>This text is from main page</p>

</body>

</html>

Inc_27.shtml

<p>This is a simple SSI test. The objects between the horizontal lines are within

an SSI.</p>

<p><img src="../images/contrib_team.jpg" width="209" height="122"></p>

<hr>

Inc_28.shtml

<p>&iexcl;Hola, mundo!</p>

<table width="635" height="353" border="1" cellpadding="3" cellspacing="0">

  <tr>

    <td><img src="../images/contrib_team.jpg" width="378" height="221"></td>

    <td bgcolor="#33CC33">&nbsp;</td>

    <td><h3>Hello, nested SSI!</h3>

      <p><em>Hello, nested SSI!</em></p>

      <p align="center"><font color="#669900" face="Verdana, Arial, Helvetica, sans-serif"><strong>Hello,

            nested SSI!</strong></font></p></td>

  </tr>

  <tr>

    <td width="397" height="122" bgcolor="#9966FF"><h2>&nbsp;</h2></td>

    <td width="90"><p align="right"><strong>Hello,<br>

      world!</strong></p>

    </td>

    <td width="122" bgcolor="#FFCC00">&nbsp;</td>

  </tr>

</table>

<p><font color="#FF3300" size="3" face="Georgia, Times New Roman, Times, serif"><strong>&iexcl;Hola,

mundo!</strong></font></p>

Inc_29.shtml

<hr>

<table width="129" height="62" border="1" cellpadding="3" cellspacing="0">

  <tr>

    <td>&nbsp;</td>

    <td>&nbsp;</td>

    <td>&nbsp;</td>

  </tr>

</table>

<hr>

Following is the result when you edit the main page using Contribute:

test1

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

 

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

server side includes

SSI – Server side includes are files in the server that contain html snippet to be included in different web pages. The web server takes care of replacing the include tag with the content of ssi file when it delivers the parent page to the client.

Why SSI ?

SSI helps you organize repeating code in you site better. A large website might have multiple pages having same header, footer, left/right margins or menus. But for ssi, same code has to be repeated in all the pages and maintaining them would become nightmare as the website grows. The same site can be redesigned to pull out the header, footer, left/right margins and menu code snippets into different ssi files. These ssi files can be included in different web pages. So in future any change in the general layout would require a change in corresponding ssi file only. There by enabling you to maintain the site effectively.

SSI include markup:

Common code can be removed from the parent page and saved as ssi file in the server. To get the content of the ssi in the parent page you will have to add include tag in the parent page. When the parent page is delivered to the client, the server takes care of replacing the include markup with the content of the ssi file.

 The syntax to embed the contents of an external file onto the current page is:

     <!--#include virtual="/ssifolder/myssi.shtml" -->

                            or

     <!--#include file="myssi.shtml" -->

      Virtual attribute can be used when the ssi is not in the same folder as the parent page.

      File attribute can be used when the ssi is in the same or sub folder as the parent page.

Typically you would be using the “virtual” attribute as it would be good practice to club all the ssi file in a folder and have the rest of the web pages in the site refer to them with a site root relative path.

Can I edit a webpage containing ssi in Contribute?

When you edit a web page using Contribute, it would pull the included ssi content form the server and render the full page like a web browser. The ssi regions in the page are locked. Hence you can not edit the ssi content in the main page. This is to prevent the user from accidently editing the ssi content, at the same time have the WYSIWYG feel when you edit the main web page.

 

 

test 2000

test1

TestSpeed

jdffkjdg fdhg fd ghf gfd gjhfd gjhfdg fd gdfg fdg fdjgfdgfgf

fd gfd gfdg fdhgfd ghfdg hfdg fdhgfd gdfhgr gh r g rfghrg

g egrf ghfj gre grehgr eg hre gr eghjg rehjgre ghre ger

regrehgreg rehg reg hhregreg hre ghreg reghre greg

rg rejhg rejhg rhej gre g hrg hreg regregre gr egr egregh

re gre grhe ghreg jhregjg hreg reg hjregregregrgere grjeg

hello this is fast enough..

TestWIP2

Quoted from http://10.192.37.25/krisftp/czech/TestWIP2.htm:

TestWIP2

Albus Pervical Wulfric Brian Dumbledore