Manual installation instructions for webReader for blogs


These are the instructions to follow if you want to implement webReader for your blog and cannot use any of the supported blog platform Widgets or plug-ins that we offer.

For blogs, the first page is usually a long list of posts created by the author. This means that there need to be one listen button for each post that webReader shall read. This is done by letting webReader read the page pointed to by the post's permalink.


There is also the option to only place the webReader button on the page pointed to by each post's permalink instead of implementing webReader on the blog's first page. If that is what you would like to do, you should use the implementation instructions for websites found here


To make a successful implementation you would need to have the rights to add code to the blog pages or blog page templates.


These are the steps you need to take.

Insert the following script declaration somewhere between <head> and </head>:



Insert the HTML code below where you want the webReader button to appear.



Define the reading area


If you do not want the complete page to be read you can easilly control where the reading should begin and end. Add these HTML comments to your web page or webpage templates

Start the reading:
Stop the reading:

Multiple buttons per page (i.e. blog first pages)


When installing webReader on a page with multple posts, you need to have a unique identifier.


First, in the call to the JavaScript function "readspeaker":


onclick="readpage(this.href+escape(document.location.href),1); return false;">


Change the 1, to the unique identifier (it can be for example the posted of the posts unique ID (string or integer).


The same unique identifier you need to set instead of the 1 in the code looking like this:


<div id="WR_1"></div>


Remember also that you need to insert the start and stop comments into the permalinks template to define the reading area.



If you are experiencing any problems, please visit the Customer Support page.