How to keep WP from creating a “single-post” page and let the user input the link of the post in the dashboard?

I have this very specific questions. On my homepage I decided to show excerpts of the latest news and events with a "while" loop. The issue is that I want the admin to define what the permalink will be of said post, and not have a /event/lorem-ipsum page for each event. The idea is to link those excerpts to Instagram posts, Facebook posts, or whatever…

My custom_post_type function is:

register_post_type('event',      array(         'rewrite' => array('slug' => 'events'),         'labels' => array(             'name' => 'Events',             'singular_name' => 'Event',             'adding_new_item' => 'Add event',             'edit_item' => 'Edit event'         ),         'menu-icon' => 'dashicons-calendar-alt',         'public' => true,         'has_archive' => true,         'supports' => array(             'title', 'thumbnail', 'editor',          )     ) ); 

Recovering InnoDB database from backed up “data” folder in XAMP in Windows 10

I copied the data directory from mysql folder and uninstalled the XAMPP as the MariaDB was not starting. I installed XAMPP same version and backed up the data folder into mysql data directory. At first only copied the required database folder named production inside the mysql data directory. PhpMyAdmin showed the tables correctly though no record/row was there and it showed "Table doesn’t exist in engine". Then I copied all the contents from the DATA folder to the mysql data folder and now it does not start. Now the problem is MariaDB is not starting. I tried setting the innodb_force_recovery but it failed to start the mysql.

The error log is given below:

2021-06-11  0:08:23 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2021-06-11  0:08:23 0 [Note] InnoDB: Uses event mutexes 2021-06-11  0:08:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2021-06-11  0:08:23 0 [Note] InnoDB: Number of pools: 1 2021-06-11  0:08:23 0 [Note] InnoDB: Using SSE2 crc32 instructions 2021-06-11  0:08:23 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M 2021-06-11  0:08:23 0 [Note] InnoDB: Completed initialization of buffer pool 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\applied.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`applied``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`applied` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\data.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`data``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`data` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\data_employer.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`data_employer``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`data_employer` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\education.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`education``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`education` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\education_list.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`education_list``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`education_list` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\industry.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`industry``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`industry` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\jobs.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`jobs``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`jobs` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login_admini.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login_admini``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login_admini` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\login_employer.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`login_employer``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`login_employer` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\resume.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`resume``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`resume` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\jobs\selected.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``jobs`.`selected``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `jobs`.`selected` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\entries.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`entries``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`entries` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\geoname.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`geoname``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`geoname` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\geonamebackup.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`geonamebackup``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`geonamebackup` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\pincodes.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`pincodes``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`pincodes` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\specifier.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`specifier``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`specifier` because it could not be opened. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 3 in a file operation. 2021-06-11  0:08:23 0 [ERROR] InnoDB: The error means the system cannot find the path specified. 2021-06-11  0:08:23 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them. 2021-06-11  0:08:23 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\projects\users.ibd' OS error: 203 2021-06-11  0:08:23 0 [ERROR] InnoDB: Operating system error number 203 in a file operation. 2021-06-11  0:08:23 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ 2021-06-11  0:08:23 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``projects`.`users``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue. 2021-06-11  0:08:23 0 [Warning] InnoDB: Ignoring tablespace for `projects`.`users` because it could not be opened. 2021-06-11  0:08:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2021-06-11  0:08:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2021-06-11  0:08:23 0 [Note] InnoDB: Setting file 'D:\Program Files\XAMP\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2021-06-11  0:08:23 0 [Note] InnoDB: File 'D:\Program Files\XAMP\mysql\data\ibtmp1' size is now 12 MB. 2021-06-11  0:08:23 0 [Note] InnoDB: Waiting for purge to start 2021-06-11  0:08:23 0 [Note] InnoDB: 10.4.19 started; log sequence number 1515509790; transaction id 611499 2021-06-11  0:08:23 0 [Note] InnoDB: Loading buffer pool(s) from D:\Program Files\XAMP\mysql\data\ib_buffer_pool 2021-06-11  0:08:23 0 [Note] Plugin 'FEEDBACK' is disabled. 2021-06-11  0:08:23 0 [Note] Server socket created on IP: '::'. 

trying to hide a “0” value from a HTML display

enter image description hereIs there any way to hide an HTML field based on the displayed value of "0" I have an ecomm site that displays Quantity available with a numeric value. I only want to display the number if it is above "0" The values are populated from data base upload to the site. The "0" value is NOT an input field. so most codes I see have the solution with some sort of input condition code.

My site displays this: Call for Availability.0 If item has QTY above "0" it displays this: Qty On Hand: 1708 I need to remove the "0" and only display Call for Availability.

I have researched similar request on this forum and found all have answers using an input field. The problem is the "0" is not an input. It is an code generated inventory amount.

I have tried CSS to hide the value, but that hides ALL the values including above "0".

I can insert any form of code needed. Java, PHP, json, etc…

Here is a sample of actual code I have:

<div id="availabilityInfo" class="availabilityInfo">  <span class="availability-header">[product_Header-availability]</span> <span id="availability" class="product_availability availability-item">[availability]</span>  <span style="display: inline;" id="product_inventory">[stock] <span class="freeshipping availability-item"><!--[freeshipping]--></span>  </span></div> 

The [STOCK] tag is what brings in the qty value of "0"

Can’t remove “synchronizing/suspect” database after removed from availability group Sql Server 2019 Enterprise

I’ve removed a db from a synchronous availability group.The db shows "synchronizing/suspect" as it should. I’m trying to remove this database cannot. I have tried:

DROP DATABASE [db1]; 

but get "Cannot drop database "db1" because it is currently in use.". even though their are no sessions using this database.

ALTER DATABASE [db1] SET OFFLINE; 

but get "ALTER DATABASE failed because a lock could not be placed on database ‘db1’. Try again later."

ALTER DATABASE [db1] SET SINGLE_USER WITH ROLLBACK IMMEDIATE 

but get "ALTER DATABASE failed because a lock could not be placed on database ‘db1’. Try again later."

ALTER DATABASE [db1] SET EMERGENCY; 

ALTER DATABASE failed because a lock could not be placed on database ‘db1’. Try again later.

This is a 24/7 production db and restarting is not a good option.

Any advice?

Linked server only works if I am on the machine itself. I can’t use it from my local computer. what is missing?

I have a few queries that I use to monitor log shipping. Sometimes I want to run those queries on a different server. I usually do that through a linked server.

I have a server called SQLDEV4-TS that has a linked server to MY_SERVER\DEVELOPMENT

ON SQLDEV4-TS I have setup Kerberos as per the picture below:

enter image description here

I have this query below that I use to test the connectivity to the linked server.

DECLARE @server_name sysname = @@servername SELECT @server_name=N'MY_SERVER\DEVELOPMENT'   DECLARE @sql NVARCHAR(MAX) = N'SELECT * FROM OPENQUERY([' + @server_name +'],        ''SELECT ''''Radhe'''' AS Radhe'');'  BEGIN TRY     EXEC sp_testlinkedserver @server_name      EXEC sp_executesql @sql=@sql  END TRY BEGIN CATCH     SELECT [error_number]=ERROR_NUMBER(), [error_message]=ERROR_MESSAGE(); END CATCH;  PRINT 'We got past the Catch block!'; 

When I am on the server itself – SQLDEV4-TS – and I run the above script I get the following result:

enter image description here

All good – it works as expected – no problem.

However, when I connect to SQLDEV4-TS from my local machine, and run the script (on my machine) I get the following result:

Login failed for user ‘NT AUTHORITY\ANONYMOUS LOGON’.

enter image description here

What is missing in this linked server setting, that I have to be on the machine itself for it to work?

How can I find and clear belazyelephant virus from my website?

I want to publish some ads on Google but they say that I have got a virus on my website and the links are these: https://belazyelephant.com/?p=hezdsyjyhe5gi3bpgmztini&sub1=Dru&sub2=debt.v1, https://belazyelephant.com/?p=hezdsyjyhe5gi3bpgmztini&sub1=Frost&sub2=debt. https://belazyelephant.com/w_24.js I think they injected it over a plugin called Popup Builder because last year, my website got infected again because of this dumb plugin. How can I find and remove this virus? I searched the virus URL in my DB but I couldn’t find it, I also removed the plugin but no luck…

Bulk-create posts from SQL database

I’m new in this forum and fairly new to WordPress as a whole, so I hope I will abide by all written and unwritten rules when posting this.

I have an SQL database with around 4,000 posts from an old website. Each post has an ID, date, title, body, keywords, and category column (and some others that are irrelevant). These columns are, as far as I’ve seen it, not named in a default manner but are, at least in part, specific to the website’s topic.

I want to create a completely new website with new hosting, new theme, new design etc.

Is there a possibility to auto-populate that new website with all the 4,000 posts from my SQL database through wordpress? So the ideal result would be to build my new website, then WordPress-SQL-magic happens, and then when the website goes live it already has 4,000 posts that are accessible through the new menu, neatly categorized based on the categories in the SQL database and also displaying the date on which it was originally published. The categories in the SQL database are mere numbers, so they would have to be linked to the actual worded menu categories.

Maybe I’m missing something very basic here, because I do know that you can export all posts as an SQL file, but I have never bulk-uploaded anything to WordPress, especially not from another site that has a different menu structure than the new one.

Thanks a lot in advance for any help you might be able to provide!

Earn free Bitcoin from playing games. Finish task be offered mining reward.

Why are you selling this site?
In need of money

How is it monetized?
It is monetized using affiliate program , pop ads , pop cash ,CPI reward program , subscription premium membership, deposit

Does this site come with any social media accounts?
No

How much time does this site take to run?

1-2 hours a day
What challenges are there with running this site?
None

Situation when the same page has different Statuses: Canonical and Canonicalised when crawled from the different countries

I need to show different content to the visitors from USA. I am using the following code in .htaccess to capture CloudFlare Geolocation data and append "/?country=US" to my URL once visitor came from USA:

SetEnvIf CF-IPCountry "(.*)$ " Country=$ 1
RewriteCond %{ENV:Country} ^(US)$
RewriteRule ^(.*)$ $ 1?country=%{ENV:Country} [R,L,QSA]

So basically all Americans seeing https://example.com/?country=US while rest of the world seeing: https://example.com/

Everything works as planned, the only concern I have …

US based bots (Google Search Console) now seeing this page as following:

  • https://example.com/ – StatusCode: 302, Status: Found, Indexability: Non-Indexable, Indexability Status: Redirected
  • https://example.com/?country=US – StatusCode: 200, Status: OK, Indexability: Non-Indexable, Indexability Status: Canonicalised

For the rest of the world:

  • https://example.com/ – StatusCode: 200, Status: OK, Indexability: Indexable, Indexability Status: Canonical

As you may see from above "https://example.com/" now has TWO different Responses when crawled in the US and outside of US.

NOW THE QUESTION …

  • Do you see any danger from SEO perspective? Is there any way to avoid this situation when the same page (https://example.com/) has TWO different Statuses: Canonical and Canonicalised when crawled from the different countries?
  • Will you recommend a different approach to this problem, maybe by avoiding the use of a querystring?

Thanks a lot! OZ