 |
|
|
 |
This is a wordpress plugin, it's purpose is to create pages navigation using the wp_list_pages() function that includes dynamic menu highlighting of all parent pages. By simply adding "current_parent" into the css of all parent pages, it is hence possible to highlight the parent of the current page. While on current pages, a css tag of "current_page_item" will be added.
 Click here for a simple example.
To install this plugin: - Download this plugin.
- Upload this plugin to "wp-content/plugins" folder.
- Go to "Plugin Management" and activate it.
To uninstall this plugin: - Go to "Plugin Management" and deactivate it.
Compatible with Wordpress 2.0 and above. To run the plugin, insert the following code into "sidebar.php" or "header.php": <ul>
<?php if ( function_exists(wp_list_pages_seigey) ) wp_list_pages_seigey('sort_column=menu_order' ); ?>
</ul> Please note that all queries are the same as those in wp_list_pages(). For example: sort_column, exclude, depth, title_li,
What does it do?
Changing the ID column into Page Order (menu_order) column in Page Management. Note: this is not a wordpress plugin although there are plans to make it so.
Why is this made?
The Wordpress Page Management list each page along with its ID, Title, Owner, Updated details and editing buttons. However more often that not I find there's a need to see the Page Order when sorting pages out and I feel that instead of listing the Page ID, the Page Order will be more useful.
How to change it?
There are three parts to change in two different pages:
- wp-admin/edit-pages.php
Find this on line 34:
<th scope="col"><?php _e('ID') ?></th> Replace with this:
<th scope="col"><!-- 061114 Seige --><?php _e('Order') ?></th>
Find this on line 47:
<th scope="col"><?php echo $post->ID; ?></th> Replace with this:
<th scope="col"><!-- 061114 Seige --><?php echo $post->menu_order; ?></th> - wp-admin/admin-functions.php
Find this on line 638:
<th scope="col"><?php echo $post->ID; ></th> Replace with this:
<th scope="col"><!-- 061114 Seige --><?php
if ($post->post_status == 'static') {
echo $post->menu_order;
} else {
echo $post->ID;
}
?><!-- 061114 Seige --></th>
And now you can easily make changes to page order whenever you want to add new pages.
While we are constantly complaining about how much Blogdrive can improve, let's take a moment to be reminded of all the good stuff we have here on Blogdrive that you shouldn't have known.
If you are reading this article right now you should turn off the lights and make sure there's nobody behind you. If you are discovered to have obtain these information, an assassin will be sent to murder you.
1) Built-in search feature - Search your own blog with the blogdrive's built-in search feature, it's originally only available for subscription blogs but if you use a GET method on your url, you'll get a free (temporary) feature. However, it only search your blog titles.
2) exceed your bandwidth - for free accounts, an allocated amount of 50mb monthly bandwidth can be exceeded even without any upgrades. If you have a subscription blog, your allocated monthly bandwidth will be higher but again your files will not fail to load in the event that you exceeded it. So, what are you complaining about? (please note: you can't store more than what you should)
3) store HTML / CSS / JS documents in your filemanager with .jpg extensions. Okay, this is supposed to be a techy hack but it works.
4) the amazing Seige - this isn't just a goodie thingy but the coolest lad I've ever known on Blogdrive. He's smart, brilliant and above all massively fantastic. Oh, did I mention that he's got a great sense of humour?
Do you have other ideas or suggestions?
Tags: blogdrive secrets goodies
Everyone's been lovey dovey over the new WYSIWYG editor (JfZ, future, forum guide, hacks) While I, despite my initial "enthusiasm", still think that it has lots of problem room for improvement.
The WYSIWYG editor is at the very core, the most important feature on Blogdrive. Without it... you would be wondering how a blog host can ever be a blog host. And we really don't expect writers to be able to write properly, right?
1)  Insert Link opens a new window? This has to be the most annoying small problem. Everytime I need to insert a link, I'll need to wait till the new window loads before I can do anything else. This is a pain especially on MSIE because it takes a long time for MSIE to open a new window. Blogdrive should really just reduce to using a "prompt" javascript function to do the magic. It's less complicated and faster. Not to mention no new HTTPrequest to the Blogdrive server while editing.
Another problem is that it'll not work if the text you highlighted contains an apostrophy ' or ' . For example if you write: "Seige's dog", and wanting to add a link to these words, it'll not copy the "Seige's dog" to the window. This is a Javascript bug.
2) Different browser syntax rendering - on Firefox it's "XHTML Transitional" while on MSIE it's "plain old HTML" with CAPITALS. You can notice the differences if you use the "HTML View" feature located at the right bottom of the editor. It's odd although
3) Up Down Left Right button doesn't work sometimes - can't move the focus of the text cursor basically but the weird thing about this is... it only happen sometimes. And as for me, I can't identify what is the source of this problem.
4) In HTML View, the text cursor isn't always where it should be - more often than not it appears to be one or two characters away. How and why this happens is a mystery. It usually happens when I have a long entry that I needed to edit. It has something to do with miscalculating the string lengths or something along those lines.
5)   Undo/Redo doesn't work sometimes - Again, this is odd and I can't tell why it doesn't work. It happens to both Firefox and MSIE.
6)   Outdent/Indent uses different elements sometimes - I would really prefer the editor to implement the <BLOCKQUOTE> elements, it works great on MSIE but on Firefox, it uses <div> with margins set to indent it... how cruel.
7) Save post to clip board works on MSIE only - it doesn't work on Firefox mainly because Firefox is stupid for not supporting the copy-to-clipboard function. Sadly.
8) Firefox browser crash when reloading editor sometimes - Again, this is another one of the "sometimes" problem. It's just weird and I just can't make it out why. Don't take me wrong that it could be other webpages I'm viewing because the window crashed a few times and it's always during reloading of the editor in Firefox.
9) Can't insert Scripts or Objects - That's due to security reasons but for someone like me who do need to use some Javascripts, it's  . Though... I shouldn't fret because I still have the beloved PTE.
10) Help Guide is coming soon ever since the big bang - See that "?" up there on the top right hand corner? Ever clicked on it, No? Don't bother.
I somehow realise that all these problems have almost everything to do with browser inconsistencies. Still I don't see why an editor should be flawed just because of certain browser not working perfectly well.
Wondering if Blogdrive will ever be bothered to fix these minor things? Nah, never. Not in a century or two.
Ever since Blogdrive fixed the PTE, it has so far been a million times better than WYSIWYG editor. Although it doesn't mean it's all great (because it doesn't work all well in Firefox/Opera), it's still better than WYSIWYG editor.
Tags: Blogdrive, WYSIWYG, Plain Text Editor, PTE, Editor,
*Updates* Blogdrive fixed the Plain text editor.
Since Blogdrive's PTE isn't going to be fixed anytime soon, I've decided to write up my own fix for it since I can't use the greasemonkey fix that was created by Xr.
Here's the link and features surrounding it:
1) URL is similar to that of blogdrive
http://design.blogdrive.com/manage/blog_entries?big=123456&pid=
http://www.blogdrive.com/manage/blog_entries?bid=123456&pid=
2) includes Extended Entry and Keywords.
3) behind the scenes features: dates automatically changes to current time
4) behind the scenes features: BID/PID auto updates from the URL.
5) behind the scenes features: inserting images in old fashion.
6) Not able to call up your previous entries contents. It does not enable editing of previous entries however it allows you to REPLACE it.
7) I tried to include Amazon affiliate thing to this, but I realised there's a server indifference here that disallow variables to be passed through. So I have no choice but to disable it.
So, there you go.
Instead of moaning of the problem over and over again, Xr decided to write up a GreaseMonkey fixer for the BlogDrive PTE Posting Dates problem. Greasemonkey is a Firefox extension which lets you to add bits of DHTML ("user scripts") to any web page to change its behavior. If you uses Firefox and have the Greasemonkey installed on your computer, You may use this tool. Download the script here. Below are the details, note the explanation: Blogdrives gives the time based on configured timezone. However, when creating a new entry, "Current" doesn't mean anything. In those cases, the hours are set to local time. Think about it if the machine from which you edit your blog is not set to the same timezone as your blog. // Blogdrive PTE Fixer v 0.2.2
// Copyright (c) 2006, Xr
// Released under the GPL license
// http://www.gnu.org/copyleft/gpl.html
//
// This is a Greasemonkey script. if you don't have GM, go to
// http://greasemonkey.mozdev.org/
// GM is an extension for Firefox (http://www.mozilla.com/firefox/)
//
// Known bugs :
// - Blogdrives gives the time based on configured timezone. However, when
// creating a new entry, "Current" doesn't mean anything. In those cases,
// the hours are set to local time. Think about it if the machine from which
// you edit your blog is not set to the same timezone as your blog.
//
// Version history :
// 0.2.2 : Fixed date systm where "09" would be interpreted as octal
// Fixed date showing GMT instead of local time.
// 0.2.1 : Title is not lost anymore
// 0.2 : Moved to a better way of getting input field, fields are now selected
// depending on posted date / current date
// 0.1 : Initial script
//
//
// ==UserScript==
// @name Blogdrive PTE Fixer
// @description Allows Plain Text Editor to correctly edit dates
// @namespace http://xr.i-jeuxvideo.com/?cat_id=progs
// @include http://www.blogdrive.com/manage/blog_entries*
// ==/UserScript==
// Get the invalid <input> field. I have not tested it, but looking through the codes it appears to be doing it right since it's well organised and written. Try it out if you uses Greasemonkey. References: Plain Text Editor (PTE) bugs and issues, Dates of Edited Posts, Can't Change My 'Publish Date', BlogDrive PTE Fixer, Greasemonkey,
Tags: BlogDrive, WYSIWYG, Editor, Firefox, Greasemonkey,
A couple of days ago, BlogDrive added some divs tags to all [blog title] texts, wrapping them up and labelling them with a unique ID:
<div id="XXXXX_kdub1">[blog title]</div> XXXXX being some random number. This change has caused some of the scripts I did not work properly. Luckily, it's not a very big change so it's not exactly obvious. Or rather, I'm just a damn good javascript programmer that the scripts just degrade gracefully automatically. *wink* Right, the scripts can be fixed. So, it's not something to worry about since all it needs is my time to sit down and remanipulate the [Blog Title] strings to omit the divs. The problem lies in all the completed, flawless templates. There are more than two hundred fifty of them, and I don't think there's is anytime to look at all of them, and determine which is would fail. Also, my previous method of using [blog title] in <title> tags (to aid in search engine ranking) would now fail to serve any purpose. Maybe BlogDrive should do that automatically for permalink pages, since it'll gain search engine ranks. It's a win-win situation if they do it, since both bloggers and BD gain popularity. However, there might be some specific yet unknown reasons why they have not implemented it. Contrary to what many people thinks, getting ranked in Google is actually much more of a compliment than "leaving tracks on the internet". If you want to blog, you should know well enough what you are opting for.
|
 |
 |
 |
|
 |
|
|
|
|
 |
Click here for a simple example.
