* only encode needed data
* don't show user select if there isn't more than one user
* vertically center follow me
* add title to handle: might be truncated
* theme compat: ensure readability in dialog
* theme compat for dark bg themes
* fix html-entity issue in username
* remove kses
let other platforms decide what to allow and what not
* Remove html_entity_decode to prevent encoding issues (#454)
I've tested this on content which includes MarkDown, HTML, encoded entities, unencoded entities, etc.
Fixes#445
Co-authored-by: Matthias Pfefferle <pfefferle@users.noreply.github.com>
* remove allowed tags
---------
Co-authored-by: Terence Eden <edent@users.noreply.github.com>
* Fix styles in Follow-Me block
A line height of 1 can easily hide some parts of letters like "g" or "p" which makes the actor-handle difficult to read.
The line height might even be up to 1.5, haven't investigated in best practices.
* build files
---------
Co-authored-by: Matthias Pfefferle <pfefferle@users.noreply.github.com>
Co-authored-by: Matt Wiebe <wiebe@automattic.com>
* fix#463
* fix delete
/cc #465 @janboddez
* add disclaimer to not use the same name as an author login
see #470
* check if url is cached before trashing it
* more group friendly settings
* change http code
* Fix Actor-Type
* fix check if value is set
* only ignore null
* better posting_restricted_to_mods handling
* remove user namespace from moderators endpoint
thanks for the feedback @mattwiebe
This will prevent the issue of attaching images that don't were uploaded to the post but not used in the post
The post needs to be using blocks to get the introspection required.
* Use a tag stack instead of regex for protecting tags
* Use the placeholder in the test
* Add comments
* Update comment
* ignor html comments
thanks @marcS0H
---------
Co-authored-by: Matthias Pfefferle <pfefferle@users.noreply.github.com>
* Blocks: short-circuit early on sites that do not support blocks
Fixes#430
This is typically only the case for sites using a custom version of WordPress, like ClassicPress.
* let grunt build the markdown
* Check for block support earlier and add filter
One can now deactivate the blocks registered by ActivityPub like so:
```
add_filter( 'activitypub_site_supports_blocks', '__return_false' );
```
* Fix readme (gotta remember to use grunt)
* alias function
---------
Co-authored-by: Matthias Pfefferle <pfefferle@users.noreply.github.com>
* Post images: fix a typo in the hook name
Follow-up to #309
It should be '_post', not twice '_pre'.
* let grunt create the readme.md
---------
Co-authored-by: Matthias Pfefferle <pfefferle@users.noreply.github.com>
* Repository maintenance: add GitHub Repo Gardening action
The Repo Gardening action is a tool that one can use to automate some of the tasks that you can perform to monitor activity in your repository.
https://github.com/marketplace/actions/repository-gardening
It includes different tasks, that can be enabled based on your needs.
This commit gets us started with the action by enabling a few tasks.
- This action relies on a few secrets that have already been added to this repo.
- Of note, `gatherSupportReferences` and `replyToCustomersReminder` aren't too useful right now, but will become useful once the plugin is released on WordPress.com and once we start receiving feedback from WordPress.com site owners.
- The `flagOss` task will point to #fediverse for now. This can be updated later on.
- I've added mapping for our 2 block directories, but that mapping can be extended for more automatic labeling later on.
* Add issue templates
