PHP’s opcache module causes this kind of behaviour. Disable this module by editing the file at /etc/php5/mods-available/opcache.ini and placing a semicolon like this. ;zend_extension=opcache.so And restart PHP5-FPM/web server service. If you are not comfortable editing these files add these lines to the top of your child theme’s functions.php file. if ( is_admin() ): ini_set( “opcache.enable”, … Read more
Can you provide the request header you get in your browser? It should follow this form: File: load-scripts.php 56: header(“Etag: $wp_version”); 57: header(‘Content-Type: application/javascript; charset=UTF-8’); 58: header(‘Expires: ‘ . gmdate( “D, d M Y H:i:s”, time() + $expires_offset ) . ‘ GMT’); 59: header(“Cache-Control: public, max-age=$expires_offset”); The request header is OK. I can confirm I … Read more
It is quite simple. All you have to do is add some code in a Custom Functions plugin. Lets say you want to block the “Hello Dolly” plugin (comes prepacked with WordPress) from updating. In your “My Functions Plugin”, mycustomfunctions.php (you can use any name really) you place the following: /* Disable a plugin from … Read more
This is a very simple query of the $wpdb->posts table. $last_update = $wpdb->get_var(” SELECT post_date FROM {$wpdb->posts} WHERE post_type IN(‘post’,’page’) AND post_status=”publish” ORDER BY post_date DESC LIMIT 1″ ); var_dump($last_update); You could do the same thing (similar) with … $args = array( ‘post_type’ => array(‘post’,’page’), ‘posts_per_page’ => 1, ); $last_updated = new WP_Query($args); var_dump($last_updated->post->post_date); … … Read more
You should integrate the ability to automatically update your plugin right through WordPress. There is a tutorial that gives you some help on this. Just my personal view, but: Please stay on the good side. Offer updates all the time, so your plugin stays up to date. I don´t want my site to get compromised … Read more
You are using a theme or plugin that uses a jQuery-dependent script with poor syntax. In this screenshot below of the browser console of the page you referenced, the expression should be … li > a[href*=’#’]. Note the missing quotes around the #. The bug didn’t show up until now because WordPress 4.5 updated the … Read more
This is a common issue and is documented on their official website for trouble shooting. The error may have been sent to you via an email with the subject line “Your Site is Experiencing a Technical Issue”, or it may have displayed in the Plugins page when you tried to update Jetpack. This happened because … Read more
Use Gulp + Gulp-Watch + BrowserSync. The goal is to run an extra process that monitors any changes in your files. When a change occurs the page is automatically reloaded including CSS injection / Scrolls / Browser clicks and all concurrently across multiple devices and browsers. Because it also generates an ip:port you can access … Read more
Like you said, downgrading would be a bad practice and is not at all recommended. Please make a backup of your database before continuing, just to play safe. It looks like you’ve only replaced wp-admin folder. WordPress updates are not limited to wp-admin folder. Try replacing wp-admin, wp-includes and all those files in the root … Read more
Yeahh! I finally found a solution! The trick was to set all files and folders their ownership and group to the apache user. Make sure you’ve an directory for temporary storage and you need to have the ../wp-content/upgrade/ directory as well. Than at your wp-config.php this is the only thing I’m not aware about of … Read more