Migrating WPMS from apache to IIS7 causes Database Error
I worked through this problem myself with the help of a forum mod on wordpress.org. You can see the full forum post here.
I worked through this problem myself with the help of a forum mod on wordpress.org. You can see the full forum post here.
Register new user and add custom data row value for it
For DB upgrades wordpress compares the db version number it hs in the code to the one in the DB. It makes no difference how the new code got there as long as it is the correct one. Which begs to caution that if you go that way you should put wordpress into maintenance mode … Read more
Definitely backup your database FIRST before trying this out. I just tested changing the option_name of a set of customizer changes to match a different theme, and it appears we can make the customizer changes switch to another theme simply by changing the option_name to match our new theme, instead of copying the option_value serialized … Read more
I will suggest WordPress Duplicator, It is best tool for copying your site to any other host/localhost, and its free, I have used it many times and it works every-time with different server settings. Please note that I haven’t affiliated with it in any way.
Yes the issue is due to the auto increment setting. All WordPress DB specifics can be found here, which includes details on which ones use auto increment: https://codex.wordpress.org/Database_Description This isn’t going to be an easy task, but here’s some sites to help you: https://www.photographerstechsupport.com/tutorials/fixing-wordpress-indexes-foreign-keys-and-auto_increment-fields/ This one is specific to wp_options: https://guides.wp-bullet.com/fixing-wp_options-table-missing-unique-column-primary-key/ Specifically the auto increment: … Read more
Yes you can. Straight from the codex The $wpdb object is not limited to the default tables created by WordPress; it can be used to read data from any table in the WordPress database (such as custom plugin tables). For example to SELECT some information from a custom table called “mytable”, you can do the … Read more
In short, no. But it’s not particularly complicated. Just add a new version_compare block each time you revise the database: $db_version = get_option( ‘my_plugin_version’ ); if ( version_compare( $db_version, ‘1.1’, ‘<‘ ) ) { // Initial update code added in 1.1 } if ( version_compare( $db_version, ‘1.2’, ‘<‘ ) ) { // Additional update code … Read more
Yes, multiple installations can share a single database. When you edit the wp-config.php file for each installation, you must give each install a unique table prefix. The process is also explained in Installing Multiple Blogs: Single Database in Codex.
It sounds like you do want a custom post type, you just want to set the public argument to false. The register_post_type() has lots of arguments that will let you do everything you probably want. Along with public, you’ll probably set has_archive to false. Setting show_ui to true will allow you to manage the posts … Read more