plugin-update-checker | custom update checker for WordPress plugins | Content Management System library

by YahnisElsts PHP Version: v5.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | plugin-update-checker Summary

plugin-update-checker is a PHP library typically used in Telecommunications, Media, Media, Entertainment, Web Site, Content Management System, Wordpress applications. plugin-update-checker has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

This is a custom update checker library for WordPress plugins and themes. It lets you add automatic update notifications and one-click upgrades to your commercial plugins, private themes, and so on. All you need to do is put your plugin/theme details in a JSON file, place the file on your server, and pass the URL to the library. The library periodically checks the URL to see if there’s a new version available and displays an update notification to the user if necessary. From the users' perspective, it works just like with plugins and themes hosted on WordPress.org. The update checker uses the default upgrade UI that is familiar to most WordPress users.

Support

Quality

Security

License

Reuse

Support

plugin-update-checker has a medium active ecosystem.

It has 1904 star(s) with 368 fork(s). There are 94 watchers for this library.

It had no major release in the last 12 months.

There are 74 open issues and 356 have been closed. On average issues are closed in 120 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of plugin-update-checker is v5.0

Quality

plugin-update-checker has 0 bugs and 0 code smells.

Security

plugin-update-checker has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

plugin-update-checker code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

plugin-update-checker is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

plugin-update-checker releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

plugin-update-checker saves you 1502 person hours of effort in developing the same functionality from scratch.

It has 3361 lines of code, 307 functions and 37 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed plugin-update-checker and discovered the below as its top functions. This is intended to give you an instant insight into plugin-update-checker implemented functionality, and help decide if they suit your requirements.

Parses lines .
Render a table
Generate link element
Render a text line
Parse a block list .
Parse Markdown markup .
Add a table to continue
Render a single element
Parse Markup markup
Generate an inline image

Get all kandi verified functions for this library.

plugin-update-checker Key Features

No Key Features are available at this moment for plugin-update-checker.

plugin-update-checker Examples and Code Snippets

No Code Snippets are available at this moment for plugin-update-checker.

Community Discussions

Trending Discussions on plugin-update-checker

How to include Composer within a GitHub repository

The variable seems to be independent, but the program works fine. why?

QUESTION

How to include Composer within a GitHub repository

Asked 2021-Jul-08 at 17:02

I am new to both Composer and Git/GitHub so please excuse me if this is a stupid question!

I have built a WordPress plugin which I have in a repository on GitHub and I will use the repository to distribute updates to the plugin using this plugin update checker library: https://github.com/YahnisElsts/plugin-update-checker

The plugin has a number of Composer dependencies that I have installed. I've been researching and apparently you aren't supposed to include the composer vendors directory in your GitHub repository (see here: https://getcomposer.org/doc/faqs/should-i-commit-the-dependencies-in-my-vendor-directory.md) however my confusion is how can I distribute the plugin from GitHub using the update checker if the vendors directory is not included?

What is the correct way to achieve this? Am I missing something obvious?

Thanks a lot in advance, Hayden

...

ANSWER

Answered 2021-Jul-08 at 15:43

add vendor folder to your .gitignore. someone can use (composer install) and (composer dump-autoload) for install your dependencies to project.

Source https://stackoverflow.com/questions/68304488

QUESTION

The variable seems to be independent, but the program works fine. why?

Asked 2020-Nov-20 at 14:31

I'm using the following library to give a update feature to my WordPress and this works fine with the code of documentation.

https://github.com/YahnisElsts/plugin-update-checker/blob/master/README.md

...

ANSWER

Answered 2020-Nov-20 at 14:24

You're creating the variable right there. You can even name it something else if you want (eg. $update_checker), that shouldn't cause any issues in this particular case as the variable isn't being used anywhere else (according to your own words.)

For more details: PHP variables.

Source https://stackoverflow.com/questions/64930526

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install plugin-update-checker

Note: In each of the below examples, part of the instructions are to create an instance of the update checker class. It’s recommended to do this either during the plugins_loaded action or outside of any hooks. If you do it only during an admin_* action, then updates will not be visible to a wide variety of WordPress maanagement tools; they will only be visible to logged-in users on dashboard pages.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: