css – node.js and webpack throws error when trying to setup node to watch theme folder for saved changes

Ok, so I have been getting this error thrown out when I try to run my npm run devFast command, so it can watch my theme for saved changes.

I think it has to do something with my file structure, some how its not reading the wordpress css file that I have copied over to the css folder so that the scripts.js file can import the css file into scripts.js to refresh my browser automatically when I make changes to my files.

I am not sure how to resolve this if its not my file structure at fault. I have researched exhaustively online, but I have not found anything.

Error in question:

PS C:wamp64wwwworkshop_01wp-contentthemesworkshop_01> npm run devFast

> workshop_01@1.0.0 devFast C:wamp64wwwworkshop_01wp-contentthemesworkshop_01
> webpack serve

i 「wds」: Project is running at http://localhost:3000/
i 「wds」: webpack output is served from http://localhost:3000/
i 「wds」: Content not from webpack is served from C:wamp64wwwworkshop_01wp-contentthemesworkshop_01
× 「wdm」: asset bundled.js 405 KiB (emitted) (name: scripts) 1 related asset
runtime modules 25.9 KiB 13 modules
modules by path ./node_modules/ 345 KiB
  modules by path ./node_modules/webpack-dev-server/client/ 20.9 KiB 10 modules
  modules by path ./node_modules/webpack/hot/ 4.46 KiB 5 modules
  modules by path ./node_modules/html-entities/lib/*.js 61 KiB 5 modules
  modules by path ./node_modules/url/ 37.4 KiB 3 modules
  modules by path ./node_modules/querystring/*.js 4.51 KiB
    ./node_modules/querystring/index.js 127 bytes (built) (code generated)
    ./node_modules/querystring/decode.js 2.34 KiB (built) (code generated)
    ./node_modules/querystring/encode.js 2.04 KiB (built) (code generated)
modules by path ./css/*.css 1.51 KiB
  ./css/style.css 1.48 KiB (built) (code generated)
  ./node_modules/css-loader/dist/cjs.js?url=false!./node_modules/postcss-loader/dist/cjs.js??ruleSet(1).rules(0).use(2)!./css/style.css 39 bytes (built) (code generated) (1 error)        
./js/scripts.js 148 bytes (built) (code generated)

ERROR in ./css/style.css (./node_modules/css-loader/dist/cjs.js?url=false!./node_modules/postcss-loader/dist/cjs.js??ruleSet(1).rules(0).use(2)!./css/style.css)
Module build failed (from ./node_modules/postcss-loader/dist/cjs.js):
ValidationError: Invalid options object. PostCSS Loader has been initialized using an options object that does not match the API schema.
 - options has an unknown property 'plugins'. These properties are valid:
   object { postcssOptions?, execute?, sourceMap?, implementation? }
    at validate (C:wamp64wwwworkshop_01wp-contentthemesworkshop_01node_moduleswebpacknode_modulesschema-utilsdistvalidate.js:104:11)
    at Object.getOptions (C:wamp64wwwworkshop_01wp-contentthemesworkshop_01node_moduleswebpacklibNormalModule.js:529:19)
    at Object.loader (C:wamp64wwwworkshop_01wp-contentthemesworkshop_01node_modulespostcss-loaderdistindex.js:40:24)
 @ ./css/style.css 2:12-168 9:17-24 13:7-21 45:20-34 49:6-59:7 50:38-52 56:26-40 58:21-28 68:15-29 47:4-60:5
 @ ./js/scripts.js 1:0-26

webpack 5.38.1 compiled with 1 error in 4433 ms
i 「wdm」: Failed to compile.

Here are the additional outputs for my package.json, webpack.config.js, scripts.js, and file structure:

package.json

{
  "name": "workshop_01",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "dev": "npm-run-all -p devFast buildWatch",
    "devFast": "webpack serve",
    "buildWatch": "webpack --watch",
    "build": "webpack",
    "test": "echo "Error: no test specified" && exit 1"
  },
  "keywords": (),
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@babel/core": "^7.14.5",
    "@babel/preset-env": "^7.14.5",
    "@babel/preset-react": "^7.14.5",
    "@glidejs/glide": "^3.4.1",
    "autoprefixer": "^10.2.6",
    "axios": "^0.21.1",
    "babel-loader": "^8.2.2",
    "clean-webpack-plugin": "^4.0.0-alpha.0",
    "css-loader": "^5.2.6",
    "cssnano": "^5.0.6",
    "fs-extra": "^10.0.0",
    "jquery": "^3.6.0",
    "mini-css-extract-plugin": "^1.6.0",
    "normalize.css": "^8.0.1",
    "npm-run-all": "^4.1.5",
    "postcss-color-function": "^4.1.0",
    "postcss-hexrgba": "^2.0.1",
    "postcss-import": "^14.0.2",
    "postcss-loader": "^6.1.0",
    "postcss-mixins": "^8.1.0",
    "postcss-nested": "^5.0.5",
    "postcss-simple-vars": "^6.0.3",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "style-loader": "^2.0.0",
    "webpack": "^5.38.1",
    "webpack-cli": "^4.7.2",
    "webpack-dev-server": "^3.11.2",
    "webpack-manifest-plugin": "^3.1.1"
  }
}

webpack.config.js

/*
  SUPER IMPORTANT: This config assumes your theme folder is named
  exactly 'fictional-university-theme' and that you have a folder
  inside it named 'bundled-assets' - If you'd like to adapt this
  config to work with your own custom folder structure and names
  be sure to adjust the publicPath value on line #116. You do NOT
  need to update any of the other publicPath settings in this file,
  only the one on line #116.
*/

const currentTask = process.env.npm_lifecycle_event
const path = require("path")
const MiniCssExtractPlugin = require("mini-css-extract-plugin")
const { CleanWebpackPlugin } = require("clean-webpack-plugin")
const ManifestPlugin = require("webpack-manifest-plugin")
const fse = require("fs-extra")

const postCSSPlugins = (require("postcss-import"), require("postcss-mixins"), require("postcss-simple-vars"), require("postcss-nested"), require("postcss-hexrgba"), require("postcss-color-function"), require("autoprefixer"))

class RunAfterCompile {
  apply(compiler) {
    compiler.hooks.done.tap("Update functions.php", function () {
      // update functions php here
      const manifest = fse.readJsonSync("./bundled-assets/manifest.json")

      fse.readFile("./functions.php", "utf8", function (err, data) {
        if (err) {
          console.log(err)
        }

        const scriptsRegEx = new RegExp("/bundled-assets/scripts.+?'", "g")
        const vendorsRegEx = new RegExp("/bundled-assets/vendors.+?'", "g")
        const cssRegEx = new RegExp("/bundled-assets/styles.+?'", "g")

        let result = data.replace(scriptsRegEx, `/bundled-assets/${manifest("scripts.js")}'`).replace(vendorsRegEx, `/bundled-assets/${manifest("vendors~scripts.js")}'`).replace(cssRegEx, `/bundled-assets/${manifest("scripts.css")}'`)

        fse.writeFile("./functions.php", result, "utf8", function (err) {
          if (err) return console.log(err)
        })
      })
    })
  }
}

let cssConfig = {
  test: /.css$/i,
  use: ("css-loader?url=false", { loader: "postcss-loader", options: { plugins: postCSSPlugins } })
}

let config = {
  entry: {
    scripts: "./js/scripts.js"
  },
  plugins: (),
  module: {
    rules: (
      cssConfig,
      {
        test: /.js$/,
        exclude: /(node_modules)/,
        use: {
          loader: "babel-loader",
          options: {
            presets: ("@babel/preset-react", ("@babel/preset-env", { targets: { node: "12" } }))
          }
        }
      }
    )
  }
}

if (currentTask == "devFast") {
  config.devtool = "source-map"
  cssConfig.use.unshift("style-loader")
  config.output = {
    filename: "bundled.js",
    publicPath: "http://localhost:3000/"
  }
  config.devServer = {
    before: function (app, server) {
      /*
        If you want the browser to also perform a traditional refresh
        after a save to a JS file you can modify the line directly
        below this comment to look like this instead. I'm using this approach
        instead of just disabling Hot Module Replacement beacuse this way our
        CSS updates can still happen immediately without a page refresh.
        If you're using a slower computer and the new bundle is not ready
        by the time this is reloading the browser you can always just set the 
        "hot" property a few lines below this to false instead of true. That
        will work on all computers and the only trade off is the browser will
        perform a traditional refresh even for CSS changes as well.
        */

      // server._watch(("./**/*.php", "./**/*.js"))
      server._watch(("./**/*.php", "!./functions.php"))
    },
    public: "http://localhost:3000",
    publicPath: "http://localhost:3000/",
    disableHostCheck: true,
    contentBase: path.join(__dirname),
    contentBasePublicPath: "http://localhost:3000/",
    hot: true,
    port: 3000,
    headers: {
      "Access-Control-Allow-Origin": "*"
    }
  }
  config.mode = "development"
}

if (currentTask == "build" || currentTask == "buildWatch") {
  cssConfig.use.unshift(MiniCssExtractPlugin.loader)
  postCSSPlugins.push(require("cssnano"))
  config.output = {
    publicPath: "/wp-content/themes/workshop_01/bundled-assets/",
    filename: "(name).(chunkhash).js",
    chunkFilename: "(name).(chunkhash).js",
    path: path.resolve(__dirname, "bundled-assets")
  }
  config.mode = "production"
  config.optimization = {
    splitChunks: { chunks: "all" }
  }
  config.plugins.push(new CleanWebpackPlugin(), new MiniCssExtractPlugin({ filename: "styles.(chunkhash).css" }), new ManifestPlugin({ publicPath: "" }), new RunAfterCompile())
}

module.exports = config

scripts.js

import "../css/style.css"

// Allow new JS and CSS to load in browser without a traditional page refresh
if (module.hot) {
  module.hot.accept()
}

enter image description here

Can anyone see any issues?
I have the latest package versions too, so all I can think of is my folder directories are the issue.

Please help me.

sharepoint online – How can I create different view based on Different Folder

Create three views like below:

Folder 1 View

Filter “Name” equal to “Folder1”

Folder 2 View

Filter “Name” equal to “Folder2”

Folder 3 View

Filter “Name” equal to “Folder3”

Filter condition should be like below for all the three views:

enter image description here

We can see that three views are created and based on the view selection folder is getting displayed in the content area:

enter image description here

Note:

  • The above UI based view creation can also be done thru the coding using camel query builder.

email – Export a single mail folder to an archive file in Outlook 2016 and “mount” that back later?

In Outlook 2016, I have a folder labeled “2020” with my mails from that year, and want to export it to a single file. I then wish to move that file around (to an external archive HDD or wherever). If, eventually, I ever need one of those mails, I would like to open the file with Outlook, and find that single file – I most definitely do not, in that case, wish to import the whole archive back into my online account.

In Outlook for Windows, one can create a .pst file which acts like a local account – you can “mount” it, move mails into and out of it, but also close it and then work with the .pst file like with anything else.

In Outlook 2016 for Mac, there is an Export and Import functionality which works on .olm files. But it seems very limited: during exporting, you can pick categories of mails, but not, say, a single mail folder. During importing, the .olm file is not “mounted”, but simply imported, adding the content of the .olm to your regular mail account.

Is there a way to achieve what I need in Outlook 2016, or is the functionality simply not there? Do you know some kind of workaround? If it matters, the account is provided by an Exchange server.

mariadb – 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: '.jobsapplied.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: '.jobsdata.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: '.jobsdata_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: '.jobseducation.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: '.jobseducation_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: '.jobsindustry.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: '.jobsjobs.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: '.jobslogin.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: '.jobslogin_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: '.jobslogin_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: '.jobsresume.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: '.jobsselected.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: '.projectsentries.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: '.projectsgeoname.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: '.projectsgeonamebackup.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: '.projectspincodes.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: '.projectsspecifier.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: '.projectsusers.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 FilesXAMPmysqldataibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2021-06-11  0:08:23 0 (Note) InnoDB: File 'D:Program FilesXAMPmysqldataibtmp1' 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 FilesXAMPmysqldataib_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: '::'.

MacOS: Specify a folder as Windows Server / System shared

I’m an irregular Apple user (except for my iPhone) since I only work with Apple PCs & Laptops at work. So here is the issue. When a User with an iMac 2017 running Mac OS Mojave (forgot the exact number) is working on the network share, he/she can use special characters that either don’t exist under Windows or that are not allowed under Windows. For example: *, ?, “, <, >, |
When I tried with an old MacBook Air 2010 (late) running High Sierra (10.13.6) the only character it didn’t like was the :. Plus the characters that I have never seen or used on a Windows PC are the < & > with an extra line underneath.

So since Mac OS supports such characters in the folder path, it would be good to have an option to define a network shared folder from a Windows device as Windows or Microsoft hosted which would disallow any special characters that are either unknown to Windows or not allowed in Windows. I don’t know if an option like this exists in MacOS and I was unable to find something myself except for instructions on how to add a Windows share or network share on the Apple Devices.

To give some more details the share is hosted on a virtual Windows Server 2019 running SMB.

Perhaps there is a way to mark certain special characters as illegal file name characters, too. That would also be an option if it’s available.

Maybe someone here know something or got an idea for this. This is also only a preventive question to avoid issues between both systems.

macos – Applescript to copy/sync dropped folders to a destination folder

Hello using Applescript on Macos I want to copy/sync dropped folders (onto the applescript app) to a predefined destination folder.

I have this script I’ve written, but it’s not working:

on open theFiles
    tell application "Finder"
        set destFolder to "/Users/Username/Desktop/My Files"
        do shell script "/usr/bin/rsync -a  'theFiles' 'destFolder' "
    end tell
end open

Can anyone please help fix my script to work? Thanks much!

Compress a folder to a .tar file in Ubuntu 20.04 via GUI

I expect Ubuntu progress in its newer distributions than going backward.

In the past, I had such an option. How can I do that with this distribution?

I am not after a command line solution. I want my options on GUI back.

compress ubuntu 20.04

Custom folder access per role

I need to restrict access of custom folder for some user role.
I have flip-page book in one folder with index.html file and other files in subfolders.
So I need to restrict access of that folder to anonymous users and grant access to certain Drupal roles.

Cannot create folder or create document or upload document im my document library

I cannot create any folder or document and upload document in my document library by any user, permission is Full and everything is ok , when drag and drop error change to “Save Conflict Your changes conflict with those made concurrently by another user. If you want your changes to be applied, click Back in your Web browser, refresh the page, and resubmit your changes.”
-SharePoint 2016
-the problem occurs to specific library
-Edit folder and document is OK

KIO Client says folder doesn’t exist when trying to link to /

I have tried two different widgets in KDE Plasma that provide links to common folders. All of the links work except to /. When I click on the link to /, it says the folder does not exist. Any idea what is causing this or how to fix it?

enter image description here

enter image description here

enter image description here