New answers tagged

0

I solved the problem by installing php-ssh2, which removes libssh2-php on the install. $ sudo apt-get install php-ssh2 I also had to change permissions on the wp-content folder to 775, but it worked leaving the wp-content/plugins at 755. $ chmod 775 wp-content


2

Sites on previous minor versions (the middle dot in the version number) will generally automatically upgrade to new patch versions (the last dot) if there's a security release. For example, a site on 4.4.3 might automatically upgrade to 4.4.4 if a security patch release was issued for 4.5.2 to 4.5.3. This means that security patches can be automatically ...


1

I don't know what big agencies do, but I can tell you one developer tool that can be used to automate this kind of testing: Codeception. What this sort of testing is technically called is acceptance testing. Codeception allows you to write automated acceptance tests. It even has an extension that will take screenshots and automatically compare them for you. ...


0

WooCommerce 2.6 brings major change in shipping module. Shipping zones are introduced in WooCommerce 2.6 to bring more flexibility while configuring your shipping methods. Legacy shipping methods (Flat Rate, International Flat Rate, Local Pickup and Delivery, and Free Shipping) are deprecated. So, it’s highly recommended to disable these and ...


1

There are scripts available which can do the job for you. As per my understanding, you will have to host your plugin updates on a remote location so that the update checker can access that and do the necessary job. You can take a look at this script which seems to be very useful as per the comments. You can also find examples on that page which you can ...


4

You're damned if you do, and you're damned if you don't. But it's typically better to "do". I have been working in WordPress support and development for a number of years now - and I can certainly say it's much better to keep everything up to date. Wait a little bit (2 weeks or so) after major updates before making the change to allow time for maintenance ...


2

You can see timeline of WordPress releases and links to summaries of changes at WordPress versions page in Codex. 4.5 release came out only about four months after 4.4. It didn't contain any major changes to dashboard. As far as I remember the last release with major dashboard overhaul was 3.8 back in 2013. It's infrequent occurrence due to amount of work ...


3

Yes, you should apply this update. To elaborate: WordPress releases major core updates (ie. 4.4.x to 4.5.x) regularly, about 2-3 times each year. In between these they will also release minor updates (ie. 4.4.1 to 4.4.2). The major updates typically introduce new functionality, enhance current functionality, and address non-critical bugs. The minor updates ...


0

In wordpress a translation is part of the code. If you change translations you should track the .po files in "git" as if it was any other kind of code. An alternative option is to override the textdomain used for translation and use another one that uses another .mo file located at some "safe" location. But this is just a band-aid over the "translation is ...


1

Ok, after having digged into WP source for a couple of hours, found a workaround. Simply tell wordpress to NOT remove old files. Now files are 100% overwritten and cached files maintained. Code is really simple add_filter('upgrader_package_options', 'avoid_deletion', 999); function avoid_deletion($options) { if($options['hook_extra']['plugin'] == 'my-...


2

Not a direct answer, but probably has to be said - this is one problem you should avoid solving unless you are talking about a local development in which case you can just set permissions to 777. The reason is that if the webserver can overwrite your code, then any malicious code running on it will be able to do that as well. The risk is just so much bigger ...


1

Not possible unless you plan in advance in your plugin for such a possibility. And even if it was somehow possible you are still not likely to have any user read the message and actually understand it. A more realistic approach is to do a two steps upgrade, in the first vesion of your plugin to maintain appropriate backward compatibility and only later you ...


0

You can access the full list of available plugin updates with get_plugin_updates() function. You just need to verify if your plugin is there, then check with the versions, and the best way to output a warning in the admin endpoint is with admin_notices hook Specify your plugin name in the $requested_name variable (line:4) add_action('admin_init', function(...



Top 50 recent answers are included