So you are attempting to import SQL data from an ancient dump file and it fails with an error:
- You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ‘TYPE=MyISAM’
This is due to an obsolete syntax. Fixing it may be quite easy. Just open the file in an appropriate text editor, run search and replace, and save it:
- search for: TYPE=MyISAM
- replace with: ENGINE=MyISAM
The Shipping tab is supposed to be between the Tax and Payments tabs in:
- WooCommerce -> Settings -> Shipping
But it is not there?!
Check the parameters in
- WooCommerce -> General
You may have
- Shipping location(s)
- Disable shipping & shipping calculations
Just change it to something else and the missing tab will appear.
You can kill (end, terminate) a process (task, program, application) in Windows in a way that is similar to the way it is done in Linux.
Start cmd.exe, e.g.:
- Start -> Run -> cmd
In the terminal window that pops up at the prompt type:
Look for the PID of the process you want to terminate and use the following command to ask it nicely to quit:
- taskkill /PID <your PID here>
If you were lucky, the process will terminate. If it doesn’t, use force:
- taskkill /PID <your PID here> /F
You may experience a situation where FontAwesome icons used in styling of your page with Bootstrap CSS fail to show up. Everything seems fine, you may even have them working perfectly well in your development environment, but then stubbornly refusing to display in the production environment.
The first thing to do is to check if you are using the same protocol for requesting the CSS as you are using for serving your page. If you are serving the site over HTTPS but will attempt to request the CSS via HTTP, you will get the “Mixed Content” error and the CSS will be rejected by the browser.
In such cases a message can be seen in Chrome’s console similar to this one:
Mixed Content: The page at ‘https://www.example.com/’ was loaded over HTTPS, but requested an insecure stylesheet ‘http://maxcdn.bootstrapcdn.com/font-awesome/4.1.0/css/font-awesome.min.css’. This request has been blocked; the content must be served over HTTPS.
If you have forgotten your admin (or any other for that matter) password for Nextcloud, one way to fix it is like this.
Go to the root directory of your Nextcloud installation and type:
sudo -u www-data php ./occ user:resetpassword <username>
Substitute <username> with the username of the user you want to reset the password for.
NB! The actual username may be different from the display name, for the admin account too.
If you do not remember the actual username, you can look it up in the MySQL database. Using any suitable tool look into the oc_users table of the Nextcloud’s database. The field uid contains the actual username which you shall then use with the occ script to reset the password.
When using jQuery for parsing GPX data (which is an XML format) you may experience a weird problem of being unable to access extra elements (nodes) added by software used to process the data, such as QGIS.
A typical example would be having such data in the file and being able to read “extensions” as an abject, being able to access its contents as text, but mysteriously failing when attempting to read “ogr:id”, which was added by QGIS:
The good news is that it is not your fault. Actually the culprit is jQuery itself, which fails to operate correctly with the node identifiers from different namespace due to a bug.
The easiest solution is to escape the colon with two backslashes, like this:
var mytest = $(this).find(‘extensions’).find(“ogr\\:id”).text();
Read more about it here.
So you build OSRM map routing server and attempt to run it following the instructions on how to do it, only to see a message:
[error] Profile profiles/car.lua not found!
Well… You shouldn’t leave the “osrm-backend” directory. As the message says, OSRM was looking for a certain file in the “profiles” subdirectory of the location where you are now and it couldn’t find one. The chances are that after building and installing OSRM you went to another directory where your OSM map files are stored to test it.
The quickest solution is to simply create a symbolic link to the map file in the “osrm-backend” directory.