If you have a WordPress install with many different plugins, you may experience that some jQuery functionality will be lost in the admin panel (i.e. you won’t be able to move the content blocks around your Dashboard).
When you open the console (press F12 in most browsers), you will see several errors that will read:
Uncaught ReferenceError: jQuery is not defined
You may also see something like:
Failed to load resource: the server responded with a status of 403 - https://www.yourdomain.com/wp-admin/load-scripts.php?c=1&load%5B%5D=sa…ry-ui-slider,jquery-touc&load%5B%5D=h-punch,iris,wp-color-picker&ver=4.3.1
Here is how you fix both of these with two easy steps…
Imagine that you made some intensive changes to your CSS or JS file, tested it in your browser by hard-refreshing the pages (because you know that your CSS and JS are being cached by the browser), everything looked good, so you uploaded it to your production server. Now, how many end-users know how to hard-refresh the page if something doesn’t look right? You know it – very few. In this short manual I will explain one trick that will save you time trying to explain to your customer that he/she has to “hard-refresh the page to update cached CSS file. Please press CTRL+F5 :)”.
Please note that your CSS/JS files will still be cached (your browser will not request them every time you load the site), however if your local cached version will not match the one currently on the server, it will request it from the server and will replace the local cached version with the most recent one.
The script will then geocode each address (get latitude and longitude) and place a marker on the map. By clicking on the marker you will get an “info-window” (in our example – with project name and the amount of photos for each project). We specify the image for the marker as well.
If you have a blog or news section on your custom website, which you want to separate by pages, use the steps below to implement a paging module. First, I usually create a file called
pager.php in your
/includes/ folder. The content of that file is below:
Most of the time we have a website or a back-end solution, written in PHP, where we use check-boxes as “flags” (to activate a user or a product for example – 1=active, 0=inactive).
Below is the example that I will base on our fictional “products” page in the back-end solution, where we specify if a given product is active or inactive (in order to show or hide it on the front of the site).