aboutsummaryrefslogtreecommitdiffstats
path: root/mod/item.php
Commit message (Collapse)AuthorAgeFilesLines
* issue #237 - when manually changing an uploaded photo URL in a post to an ↵friendica2013-12-101-1/+4
| | | | invalid URL that happens to not throw an error, it affects the ability to parse the URL to see if it's a local image and correct permissions. The correct way to do this is to change the '-2' to '-1' if you want 640 instead of 320 and '-0' if you want the original size - which is not likely to win you many friends if it happens to be a 42 megapixel photo. We might have limits in place to prevent monster photos from destroying everybody's streams, but many services you export the post to will probably not.
* allow editing posts on connectors that support editsfriendica2013-11-261-1/+3
|
* sort out the preview iconsfriendica2013-11-251-1/+1
|
* wp-to-red: now supports editing, titles, and native permalinksfriendica2013-11-251-0/+13
|
* Add some message_id meta information for wordpress posts so we'll know where ↵friendica2013-11-241-0/+10
| | | | to send comments
* pull in some posts when we first connect with a new channel (if allowed to) ↵friendica2013-11-171-8/+0
| | | | - if not allowed to, do it if that condition changes
* fix photo permissions on encrypted postsfriendica2013-11-131-2/+8
|
* provide expire feature on post and comments as well as private messages. ↵friendica2013-11-071-5/+3
| | | | This requires a feature setting and is currently unmaskable - if the author says it's gone, there's not a lot you can do to stop it or try and save it. It's gone.
* private tagged posts weren't creating second delivery chain - they were ↵friendica2013-11-041-1/+1
| | | | incorrectly being marked as "in a reshare" due to being obscured.
* part one - honour system.tagifonlyrecip pconfig, default is false - not ↵friendica2013-10-191-2/+3
| | | | ready to deal with the second part yet (changing the tag char for tag_deliver channels) without a bit more discussion/concensus.
* oauth wasn't logging in properly, also fixed api status_show to return last ↵friendica2013-10-151-1/+0
| | | | public post, not the last private post
* linkify post categoriesfriendica2013-10-141-1/+1
|
* Typo in replaced variableOlaf Conradi2013-10-121-1/+1
|
* bug 175 - categories not updated when editingfriendica2013-10-111-15/+1
|
* Typo and whitespaceOlaf Conradi2013-10-071-2/+2
|
* fix a bunch of post editing bugs - though this consolidates some disparate ↵friendica2013-10-041-43/+11
| | | | code and may create some new bugs due to regression
* post signaturesfriendica2013-10-021-5/+10
|
* fix can_comment_on_post when viewing wall-to-wallfriendica2013-09-281-8/+14
|
* hopefully(?) the final word on remote comment permissionsfriendica2013-09-201-0/+3
|
* hopefully this will go over a bit better - check post owner permissions as ↵friendica2013-09-201-1/+9
| | | | well as local owner permissions for comments during submission, since the comment was being blindly accepted on the local system due to only checking the profile owner. Also change collections query to include only top-level posts by a member of the collection.
* sync photo permissions with the attached item whenever they change.friendica2013-09-171-1/+4
|
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-101-1/+2
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* .Christian Vogeley2013-09-081-1/+1
|
* retrun checkChristian Vogeley2013-09-081-0/+1
|
* Merge service classChristian Vogeley2013-09-081-1/+48
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | //service class configure in .htconfig.php: $a->config['system']['default_service_class']='standard'; // this is the default service class that is attached to every new account $a->config['service_class']['standard'] = array('photo_upload_limit'=>20000000, // total photo storage limit per channel (here 20MB) 'total_identities' =>5, // number of channels an account can create 'total_items' =>2000, // number of top level posts a channel can create. Applies only to top level posts of the user, other posts and comments are unaffected 'total_pages' =>10, // number of pages a channel can create 'total_channels' =>500, // number of channels the user can add, other users can still add this channel, even if the limit is reached 'attach_upload_limit' =>20000000); // total attachment storage limit per channel (here 20MB)
| * Service class itemsChristian Vogeley2013-09-081-0/+48
| | | | | | | | Items / webpages /attachment message
* | provide mimetype selector on edit (pages and blocks)friendica2013-09-061-1/+2
| |
* | fix private message encryption since the input_filter mangled itfriendica2013-09-031-0/+3
| |
* | security fix and ability to change layout on webpage edit formfriendica2013-09-031-1/+2
| |
* | pass execflag - Working for preview but not yet executing on page renderfriendica2013-09-021-1/+19
| |
* | fix webpage storagefriendica2013-09-021-7/+3
| |
* | webpage content-type -- needs cleaning up and a security check once all the ↵friendica2013-09-021-117/+127
| | | | | | | | important bits are in place.
* | Sheesh. Three lines of Javascript. All you have to do is find which of the ↵friendica2013-09-011-40/+41
| | | | | | | | three lines is doing something wrong. Or FILE A BUG. Or use a different browser (not *try* a different browser, *use* a different browser), or turn off freaking tinymce. But no - let's argue about browsers instead.
* | add layouts and editlayout and rework the page logic in mod/itemfriendica2013-09-011-13/+4
| |
* | This isn't optimal, but on the short term we'll clone the page editor to use ↵friendica2013-09-011-2/+15
|/ | | | as a block editor, and probably a layout editor as well. Eventually, these should all probably just be switches onto a single editor instance. Decided to put the layout_mid into the item table directory rather than re-use resource_id, so that we can still have pages attached to different resources like photos and events and stuff. The block editor is far from finished, at this point I've only cloned it and changed the name and type of item it looks for.
* block content-type (called ITEM_BUILDBLOCK to avoid confusion with content ↵friendica2013-08-121-0/+3
| | | | that is blocked)
* yhis should fix the privacy leak - as well as non-private replies to private ↵friendica2013-08-011-1/+1
| | | | posts
* fix some privacy leakage in logsfriendica2013-07-311-11/+14
|
* fix bug #84, make imported messages from your clones show up on your wallfriendica2013-07-291-0/+3
|
* encrypt private messages on disk - there are still a couple of places where ↵friendica2013-07-281-0/+30
| | | | the text is leaked in the logs during processing.
* autotag clean-up, mop up, and go homefriendica2013-06-271-4/+5
|
* testing autotagfriendica2013-06-271-1/+2
|
* if you send a private post to an @-taggable channel (and nobody else), tag ↵friendica2013-06-271-0/+12
| | | | | | them. This sort of implements what Zottel was asking for - posting to a forum by posting only to the forum without having to tag it. Taggables are already highlighted in the ACL widget so as to avoid privacy surprises. Currently untested but shouldn't take much to get working if it isn't working already.
* map comment_policy on local post submissionfriendica2013-06-181-0/+1
|
* hijack the #getzot tagfriendica2013-06-151-9/+17
|
* convert most red photos to zmgfriendica2013-05-281-2/+2
|
* workarounds for people that re-install and end up polluting everybody's ↵friendica2013-05-161-0/+2
| | | | databases with stale entries
* get search page working with live-update and endless scroll, still not ↵friendica2013-05-091-1/+3
| | | | perfect - there may be duplicated content and possibly unauthorised content and 'timeago' not working correctly - will deal with those later, but at least you can see results.
* turn naked links in posts into zrl's if we've got a hubloc for the sitefriendica2013-04-181-0/+7
|
* turn all Red links into zrls (not the old zrls, the new bbcode zrl which ↵friendica2013-04-151-4/+4
| | | | means we can zidify them)
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-20 20:35:21 +0000