My client has asked me to make a WordPress Plugin that people must purchase. Therefore, it is not put into the WordPress.org plugin repository and is not updatable by default from the Plugins menu in wp-admin.
Is there a best practice way for making the plugin updatable? As in, showing an update on the dashboard, plugin options panel, and Plugins page. When clicked, it automatically upgrades the source code without one having to go through a series of steps. How would you suggest this would work, and do you have any code snippets to explain the process?
I think the best code snippets are in the WordPress code itself. See how they do it, and duplicate it with your plugin. Basically, they send some information about your installed themes and plugins to an server, which responds back with updates if there are any. You can remove your plugin from the list that is sent to WordPress if you want to keep this info to yourself.
Related
We are preparing a flutter plug-in for a corporate company. We want users using this plugin not to see the codes. So how do we obfuscation the codes? I know you cannot upload it this way via pub.dev. We can send this plugin to them as an external file.
I don't think it is possible with the current set of tools. I guess the main reason is that plugins are not compiled.
I also think it is this way by design. But you could always post a feature request to the Flutter team.
I have been working with Wordpress and Drupal for a while now, and something you have to do to maintain those CMSs is update themes, plugins, core, and modules.
My question is do you have to do that with the ExpressionEngine CMS? In the addons dropdown, there are modules, accessories, extentions, fieldtypes, and plugins. When I go to these, it doens't look like there is a way to update them. It shows what version there is, and I am able to delete them from there, but no updates anywhere in sight. Is it something I even need to do?
Thanks
Edit: I found the "update modules" button, but I still do not see anything like that for plugins, or anything else.
EE doesn't make it quite as easy as it is in WordPress. You could check out the Lamplighter extension to see what's still in need of an update then download from the respective source.
This is getting into opinion a bit but when I did a lot of EE dev, I usually stuck to the philosophy that if it worked, I used it and didn't worry about upgrading. Occasionally an extension/plugin would get a significant upgrade, a security patch, or have a feature implemented that I needed. That's That's when I'd go through the process of downloading and installing updates.
I've to create plugin or add-on for my official community site.
Requirement
There should be a button at browser, which should extend a form, which can add the current url as a bookmark with interaction from user with some more inputs, in turn that should be recorded into excel sheet in local drive. I've VBA code to extract data from the community url to excel sheet. Now, I've to create browser control to enable user direct url to fetch the data.
My control should be activated (i.e. toolbar button) based on url, so what should i create, a plugin or add-on ? i want my control not to affect browser performance or user experience.
Based on reply for 2, what tool should i use to create plugin/add-on which should be compatible across browsers ?
I've gone thro' Fire-breath demo, code capability with Visual studio, which was nice, but still missing some knowledge about visual studio, what to package of visual studio install and what language to use, it would be better if it is Visual basic ?
At last, is it possible to place control (i.e. button) inside the webpage to activate my code, if so, which one is capable of doing it, add-on or plugin ? workflow in nutshell to achieve that...
Thanks a lot
First, a few things to understand:
A browser plugin is something that is instantiated in one of two ways:
Injected into the DOM in an object or embed tag
Instantiated by the browser to open a page with a specific mimetype
Browser plugins don't know anything about the browser, the URL bar, the bookmarks, the context menus, browser dialogs, browser chrome, browser events, etc. Browser plugins only know anything about the current page. Browser plugins cannot change browser settings
Browser plugins are DLLs; they can't easily be written in Visual Basic. While it might be possible, I've never seen one, and you'd have to learn a lot about NPAPI plugins before you could do that. You'd also probably have to write one for IE, one for IE, etc.
In other words, what you need is not a plugin. Firebreath is not going to help you much, if at all. Some extensions (also called add-ons) use a npapi plugin to provide functionality that they cannot do on their own. For more information see http://npapi.com/extensions
With that information, I recommend you think about it and create a new, more specific question for what you need to know next. I don't know extensions, I do plugins. Actually, once you break down what you need to do into some smaller questions you'll probably find others who have ask most of them and you can find the answers with simple searches. Your main problem is that you don't yet understand the technologies you need to use. Hopefully this has helped.
I would like to disable a read more plugin ( cutof content) in all pages except my main menu pages in joomla
How do I do this
Thanks in advance
I'm not aware of any method that allows for the actual disabling of a plugin for certain pages. Plugins are either on or off, site-wide. This can be seen from the Extensions | Plugin Manager, as well as the SQL database: jos_plugins. With that said, what would be the purpose in disabling a plugin for certain pages? Most plugins, especially those like a "readmore" are typically setup to be activated by a simple code sequence, such as {readmore}path/file.htm{/readmore} and consequently, you can turn the plugin "off" by simply choosing to not use it. Most plugins of that nature provide very little more than essentially "coded access to a CSS class". If you could be more specific on why you need to actually disable the plugin for certain pages, perhaps we'd be better equipped to answer properly.
Depending on the plugin, you could feasibly remove the event trigger that would set the plugin to run, thought it would not be advisable since it would stop that trigger for all plugins and could cause unintended effects.
I am not sure what you mean by "Read more" plugin. You can turn the read more text on and off as a setting in the menu item parameters or in the article itself. Have you tied that?
i just want to know about the files and folder structure for a site which is a plugin oriented like wordpress or joomla.
my requirement is to develop a site and want to add more functions via plugin or something like features.
what i need is to just add and additional information or functional sessions like in wordpress
we can use All in one SEO packages it will bypass the title and some other information.
or some other features like Related articles are shown at the bottom of a particular article body.
aam talking about a structure of wordpress.
does any one have an Idea please share with me.
hope every one understood my qustion as well.
thank you.
I think there are many possible solutions.
It might depend on:
scalablity (how large do you want it to support plugins and do the reuse parts of each other?)
vibility (how should the plugin address become visible in the url?)
deployment (who can add new plugins? is it open for everyone or just certified developers)
You could go for:
www.domain.xyz/plugins/some_module/
But what if the plugins arent plugins but becomes default part of the system afterwards?
Then it would be more logical to call them what they are like:
www.domain.xyz/some_module/
But then you might get into problems with plugins name like exisiting system folders. Therefore you would need some "reserved" list of foldernames to prevent that.
You could also go for:
some_module.domain.xyz/
But that would requiere your webadmin or webserver to support multiple aliases for one website on the other hand, this arhictecture would bring scalability, because you could move the modules to other webhosts later on. But its also more expensive work in the development + its hard to make it "user/developer controlled" as this could grow.
You could have a look at how FaceBook is handling Applications too. Thats a plugin interface too. Slow, but implemented.