kesp

the data in wp_redirection_logs has no value to me.

Is it worth considering deleting these tables and reinstalling the plugin?

Or perhaps emptying the tables of data?

Hi again,

I just used better delete revision to optimise the db and now i’m only left with a few errors:

mydomain_697250_db1.wp_redirection_logs check Table is marked as crashed
mydomain_697250_db1.wp_redirection_logs check 5 clients are using or haven’t closed the table properly
mydomain_697250_db1.wp_redirection_logs check Found 85453688 deleted space in delete link chain. Should be 85472584
mydomain_697250_db1.wp_redirection_logs check Found 384384 deleted rows in delete link chain. Should be 384386
mydomain_697250_db1.wp_redirection_logs check record delete-link-chain corrupted
mydomain_697250_db1.wp_redirection_logs check Corrupt

These are related to the Redirection plugin.

Do I really need to restore the entire db just because of these few tables?

Kes

I have a back up from last week

Still a fair bit of work lost.

May see if host has something more recent.

Thanks,

Kes

Hi Tara,

I did that and got those messages and the advice to post them on here.

Kes

Just heard it was a wordpress bug that has been fixed in the latest update

Case closed

I’ve also been trying this method but still not having much luck

<?php
$tags = wp_get_post_tags($post->ID);
if ($tags) {
//echo 'Related Events';
$first_tag = $tags[0]->name;
//echo $first_tag;
$querystr = "
SELECT $wpdb->posts.*
FROM $wpdb->posts, $wpdb->postmeta
WHERE $wpdb->posts.ID = $wpdb->postmeta.post_id
AND $wpdb->postmeta.meta_key = 'festivalKey'
AND $wpdb->postmeta.meta_value = '". $first_tag ."'
AND $wpdb->posts.post_status = 'publish'
AND $wpdb->posts.post_type = 'page'
ORDER BY $wpdb->posts.post_title ASC LIMIT 10
";

$pageposts = $wpdb->get_results($querystr, OBJECT);

if ($pageposts):
global $post;
foreach ($pageposts as $post):
setup_postdata($post);

?>

<a href="<?php the_permalink(); ?>">
            <?php echo get_post_meta($post->ID, 'festivalName', true); ?>  </a>

<?php
endforeach;
else : 

endif;
}

resolved

The answer ??

it looks exactly like:

AND MONTHNAME($wpdb->postmeta.meta_value) = 'October'

resolved

Or it could look something like:

AND DATENAME(MONTH, $wpdb->postmeta.meta_value) = 'October'

Sorry to bump up but just had some more pseudo code thoughts.

What i’m trying to achieve might look something like:

SELECT $wpdb->posts.*
    FROM $wpdb->posts, $wpdb->postmeta
    WHERE $wpdb->posts.ID = $wpdb->postmeta.post_id
    AND $wpdb->postmeta.meta_key = 'festStartDate'
    AND date("F", strtotime("$wpdb->postmeta.meta_value")) = 'October'
    ORDER BY $wpdb->postmeta.meta_value ASC

But not sure how you add that kind of date manipulation to a query…

Hey bc,

That works a treat – thanks!

So essentially, we’ve grabbed the current post ID, put it in the array exclude_featured and then inserted the post ID’s from the first loop in exclude_featured as well.

Then in the second loop exclude everything in exclude_featured

Have I got that right?

Cheers,

Kes

Hi alchymyth,

Thanks for the reply.

I just gave that a try but no change to the output..

Kes

Hi esmi,

I’m on a vps so my host only provides so much support. However, I think under the radar a very helpful chap fixed the table because the site is all working fine now. (at least on the face of it)

Anyhow, i thought now would be a good time to take a back up. Problem is, i think the db might be too big to download because phpadmin and sqlbuddy are both crashing when i try to download.

I’m going through all the revisions and deleting those manually.

But i’m wondering if there is anyway I can backup a copy of the db.

I know i should have been doing this more frequently before but it’s only a 1000 page blog and i kind of thought that i’d have way more than enough resources before i started needing to worry about overloading the db (if that is whats happened)

Any pointers, tutorials you can recommend for backuping up this db without phpadmin or sqlbuddy?

K

Hi esmi,

if it’s only the wp_options table that has crashed is there anyway to repair just that table or use the backed up version of that table?

I don’t mind losing info in the wp_options table if it’s just things like colour settings but tables like wp_posts might have lots of work in them that i don’t want to lose if i revert back to a February version if i can help it

K

Hi esmi,

The only one I can find is from 11/2/2013