Safety when installing plugins on domains I don't own

I developed a wordpress plugin entirely on localhost and tested it on a live server (CPanel) that I have full access to. What I'd like to know is what information I would need from a website owner if I were to install the plugin on their website? The assumption is that the website owner wants to give me as little information as possible, and I too don't want to expose myself to any liability beyond what I absolutely need to view to install the plugin for them.

Thanks

Solutions

release your plugin under gpl, put your name as author make a small readme ant thats it.

If thei hosting supports WordPress autoupgrade feature I don't see any reason of manually installing plugins. It can be done from admin cp there. If your plugin requires manual installation, then, probably, it is a bad plugin ;)

If you want to generate income from support, I am afraid, you will end up with requiring full access to hosting. And also you should know better than us what access will you need in order to support your plugin.

Assuming the plugin is not released publicly, you will need a user account for their WordPress install and FTP acccess.

A better option might be step-by-step instructions, or releasing the plugin on codex.wordpress.org -- if it's available there, you can install it with only a WordPress administrator account, which they can then delete or disable once it's installed.

Tags: PHP / Wordpress / Plugins

Similar questions

Multiple domains, Single database, 1 Parent/Master with all content, other domains/slaves with filtered content (based on "location" variable)
Sorry if the title of this is not clear. Here's my scenario. I want to create multiple sites (will use 3 as example) with the following content filtering. www.main.com - serves all content www.usa.com - serves content that is tagged or categorized as US-only content. www.uk.com - serves content that is tagged or categorized as UK-only content. From...
I have two website domains, A and B. Can I switch the domains so that A's content moves to B, and vice versa?
For context, these are both blogs running on WordPress. They are running different themes that have each been customized. They share the same hosting account. If anyone is wondering how this happened, site A is my name and was the first site I started blogging on. As the blog began to grow, I bought B, a much better domain name that is more SEO-fri...
Installing Wordpress on multiple sub-domains
I have 50 subdomains (created in cpanel) and want to install wordpress on each one - I do do it manually using Softaculous, but can it be done automatically? If so, how?
Shortcode plugins for own custom cms like wordpress shortcode plugins
I have created a custom CMS for my own and a plugin system that is working as I expected. Now I want to create plugins based on shortcodes, eg: [gallery attr1=100 attr2="string"] and [mycode title='message' color='#F00']Hello World![/mycode] I want to handle the above mentioned shortcodes in my CMS. Functions will replace shortcodes with HTML and g...
docker/wordpress: seperate default plugins from own plugins
Let me try to explain what i want to achieve: I am doing wordpress development and and try to set it up nicely via docker. I have a folder with themes and plugin where i my develop plugins and themes in. This folder also contains Docker files to be able to run them i a container where wordpress is installed via its docker image. So far so good, but...
Multilingual wordpress site with own domains for every language
The goal is to have one wordpress instalation with varius language versions which share media library (images...), user accounts etc. but also work on their own second level domains so I have website.com and website.cc and website.de and similar but I dont need to manage three different wordpresses. I guess that should be possible to do using some ...

Also ask

We use cookies to deliver the best possible experience on our website. By continuing to use this site, accepting or closing this box, you consent to our use of cookies. To learn more, visit our privacy policy.