openannotation / annotator-wordpress Goto Github PK

As they already do with comments, blog administrators will probably want to edit or delete the annotations created by users with lower editorial privileges. Perhaps we need to devise a mechanism whereby blog owners can exert editorial control over those annotations that are created and displayed directly through the Wordpress plugin. At the same time, they should not have editorial control over the annotations created and displayed independently through other clients (i.e. the bookmarklet, as well as other possible clients such as browser extensions ). It seems to me that, although in both cases the data store may be the same, these two are substantially different spaces of debate and they should be regulated by different authorities (the consumer / site owner in the former case, the service provider in the latter ).

Power users may want to override the way the Wordpress plugin instantiates the Annotator. It would be perhaps good to provide the blog owner with to possibility of injecting his own JavaScript snippet and running such snippet right before than the Annotator gets instantiated.

Seems that if you do annotations while logged in (as you need to be) these annotations do not show up if you are logged out.

In the case of reading groups, or blogs where several people peer review each others' writings perhaps it is desirable to display annotations only to group members. This could be implemented as another option for the plugin settings page.

when installing the wordpress plugin, the following message appears after trying to activate the plugin:
plugin does not have a valid header

This plugin causes problems with other JQuery functions.
Could possibly be caused by it including it's own JQuery?

Currently the plugin includes the Annotator on the basis of a single URL pattern defined in the settings page. This is far from being a satisfactory solution, and is not fine grained and user friendly as it should be. On the contrary, It's practically impossible to come up with a regex that matches posts belonging to one or multiple tags or categories.

For instance, if the index page for the blog posts tagged 'bar' is accessible at the URL http://blogaddress/tags/bar, this will be matched by the regex: /\/tags\/bar\/.*$/. However, there is practically no way to define a regex for matching the single URLs of the posts tagged 'bar', as these are typically generated by combining only the date and title, and not their categories or tags .

Perhaps a better approach would be to devise an inclusion mechanism based only on two criteria.
The Annotator would be automatically included for:

• All blog posts belonging to the special category annotable
• All blog posts having the custom field annotable set to true.

Finally, the annotator will not be included if a blog post belongs to the annotable category but also has the annotable custom field set to false.

At the moment annotateit.org is the only annotator store supported. It would be good to offer an option to use a different annotator store.

Fantastic idea, Is there any plans to make this work with new wordpress versions?

Default wordpress select is .entry-content and does not seem to be present in default wordpress twentyeleven theme. We should

a) fix this

b) really highlight in installation instructions that you need to configure this (though I worry about this -- many WP users are non-technical, perhaps we need to some auto-guessing or something ...)

Affects the the current version of the annotator (1.0.0rc3) when injected into the default Wordpress theme.