Unzip the file locally, FTP into your webserver, remove the content of the wp-content/plugins/plugin-notes/ folder, but not the folder itself, then upload the contents of the locally unzipped folder into the wp-content/plugins/plugin-notes/ folder on the server.
Thank you for your quick answer and detailed explanation!
I installed 1.6 on my I use WordPress 3.8.1. and I could not find any bugs – the plugin description is saved, the color and the template for new notes is saved properly so your plugin works perfectly fine and I don’t have any reason to downgrade. I think it is safe to make it official stable version after you try yourself and confirm again what I just said.
And also markdown syntax works, but it is not compatible with WordPress posts and pages and will not be convenient for wordpress users who use visual text editor.
Another little feature request: will it be possible for you to add the link at the bottom to the official wordpress.org plugin page next to the author’s web site (plugin site)?
Thanks for testing! I’ll do some more tests with various WP versions when I get a chance and will upload if they all turn out positive.
And also markdown syntax works, but it is not compatible with WordPress posts and pages and will not be convenient for wordpress users who use visual text editor.
True. The notes are saved in a different format than posts which is why the compatibility is not something I would consider an issue.
And yes, I don’t expect ‘ordinary’ users to use markdown, but then again, I doubt many ‘ordinary’ users use this plugin in the first place. I kind of have the feeling that it’s more a plugin used by developers/advanced admins. In any case, the notes are only available to admins/users with the plugin install capacity, not to ordinary users.
Another little feature request: will it be possible for you to add the link at the bottom to the official wordpress.org plugin page next to the author’s web site (plugin site)?
I’ll have a look at that again when I continue development for 2.0 – you may want to open this as an issue on GitHub to make sure I remember 😉 -. I seem to remember that I previously choose not to implement it as some plugin authors already show the WP link and others link to their own website, which in effect would mean that you could end up with two links to the WP repo in that same line.
Also, the filter used to add the plugin notes, gets the fully formed html of that last line (and basically adds the plugin notes functionality to (and before) the line). That means that adding a link to the line would involve, parsing the html back to the individual parts, adding the link somewhere in between and the glueing it all together again, which does seem kind of error-prone.
Knowing that, what do you think ?
Oh and more about that link: it also would create invalid links for premium plugins and plugins which aren’t in the WP repo. Unless of course I’d test to see that the link is valid which would create quite some overhead what with the round trip to the WP site to check for each plugin.
The link can be added to the note with the variable replacement anyhow and using the variable is a user choice, so they would be ‘responsible’ for the validity of the link in that case 😉
Does that clarify it more ?
I am the site admin, but I use visual editor most of the time because manually typing the code is more difficult. I thought we could have a few basic buttons similar to the editing window in this forum. I was also under impression that if visual editor is already available for wordpress posts and pages, the code could be re-used for the note editor by calling the appropriate functions/libraries. But it looks like I was wrong and it is not that simple. Your plugin is great anyways!
If there is a variable for the link to wordpress.org plugin page, this would be a solution.
Yes, the visual editor is available for re-use, but I seem to remember with only one instance per admin page, which makes it difficult to use for the plugin notes.
I added the variable replacement in v1.5, you can read more about which variables you can use (and the other new features) in the readme.txt file. In v2.0, the information in the help tab at the top of the plugin page has been extended to include a list of the variables (in v1.5 it mentions the feature, not the codes).
Variables can be used in templates too and the result will change depending on the plugin the note is for 😉
Quote from the readme.txt file of version 1.5:
= Which variables can I use ? =
There are a number of variables you can use in the notes which will automagically be replaced. Most aren’t that useful as the info is provided by default for the plugin, but they are included anyway for completeness.
Example use: you want a link to the WordPress Plugin repository for each plugin.
Instead of manually adding each and every link, you can just add the following note to each plugin and the link will be automagically placed:
Plugin: %WPURI_LINK%
**Available variables**:
%PLUGIN_PATH% : Plugin uri path on your website
%WPURI% : URI of the WordPress repository of the plugin (Please note: it is not tested whether the plugin is actually registered in the WP plugin repository!)
%WPURI_LINK% : A link to the above WordPress repository of the plugin
**Already showing for each plugin (less useful)**:
%NAME%: Plugin Name
%URI%: URI of the plugin website
%AUTHOR%: Name of the plugin author
%AUTHORURI%: Website of the plugin author
%VERSION%: Current plugin version
%DESCRIPTION%: Description of the plugin
The variables work fine, thank you!
Is it possible to make all the links clickable by default? Otherwise I had to use [%WPURI%](%WPURI%).
The %WPURI_LINK% variable automatically makes the link. Does that help ?
Yes, it does help, thanks for pointing this out!
Other links, are not clickable, but they already show at the bottom. So this is not a big deal and can be left alone (unless it is very easy to make them all clickable by default).
Thanks again!!!
As you say: they are already clickable at the bottom, which is why I didn’t bother too much with them 😉
Is this update still being worked on?
@jrf: I’ve been actively using the unofficial version 1.6 for more than two months now and I love this plugin! It makes my life so much easier. It works perfectly fine with WordPress 3.8.1 and even 3.9.1 and I didn’t see any problems whatsoever. For some reason the latest official stable version is still 1.1 instead of 1.6 and I am sure WordPress community is missing this wonderful plugin!
It’s rather quiet here lately. Is this on hold or is it still being developed? I have been using this plugin for a long time and happen to be eager for the updates that were mentioned above.
Really, really wanted to try this plugin, but the WordPress Gods have deemed it broken (in v.4, that is). Specifically, when activated it returns a “does not have a valid header” error and deactivates.
edit: the above error is for v.1.6 The stable release completely stopped by site dead in its tracks. Would not recommend on v.4 currently.
@tadees
I am using v1.1 and it still appears to be functioning well on my site.
