edit-post-rows.php in WordPress 3.0.4 - CoreFiles

CoreFiles by mySites.guru

Use CoreFiles from your AI agent

# CoreFiles

> The original files of every Joomla and WordPress release, run by mySites.guru. Free, no API key, read-only GET requests.

Use it to tell whether a file on a Joomla or WordPress site is an unmodified core file, which release it came from, and what changed between releases. Hash the site's files where they are and send only the hashes; never upload a site's files.

Base URL: https://corefiles.mysites.guru
Platforms: joomla, wordpress. Versions as released, for example 5.4.0, 6.2.0-rc1, 7.1.4.
Add ?format=json to a page URL (/lookup, /pretty, /folder, /history, /diff, /stats) for the same data as JSON.

## Look up a file by its hash

GET /lookup/{md5 or sha256}?format=json&name={file name}
Lists every release and path that has this content. No matches means it is not a core file in any stored release. With name, "named" lists core files that have that file name, so you can fetch the original and compare.

## Read a core file

GET /raw/{platform}/{version}/{path}        the file's bytes
GET /stat/{platform}/{version}/{path}       md5, sha1, sha256 and size as JSON
GET /history/{platform}/{path}?format=json  the releases where that file changed

## Compare releases

GET /diff/{platform}/{from}/{to}?format=json         added, removed and changed files
GET /diff/{platform}/{from}/{to}/{path}?format=text  a unified diff of one file

## Check a whole site

GET /hashes/{platform}/{version}/plain
Every core file in that release as path<TAB>md5. Hash the site's files and compare: a different md5 means a modified core file, and a file missing from the list is not core.

## Reading the answers

A 404 with X-Corefiles-Release: present means the path is not in that release, so the file is not core.
A 404 with X-Corefiles-Release: missing means that release is not stored yet. Treat the answer as unknown, never as "not core". New releases are added within the hour.
GET /releases.json lists every stored release.

Paste it into Claude, ChatGPT or Cursor. Agents can also read it at /llms.txt. On a lookup, file, history or compare page, Copy for your AI agent adds what that page shows.

edit-post-rows.php34 lines, 617 bytes, from wordpress-3.0.4.zip

Raw History Compare with 3.0.3

md5: 98b07977eb3f0ea718ffadad63bfa079
sha1: 55469ca9fcc0e931f644286ef62eff3510b826d5
sha256: 0d9ed209cf5075fb3ddd23b0c0f9f1c7b70472d8320d38992b9182f9a307c0ee

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

<?php
/**
 * Edit posts rows table for inclusion in administration panels.
 *
 * @package WordPress
 * @subpackage Administration
 */

// don't load directly
if ( !defined('ABSPATH') )
	die('-1');
?>
<table class="widefat <?php echo $post_type_object->hierarchical ? 'page' : 'post'; ?> fixed" cellspacing="0">
	<thead>
	<tr>
<?php print_column_headers( $current_screen ); ?>
	</tr>
	</thead>

	<tfoot>
	<tr>
<?php print_column_headers($current_screen, false); ?>
	</tr>
	</tfoot>

	<tbody>
<?php
if ( $post_type_object->hierarchical )
	page_rows($posts, $pagenum, $per_page);
else
	post_rows();
?>
	</tbody>
</table>

The same content is in 12 releases, WordPress 3.0-beta1 to 3.0.6. See them all, or every version of this file.