Hallo,
wenn ich einen Beitrag veröffentlichen will bekomm ich immer einen Aufruf ob ich folgendes Skript weiter ausführen möchte wp-includes/js/jquery/jquery.js?ver=1.2.6:11 , drücke ich auf "weiter ausführen" wird der Beitrag normal veröffentlicht, jedoch dauert der ganze Spass einige Zeit ca. 1-2 minuten um einen Beitrag zu veröffentlichen. Habe dazu folgendes gefunden, jedoch ist mein Englisch nicht so perfekt, dass ich es so gut verstehe, dass ich die Änderung ohne Absicherung durchführn will.
erste idee war:
I found the problem with my site was that on writing a NEW post (not editing an existing one) there was a script that was loading the post meta for EVERY post-id in the whole database. In my case about 30,000 records. This killed the system. What I did was prevent the load of post meta by modifying the wp-admin\edit-form-advanced.php and removing the load of the custom fields meta.
<?php
$metadata = has_meta($post->ID);
list_meta($metadata);
?>
This fixed the problem and it loads very quickly now. May not be elegant but then again neither is loading every post in the meta!
könnte ich machen, in dem beitrag kam jedoch später ein einwand und folgende Lösung:
I went into my database to look at the metadata in a bit more detail. In the postmeta table, I noticed there were reams and reams of entries with post_id reference '0'. This suggested to me that it was actually these posts' meta (rather than ALL posts' meta) that were being pulled into the custom fields because they had no specific post id, so they acted like a wildcard.
Soooo... I deleted them all by hand. An absolute ball-ache, but as I'm new to all this, it was the only way (a search query threw up nothing).
After checking that there were no '0' post_id'd entries left, I backed it all up again, checked my site to see if any of the custom field-related items were affected (they weren't), re-added the code Gary took out of edit-form-advanced.php and checked the Write Post once again. No renegade custom fields. Checked the Manage Posts again, and the custom fields were back.
I don't want people to see this as 'the answer' because I really am a novice at databases and wouldn't want to put false information out there. But this did work for me, and I think its quite important because using Gary's hack will mean that a wrongly-entered custom field will disappear into the database, and potentially cause problems if you can't edit it from the post page itself.
versteh ich schon weniger??
die komplette Diskussion gibts hier
freue mich über hilfe, denn die ladezeiten machen mich kirre