Forum Replies Created

Viewing 15 replies - 91 through 105 (of 117 total)
  • Thread Starter mystifier

    (@mystifier)

    Thanks for a fast response Elfin, but the shipping page simply calls the module: [eshop_show_shipping]

    I can’t find a way to manage the values.

    Is it possible to set a shop to show simply three prices and two zones (UK/International).

    Thanks again.

    Thread Starter mystifier

    (@mystifier)

    Incidentally, I use a managed server so I don’t have access to apache/php so I can’t for example, see httpd.conf etc.,

    My ‘root’ looks like:

    -site1
    –wp-content
    –wp-includes
    -site2
    –wp-content
    –wp-includes

    -siteX
    –wp-content
    –wp-includes

    Thread Starter mystifier

    (@mystifier)

    Thanks samboll, I think I have figured it out now.

    You will have to delete revisions in the database; there is, strangely, no current provision from WordPress.
    i.e. Delete from wp_posts where post_status=’revision’ and ….

    You can restrict the number of revisions by adding
    define (‘WP_POST_REVISIONS’, X);
    to wp-config (where X is the number of desired revisions, default=until your database falls over with the burden).

    Yo! Now I am happy.

    By running clean-up SQL:
    > Delete from wp-posts where post-status=’revision’
    and adding to wp-config:
    > define (‘WP_POST_REVISIONS’, 0);
    > define(‘AUTOSAVE_INTERVAL’, 600); // One hour should be long enough!

    I don’t get masses of large unwanted duplication and I can simply click Save whenever I want to without having everything duplicated with unwanted auto-saves every minute.

    It was BAD judgement that the majority of users would love this extra database content.

    Yo! Now I am happy.

    By running clean-up SQL:
    > Delete from wp-posts where post-status=’revision’
    and adding to wp-config:
    > define (‘WP_POST_REVISIONS’, 0);
    > define(‘AUTOSAVE_INTERVAL’, 600); // One hour should be long enough!

    I don’t get masses of large unwanted duplication and I can simply click Save whenever I want to without having everything duplicated with unwanted auto-saves every minute.

    It was BAD judgement that the majority of users would love this extra database content.

    Thread Starter mystifier

    (@mystifier)

    My apologies, define(‘WP_POST_REVISIONS’, false); DOES work!

    I was confused by the new auto_save which happens regardless as a single ‘revision’. I would rather not have this either because it will double my database but I can live with it. My main problem was that because of the nature of my site, large posts get many revisions.

    I don’t like code hacks because they have to be re-made every update but I may hack auto_save to kill it.

    My apologies, define (‘WP_POST_REVISIONS’, 0); DOES work.

    When I tested, I was confused by the new auto_save which happens as a single ‘revision’. I would rather not have this either but I can live with it; my main problem is that because of the nature of my site, large posts receive many minor revisions.

    After every session, I run clean-up SQL:
    Delete from wp_posts where post_type=’revision’;

    It is hopefully a temporary inconvenience until some control is given to revisions; at the moment, it is an abortion.

    Simplest way now is to run SQL:

    Delete from wp_posts where post_type=’revision’;

    define(‘WP_POST_REVISIONS’, false);

    Doesn’t work. Large unwanted posts are simply added following every minor revision. My database has grown massively.

    “I bet you’re the kind of person who actually goes through and deletes old email too, right?” – Well, surprisingly yes; since I receive tens a day that makes very good sense.

    This is a very blase approach that has resulted in the worst ever WordPress version change. The number of stored Revisions (0 in my case) should at very least be controllable. Quadrupling the size of my database with unwanted posts makes 2.6 unusable and already, my phpadmin imports (controlled by my host not me) have to be split into sections.

    Bloody infuriating mess up of a blog tool I have always revered. I will try to revert to 2.5 until it is ‘fixed’.

    I wish!! In the current 2.6, there is no wp_post_revisions table; revisions and simply included in wp_posts and not so easy to get rid of.

    My table has grown massively with unwanted large posts that are unconditionally added. I am seriously contemplating reverting to 2.5.

    Thread Starter mystifier

    (@mystifier)

    define(‘WP_POST_REVISIONS’, false);

    Does not have the desired effect. I correct one character and it unconditionally saves a whole new version of a several hundred word post.

    At the moment, I am bitterly regretting upgrading 🙁

    Thread Starter mystifier

    (@mystifier)

    My site has over 300, sometimes long posts – the last thing I want is five or six versions of them; this would certainly exceed the phpadmin import filesize on my hosting package requiring that I split it.

    Thanks for the wp-config entry, I will try it after I have hand deleted tens of unwanted posts 😉

    Strongly agree. I can see its use for multiple authors but for me, it simply generates annoying unwanted database entries.

    I can’t even see yet how to delete unwanted revisions.

Viewing 15 replies - 91 through 105 (of 117 total)