Dylan Kuhn

Could be related to this Firebug issue:

https://code.google.com/p/fbug/issues/detail?id=1565

I think I’ve tracked it to Firebug 1.3.3 (w/ Firefox 3.0.7). No problem when that’s disabled.

I spoke too soon, the problem showed up again. When loading post.php?action=edit&post=x, something seemed to be causing a redirect. Sometimes I would get the dialog asking if I’m sure I want to navigate away from the page without saving. No matter how I responded, the page would appear to redirect. Sometimes I’d get the row of HTML editor buttons at the top of the new page.

Now with all my Firefox extensions disabled, it seems to be working again.

I starting having a problem like this today. I had the Google Gears extension installed with Firefox. Disabling that extension has resolved the problem for me.

Hey Chase,

Thanks for the link, I’m sure that will come in handy for myself and others.

So if you want to use the delta method, you’ll have to record your weight gain or loss instead of your current weight. I suppose I could make a method that treats each point as a new total, I just didn’t think to do it that way.

The underlying trouble here is that the API will not treat the X axis as a timeline and plot data points for you. Or it will, but the points are always equally spaced, with no sense of the actual time between them. That’s why tally graphs always have some fixed number of time intervals, so the time scale isn’t lost.

Let’s start a separate thread for the week interval problem so I can track that as a bug. I’ll start it.

Hi Chase,

It looks to me like you do want to use the delta method. The documentation for that says:

The delta method computes a running total, adding changes to the total for each interval. This can be used for data like weight loss and gain, where an initial entry is made with a starting weight, then gains and losses are recorded as positive and negative values.

I think if you change your field values to do that, you’ll get the result you’re looking for.

It does look like you may have found a bug with the weekly tally – probably it comes from difficulty with week numbering at the beginning of the year. Try it with some different interval counts, perhaps. We can work on that if it continues to be troublesome.

Cool, glad TG caught your fancy. You can pass any parameters accepted by the Google Chart API to Tally Graph. They’re cryptic, and in the future I may be able to put a friendlier interface on top of them, but you can accomplish a lot with them.

If you figure out the right parameters for what you’re trying to do, post ’em here for others! If you’d like some help, I may be willing to do some of that kind of support here if my beer fund isn’t dry ??

I’m curious about this too – anyone know what’s up?

Thanks, I’ve been wondering how to do that.

I should probably try it before piping up, but what if you followed the example here

https://codex.www.ads-software.com/Alphabetizing_Posts

but with &orderby=cat_ID,postID ?

Talking to myself in here again, but maybe someone else will benefit. The problem was that my main blog is now on a page, and pages are aparently assumed to have only one post, so &paged=2 returned no posts instead of the one post for that page. I solved the problem in my .htaccess file with these lines:


RewriteRule ^(blog)/page/?([0-9]{1,})/?$ /index.php?pagename=$1&pgd=$2 [QSA,L]
RewriteRule ^(blog)(/[0-9]+)?/?$ /index.php?pagename=$1&pgd=$2 [QSA,L]


The key is using ‘pgd’ instead ‘paged’, so the initial query returns the one bogus post for page ‘blog’, and the blog.php template is correctly used. Then, in that template:


<?php $qy = preg_replace('/page_id=d*&?/','',$_SERVER['QUERY_STRING']); ?>
<?php $qy = preg_replace('/pagename=w*&?/','',$qy); ?>
<?php $qy = preg_replace('/page=w*&?/','',$qy); ?>
<?php $qy = preg_replace('/pgd=(d*)(&?)/','paged=${1}${2}',$qy); ?>
<?php $qy = $qy==''?'orderby=date':$qy; ?>
<?php query_posts($qy); ?>
<?php extract ($wp_query->query_vars); ?>
<?php if (have_posts()) : while (have_posts()) : the_post(); ?>


Here I turn the ‘pgd’ back to ‘paged’ for the real query that pulls up my blog posts. I included the beginning of The Loop for context. The extract() call is necessary to get posts_nav_links() to work later in the template.

Very pleasing to look at, and read.

I posted a hack for a button that will switch the current order, leaving other parts of the query (date, search, category, etc) intact:
https://www.ads-software.com/support/10/2889

The Oct 29 entry provides a way to get old linebreaks out – I’m seeing linebreaks being put in where they shouldn’t be. I’m wondering if it might be because I’m on Mac OS X and there is some difference in regexp handling in PHP… ??

I have the same problem on OS X 10.3 with an out-of-the-box setup (sorry, not on the web so no URL). My theory is that MySql on OS X doesn’t sort by date correctly, but I don’t have time now to investigate fully. I’m ordering by “ID desc” for the moment, but this isn’t a permanent solution. Eventually I will try to put together a test case and see if I’m right.