Welcome to Vasudevaservice.com

This plugin will show the draft posts created in all your WPMU blogs. To activate, just download the PHP file and put it in your wp-content/mu-plugins folder. The file can be downloaded here....

To view all posts, click on 'Site Admin' and then on the 'Posts for moderation' submenu.

To do: make 'view' and 'edit' links, a bit like the Wordpress 'manage' interface actually. In any case, it's probably best if each theme you supply has an 'Edit this post' link, so the moderator can first view the post and then edit it if necessary without going back to admin screen.

To embed a quicktime video, use the following code:

<object width="400" height="274">
<embed src="video.mp4" type="application/quicktime"
  wmode="transparent" width="400" height="274" autoplay="true">
</embed></object>

The autoplay argument determines whether the video plays or not immediately the page is loaded.

There are also other arguments you can add just like autoplay:

• loop="true"/"false"— the movie plays once or continuously.
• controller="true"/"false" — toggles the playback controls e.g. pause, fast forward, or mute.

The full range of options are available on the Apple Quicktime site:

http://www.apple.com/quicktime/tutorials/embed2.html

 <object width="400" height="274">
<embed src="images/preview_image.mp4" href="video.mp4" target="myself"
  type="application/quicktime" wmode="transparent" width="400" height="274"
  autoplay="false"></embed></object>

Plone 3.0.5 came out on January 7, 2008.

Full release announcement

If you have a very popular blog it might be worth dividing your comments into pages for easier viewing. Fortunately there is a Wordpress plugin called Paged Comments to do just that, thanks to Keyvan Minoukadeh. However it needs a bit of tweaking to work on your site.

<?php // Do not delete these lines
    if ('comments.php' == basename($_SERVER['SCRIPT_FILENAME']))
        die ('Please do not load this page directly. Thanks!');

  <!-- Comment page numbers -->
<?php if ($paged_comments->pager->num_pages() > 1): ?>
 <p class="comment-page-numbers"><?php _e("Pages:"); ?> <?php paged_comments_print_pages(); ?></p>
 <?php endif; ?>
 <!-- End comment page numbers -->

<div class="comment-number"><?php echo $comment_number; $comment_number += $comment_delta;?></div>

1. Ok, basically if your blog is a new Blogger blog (after it was acquited by Google and Google usernames introduced) first step is to be sure have Wordpress 2.2.

If you have an old version of WP, you can always upgrade:

http://codex.wordpress.org/Upgrading_WordPress_Extended

Wordpress 2.1 allows you to upgrade from Old Blogger blogs, but not New ones.

2. If your Blogger blog is hosted via FTP, go into the settings of the blogger blog and turn it into a blogspot blog (this change is reversible if anything goes wrong). Your blogger blog url will now be at (some name you choose).blogspot.com
3. Go to your blog admin on your WP blog. Go to Manage -> Import and select the 'New Blogger' option. You will be asked for your blogspot url, blogger username and password. And hey presto, the job is done! (You might want to verify that before we go on)

Some recent users may have trouble signing into their Google account from Wordpress due to the fact that Blogger changed their hostname API:

http://wordpress.org/support/topic/131952?replies=2

As you can see here, you just need to make a simple change in wp-admin/import/blogger.php file, changing www2.blogger.com in line 84 to www.blogger.com. This will be automatically fixed in Wordpress 2.3.

4. Ok, here is the time consuming job, setting up redirects from the old posts to the new, so that if someone clicks on a link to the old address they are automatically forwarded. Make sure you first are happy with the permalink structure on your WP blog (Go to Options -> Permalinks to change this)

Now open up some text editor to write the redirects. Suppose your old blogger blog was at

http://www.mysite.com/{old address}

and your new WP address is at

http://www.mysite.com/{new address}

basically all you do is type

redirect 301 /{old address} http://www.mysite.com/{new address}

301 is basically a code that tells Google that the item has permanently moved to the new address and you aren't trying to pull any funny stuff on them. For each entry, type in the proper 301 redirect on a separate line. You can still get the old url address by looking at the blogspot blog.

You need to type in the full URL of the new address. Why? Basically, it allows you to redirect your posts to entries on a completely different site if you so choose!

Now you need to use an FTP client to go into the filesystem of where you host your blog. At root there should be a file called .htaccess; if not, create one (all files with . in front are system files and might be hidden unless you tell your FTP client to show hidden files). Then just copy and paste your redirects into this file, save, and try it out by typing in an old blogger address

5. I've heard (although i don't know the logic behind it) that its good to keep the FTP site going for a couple of days. So go to your Blogger blog and move it back to ftp, and then delete it after a few days.

This is actually an email response I sent to a friend who was asking about this sort of thing. It kind of complements Richard's blog post below.

There are a number of programs out there to make the life of people designing websites much easier. Choosing the right one depends on what kind of website you want - so you need to ak yourself the following questions:

1. Are you designing a completely new site, or are you putting a new design to an already existing site?

2. Is your site big (greater than 30 pages) or small (less than 30 pages)

3. Do you see the site as a project that will take a finite amount of time (15-20 pages and then stop) or will it be an ongoing project and pages will be added as time goes on?

For small, finite sites we recommend using a very easy to use design program called Dreamweaver, which is expensive. There are also free equivalents of Dreamweaver which Richard mentioned in his blog post.

However, these programs can be a little inefficient if you want to add lots and lots of content very quickly - there are specialised programs called Content Management Systems that handle this much better - for example the Plone program used to manage content on this very site (there are also other programs like Wordpress (used primarily for personal sites and blogs), Alfresco and Drupal. The only problem is sites using Content Management Systems often start out looking not quite the way you envisioned them (and perhaps even a little ugly). With some technical expertise you can also make these sites as beautiful as Dreamwaever sites, but it will take longer to learn, especially if the people you have in mind to work on the project have no computer experience.

Finding a good, reliable web host is not easy.

It is important to bear in mind:

1. How much traffic will your site have? - Most sites start off small, but if traffic increases, you may need an option with more bandwidth available. E.g. small packages may start from 2GB per month.
2. Do you need optional extras? For example, wordpress blog.

Some Web Hosts worth Considering

1. SiteGround - $6.00 per month.

Supports Wordpress, High Bandwidth and disc space capacity.

2. Small Orange tiny packages from $25 per year.

Supports Wordpress and AWStats, Tiny package has small bandwidth, but can upgrade to higher bandwidth.

3. Pow Web $6.00 per month

Supports Wordpress, AWStats, High Bandwidth.

4. Heart Internet from $5.00 per month

Wordpress not available on cheap package, but is on more expensive.

5. Streamline.net from $28 per year.

Cheap if you want unlimited bandwidth and disc space. Wordpress is supported, but need to install yourself.

Photo: Projjwal Pohland .

In Linguaplone, the one thing that you can't translate is the portal itself. Hence if you have any documents or folders at site root, then they will be translated into documents or folders also at site root. It is easy to see how (especially with more than two languages) things can get very messy indeed.

However there is a way around this if you have your site address directed to a folder at the root of the portal, public_home, say (in my opinion this should be Plone default behaviour to stop user content from being scattered around portal tools in the zmi). You can then translate the folder and the translated folder will show up on the same level as public_home. (You can even translate some content inside the folder before you translate the folder and LinguaPlone will put the content inside the folder for you)

However, perhaps you want all content - including translations - to be inside the public_home folder for ease of maintenance. Well, after you translate the folder, you can go into the zmi, cut the folder and paste it within public_home. This doesn't seem to have any effect on the links between original and translated folders, or on any content translated after you move the folder, and you now have all the content for each language inside their respective folders inside public_home.

Anyone who has tried to add images using the csv-table directive in restructured text may have come to the following conclusion: it can't be done. Well certainly not using any of the existing attributes or syntax for tables (an oversight?), but it can be done with the replacement directive.

Firstly, a csv-table in restructured text looks like this:

Currently Held Records

No	Category	Details	Record	Date	Photo
1	Somersaulting	Longest continuous distance	12 miles 390 yards	Apr 1986

And would created with the following code:

.. csv-table:: Currently Held Records
  :header: "No", "Category", "Details", "Record", "Date", "Photo"
  :widths: 42, 270, 270, 220, 119, 119

  1, "**Somersaulting**", "Longest continuous distance", "12 miles 390 yards", "Apr 1986", |green_face.jpg|

Ignore the first three lines—it's the table structure info, similar to the way you would define an image, but instead defining table column titles and widths. Should be pretty obvious how to change anything there, but in case not, let's recap a few csv-table fundamentals, as it is important in restructed text that formatting is followed precisely—right down to the space and comma:

• a single space after each comma—no other spaces
• bold text like **this**
• all text inside "quote marks"
• numbers don't need to be in quote marks, unless together with text: "12 miles 390 yards"
• return at the end of the line

The last line is an example of a row of the table, and more importantly contains the image:

1, "**Somersaulting**", "Longest continuous distance", "12 miles 390 yards", "Apr 1986", |green_face.jpg|

The image is the complex, for “|green_face.jpg|” (without quotes) is actually a “replacement” for the image definition, somewhat akin to an ID in css or a variable in pretty much any programming language you could name.

The image url, link and any other image parametres pointed to by the replacement id then get defined below the table (ie at the bottom of your reSt document):

.. |green_face.jpg| image:: green_face.jpg
  :target: green_face.jpg

Note:

• The spaces are important as usual, as is putting the info on two lines
• the name of the replacement/id can be anything, but it makes sense to me to use the image name
• you can use the same image two times (or more) but only define the replacement once.