How safe is it to delete old posts edits to save database space?
The revisional feature of WordPress is only for users. That means, that if you don’t need them old revisions, you can safely delete them. The system actually doesn’t care.
The revisional feature of WordPress is only for users. That means, that if you don’t need them old revisions, you can safely delete them. The system actually doesn’t care.
It depends on your user account structure. The superadmin of the MU can always edit anything and you cannot lock that one out for obvious reasons, but you can remove all other users from that 1 website you want to lock down. Go to Network Admin > Sites > Edit (link) and then in the … Read more
While you might not be writing a plugin specifically, this resource will still be pertinent: http://codex.wordpress.org/Writing_a_Plugin#Plugin_Development_Suggestions From the codex Use the existing database tables instead of creating new custom tables if possible. Most use-cases can be accomplished with custom post types and meta data, custom taxonomy and/or one of the other standard tables and using … Read more
No. it does not . And your post will not be deleted Updates from the wordpress interface regard only the core FILES. not the DB. However, sometimes, between versions, a db upgrade can be made which is mainly reordering or fixing DB. Not deleting entries. It is at any rate recommended to do a db … Read more
This is essentially a SQL question. The only possible WordPress related component would be if you were asking about database structure, which is in the Codex. Or you could just look at the database itself. The post ID is incremented and never duplicated. The highest IDs are the last added. The query is simple. SELECT … Read more
As @s_ha_dum mentioned in the comments, building an API or some sort of XML or JSON feed (or leveraging one that’s already there, or installing a plugin on whatever system that is, etc) is really your only way of getting at that data remotely. Once you get that going, you can use wp_remote_get to query … Read more
Multiple installs can share a single database, as long as each install has a unique table prefix defined in wp-config.php before going through the install process: /** * WordPress Database Table prefix. * * You can have multiple installations in one database if you give each a unique * prefix. Only numbers, letters, and underscores … Read more
WordPress is an ecosystem of its own, and it’s pretty fat in terms of memory use and existing APIs and structures. Integrating this huge behemoth with a lean back-end that you have already built on your own won’t make much sense unless you specifically want to use WP’s back-end functionality instead of yours. WordPress themes … Read more
I’m pretty sure that first SQL query isn’t correct SQL (insert has different syntax) 😉 It should be: INSERT INTO {$wpdb->prefix}awpcp_adphotos (ad_id, image_name, disabled, isprimary) VALUES (%d, %s, %d,%d) In second example, I’m almost sure that ad_id is not string, and image_name is not a number. Of cours I’m only guessing, because I haven’t seen … Read more
Since: upgrade endpoint in question doesn’t seem to be behind login wall no user action is required other than visiting it I would imagine requesting the suggested URL with some CLI tool for HTTP requests (curl and wget are commonly available) should accomplish upgrade.