Tag Info

New answers tagged

0

Various possibilities. If fixing a bug, I'll sometimes actually make a patch and send it to the Plugin author. More than once they've added the patch and said thanks. Beyond that, if you really need to hack a plugin, you should also change the folder and header info so that the auto-update doesn't recognize it. Of course you'll not get new updates. ...


5

You don't, for the same reason you don't modify WordPress Core, you extend it or use hooks and filters to modify its behaviour. So when extending or changing plugins you have 2 options: Forking You've been creating forks of a plugin so far, but it's important to change the name when this happens so your new plugin isn't overwritten. You'll need to ...


1

There is no such child folder, but depending on the type of change, you can write a new plugin to override the code. If it's Revolution Slider, be sure you're reading all the documentation to be sure you actually need to be doing the edits in the first place. Most things you would "need" to change might actually be settings.


2

Was a bug in the core, I published the ticket ( https://core.trac.wordpress.org/ticket/32310 ) and is added for the next version 4.2.3. In this version the code change the collation of some tables and this works fine if the change is fast. But in big tables this change take time, hive a timeout in the upgrade process and can't continue, so is a loop. In ...


0

If you want a hosted solution that you don't have to manage, check out Kernl (https://kernl.us). Its a service that provides the infrastructure for updating plugins and makes it easy to integrate into your own plugins.


2

I don't think anyone can give you a guarantee that you will have no problems, however typically WordPress handles the upgrade process very well. You are only a couple of versions behind so I wouldn't anticipate any major problems. You should consider: Back up all the files and database before proceeding. If you don't know how to do this, ask your web ...


0

Yes, Wordpress does provide Theme API function. I know the question is asked a year ago, but if you want it still, here's the solution. A brief explanation of usage of Theme API is given here: http://code.tutsplus.com/articles/interacting-with-wordpress-plug-in-theme-api--wp-25805 [Go to the Themes API section which is after half of the article] Along ...


1

You may want to check out the WordPress Development Kit plugin. I recently migrated my proprietary update system to this plugin. The plugin now serves as the back-end processor for my premium plugin updates. This is similar in setup to the solution provided by agileapricot above. It will install as a standard plugin on a WordPress site. You host ...


0

Fixed it. Put in a few commands that helped give wordpress the permissions it needed to auto update: sudo usermod -aG www-data $USER sudo chown -R www-data:www-data /var/www sudo chmod -R 774 /var/www This problem has been plaguing me for months. I feel like a huge weight has been lifted off my chest now haha.


0

Ok, I found the problem. It was WordPress Move Comments plug-in's issue and the problem solved by disabling this plugin. I'll say this problem to the developers today.


0

It is possible to upgrade/update the database for each child site individually by visiting: https://rootsite/subsite/wp-admin/upgrade.php See also related core trac ticket, Database is not upgraded in multisite if loopback is disabled


0

Find all the functions "get_avatar" used in your theme folder. Identify the wrong calls echo get_avatar($comment,$size='48',$default='<path_to_url>' ); or echo get_avatar($comment,48,'<path_to_url>' ); If you find these,then change it to echo get_avatar( $comment, 48 ); . Hope this gonna help you :)


3

Blocking the server from your hosts to prevent auto updating won't hide notifications in the back office. You have to add some code in your functions.php file. The answer you are looking for is perfectly explained here You should add these 3 portions of code at the bottom of you functions.php file : The first one will disable wordpress core update ...



Top 50 recent answers are included